Skip to main content
Experience faster, smarter testing with BrowserStack AI Agents. See what your workflow’s been missing. Explore now!
No Result Found
Connect and get help from 7,000+ developers on our Discord community. Ask the CommunityAsk the Community

Instant failure analysis with Screenshots

Low Code Automation enables instant analysis of failed test executions with Screenshots.

Screenshots provide a visual record of the application’s state for your test steps. They are invaluable in pinpointing the exact moment when a test failure occurs, making it easier to identify the cause of the issue.

With Low Code Automation, screenshots are automatically captured at various key stages of the test like navigation, click actions and validation steps. These screenshots are available during both local and cloud test executions. You can even download the screenshots for bug reporting.

How to view screenshots for tests ?

You can access screenshots for any test execution, whether local or cloud, simply by clicking the + icon associated with the respective test step. View test screenshots

Compare with baseline screenshot

When a test step fails because an element can’t be found, comparing the current state of the page against the recorded baseline helps you identify what changed. For element detection failures, Low Code Automation captures the screen at the point of failure and lets you compare it side by side with the baseline screenshot, which is captured during the first successful build run of a test step. This helps you identify whether the page layout, a blocking dialog, or a missing element caused the failure.

The failure also reports how much the page has changed from its recorded state. For example, Could not find element on the page. Please file a bug or re-record the test step. The page has changed 93.24% since recording. A high change percentage tells you the page differs significantly from when the step was recorded, so you can decide whether to re-record the step.

This feature is in beta and available to select customers.

On a failed step, select Compare with expected screen to open the comparison view.

The Compare with expected screen option on a failed element detection step.

The comparison view shows the baseline screenshot, which is the expected state, alongside the captured screenshot, the current state at the point of failure.

The comparison view showing the baseline and captured screenshots side by side for a failed step.

In the comparison view:

  • The captured screenshot is a full-page screenshot, so you get the complete view of the webpage instead of only the visible viewport.
  • You can download either screenshot using the Download icon available on the comparison view.

We're sorry to hear that. Please share your feedback so we can do better

Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked





Thank you for your valuable feedback

Is this page helping you?

Yes
No

We're sorry to hear that. Please share your feedback so we can do better

Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked





Thank you for your valuable feedback!

Talk to an Expert
Download Copy Check Circle