Visual testing is the process of comparing application UI with the results expected by design or with the previous state of the application. Automated visual testing tools, like Argos, allow monitoring of the application's UI on multiple browsers and screen sizes.
Argos visual testing is based on screenshots comparison changes detection and manual review. With this process, developers can check the visual impacts of their pull requests in a few seconds, even on a large application.
Visual changes detection
Argos notifies you directly on your GitHub pull-request by adding a status check. If there is no change detected detected, the status is ✅ Pass, you can confidently merge your pull-request.
If some changes are detected, the status is ❌ Fail. In this case, you have to review your visual changes.
Click on the "Details" link to review the visual changes.
Review visual changes
The visual changes review takes place in the Argos application.
Argos build example
Navigate through the screenshot diffs by clicking on the sidebar, the navigation buttons, or using your keyboard.
?to show all available keyboard shortcuts.
The side-by-side UI is designed to quickly spot visual changes and verify that screenshots match their expected results.
👎 Reject a build workflow
If you spot a visual bug or if a screenshot doesn't satisfy your expectations, click on the "Review changes" button and select "Reject changes". The build status becomes "Changes rejected", and GitHub is notified of the rejection.
After rejecting the change, you should commit a new version to fix it.
👍 Approve a build workflow
When screenshots match the expected results, click on the "Review changes" button, then select 🟢 "Approve changes". The build status becomes 🔴 "Changes approved", and GitHub is notified of the approval.
Once the changes are accepted, you can confidently merge your pull request.
How to update the screenshot comparison baseline?
Argos updates the comparison baseline screenshots when a commit is merged into the repository's reference branch.
What is a reference branch?
The reference branch is used as the baseline for the screenshots comparisons. Argos automatically uses the GitHub default branch as the reference branch. You can choose another reference branch in Argos repository settings.
How to update the reference branch?
What is an orphan build?
An orphan build is the first one performed on a reference branch. It won't show any comparison. The screenshots of this build will be considered as the baseline for the following comparisons.
What is a reference build?
A reference build is created when a commit is merged on the reference branch. Its screenshots will be used as the baseline for following comparisons performed on other branches.