Test Execution Workflow
This workflow is responsible for generating snapshots (screenshots) of the website or app under test. Users new to visual testing often have an existing test suite in WebdriverIO, Cypress or a similar framework. With Sauce Visual testing existing test suites can be enhanced with a few extra "take a snapshot" statements and that is all it takes to implement this workflow. Test Execution can be executed for both E2E and Component Testing.
Sauce Visual provides integrations with different kind of frameworks:
- E2E Testing allows to navigate a website and capture snapshots any time this is needed.
- Component Testing allows to test extensively all your components.
Alternatively, check out our examples.
First Test Execution
Upon executing your tests for the first time, a visual baseline is automatically created in our system. This baseline serves as the standard for all subsequent tests and matches based on the metadata as described in the Baseline Matching.
The newly created baseline needs to be reviewed and approved by a user. This can be done in the Sauce Visual Builds page. Once approved, see Reviewing and Accepting baselines, the baseline is "locked" and will be used for all subsequent tests.
Subsequent Test Executions
As new tests are run, they are compared to the original baseline, with any deviations highlighted to signal visual changes. These comparisons are integral for detecting any unintended visual modifications early in your development cycle. All test builds, including the initial baseline and subsequent runs, can be monitored and managed through the Sauce Labs platform at Sauce Visual Builds.
The baseline is established during the initial run, and any subsequent visual differences detected will be marked for review.