You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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:
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:
The text was updated successfully, but these errors were encountered: