Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clean-up allure report output of the resource checking step #3644

Open
ikalinin1 opened this issue Feb 15, 2023 · 1 comment · May be fixed by #3782
Open

Clean-up allure report output of the resource checking step #3644

ikalinin1 opened this issue Feb 15, 2023 · 1 comment · May be fixed by #3782
Labels
feature New feature or request

Comments

@ikalinin1
Copy link
Member

Currently, resource checking results in a large amount of redundant data such as HTTP client logs, request/response attachments. See the report.
allure.zip

In order to simplify the step outputs and increase the user experience we need to refactor the report output of the step and reduce it to the resulting table.

Steps to reproduce:

  1. run the tests https://github.com/ikalinin1/demo-tests
  2. open report
  3. go to RESOURCES suite and observe step representation in the report.
@ikalinin1 ikalinin1 added the feature New feature or request label Feb 15, 2023
@ikalinin1 ikalinin1 added this to To do in VIVIDUS Framework Development via automation Feb 15, 2023
@EDbarvinsky
Copy link
Contributor

During the discussion with the team, we agreed, that it makes sense to store attachments with requests/responses.
At the same time to get rid of the information that duplicates in the final resource validation table, makes sense to get rid of the sub-steps for GET\HEAD reporting for resources (but should be present in the log) and leave them for pages. Example of the steps which may be removed on the screenshot:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

2 participants