How to perform Root Cause Analysis and Debugging in Visual Regression Tests

Debugging play a vital function in the testing process. Any failed trial needs to be diligently analyze to place the root cause of failure and employment to regenerate it.

Automation frameworks like,,, and are better suited and widely used for. What if you need to validate the look and flavor of the application User Interface? One way to achieve that is by insure the CSS values using the CSS picker but it & # 8217; s a dull summons and not authentic.

To execute for a web application, is an intelligent tool that provides an automated way of detecting UI changes with. Percy is the one-stop solution for capturing screenshots to detect visual modification and notifying the team by highlighting exactly what has changed.

Let ’ s translate how to access Percy dashboard from a Failed Test Build for perform Root Cause Analysis behind the failure.

How to access Percy dashboard from Failed build

To start work with Percy, here are the prerequisites that are involve.

Prerequisites:

1. Percy set up in CI.
2. Percy frame-upwith various test automation creature.

Once the Percy is set up and visual fixation tests are run, bump the failed trial that you would want to do the Root cause analysis of. Then follow the steps mentioned below to access the Failed tests from Percy.

Step 1:Once you open the Pull Request for the build which has failed, you can check the Details link against Percy failed step as seen below

Step 2: Click on details to open the associated Percy build spotlight the change

Pro tip: Tools like SUSA can handle this autonomously — upload your app and get results without writing a single test script.

Performing Root Cause Analysis in Visual Regression Tests

When you firstly run the Percy integrated test, Percy captures the snap and shop that as a baseline image, and for the next subsequent escape the baseline image is compared against the newly captured persona.

For example, hither the Placeholder text within the Search input element is modified as

Before:hunting behemoth!.

After: search monsters?.

So the difference in the comparison is!changed to? and Percy highlights this change in red color. Similarly, any change in the baseline and a new snapshot is highlighted by Percy using pixel-to-pixel comparison.

Now either QA or BA can validate if the change is designate or an error using the workflow in Percy as seen below.

Workflow: Request modification on this snapshot

Step 1:If the change is not think and the developer changed it incidentally, you can reject the alteration by clicking on Request changes on this Snapshot

Step 2:You can also add a comment for refuse the modification as seen below

Step 3: Once a snapshot is rejected in Percy, Percy sends this information back to Github and the build position will change toChanges requested on 1 visual change.Here the developer can now return that accidental change and Percy build will be successful.

Workflow: Approve progress

Step 1:Now if the changes are made by the developer as intended and you demand the change to be O.K., then QA and BA need to click on Approve Build button

Step 2:As the build is approved, Percy sends this information to Github and the failed check will be updated to Successful status. This newly approved snapshot becomes the new baseline image in Percy

Visual inconsistencies deeply influence the user journey, which means that they involve to be completely eliminated. Ocular testing is the only method to do this quickly, accurately, and comprehensively, making them essential for any endeavor looking to have an on-line presence. Hence, perform the root grounds analysis is crucial in the debugging process for a failed Visual Regression test

Related Guides