Screenshot Section
Last updated
Was this helpful?
Last updated
Was this helpful?
Visual validation is an integral part of automated testing, and the AutomationReport.html facilitates this by embedding screenshots within the test report. These images, which feature highlighted elements, offer an immediate visual reference that corresponds with the validation points of the test cases.
Screenshots in the report are not just static images; they come with dynamically created borders around elements that are subject to validation. This helps to draw focus to where exactly the validation checks are performed within the application's user interface.
Highlighting: The automated test suite enhances visibility by placing a distinct border around the UI element being validated. This could be a color-coded outline that encircles the element in question.
Clarity in Validation: This visual cue unambiguously indicates the focal point of the test step, making it clear what the automated test was checking at that moment.
When reviewing the report, the highlighted elements in the screenshots allow for a quick understanding of where the test actions took place and which elements were involved in the test failures or successes.
This feature is particularly useful when sharing reports with team members who were not directly involved in writing or running the tests, as it provides a clear picture of the test scenario without the need for additional explanation.
Embedded Images: Each screenshot is embedded as a base64 image within the report, ensuring that the report is self-contained and easily shareable.
Interpreting Highlights: The highlighted borders serve as a guide to identify the validation areas quickly. It becomes particularly useful in understanding why a test may have failed — whether it's because the element was not present, not visible, or not in the expected state.
The highlighted screenshots in the AutomationReport.html are a testament to the attention to detail in your automated testing process. They provide a powerful means for validating the UI against expected outcomes and help anyone reviewing the report to understand the test context at a glance. By facilitating this level of clarity, the report becomes an invaluable tool for both developers and stakeholders to ensure the application meets the desired quality standards.
