Recommended Guidelines

In this guide, you’ll find a quick overview of our foremost recommendations.

Use Percy and BrowserStack for both visual and functional assertions

Percy should be used to complement or encompass functional assertions with less lines of code and more test coverage. You should be running your visual and functional tests together.

Verify the entire page

While there are various options to visually verify your application with Percy, we recommend verifying the entire page of your application to obtain the most coverage from your visual testing. This can be done with full page screenshots, for your website as well as your mobile apps.

Use the Recommended match level

By default, Percy uses the Recommended match level (our recommended comparison method), which employs Percy’s Visual Engine to compare your baseline image with the current image from a regression run.

Utilize a wrapper class to encapsulate visual checks

It’s a good practice to create a wrapper class that isolates the Percy Screenshot calls so that if there are any changes to the percyscreenshot call, the required changes to the test code will be limited to an individual function.

Use BrowserStack’s device grid to run cross-platform tests

BrowserStack’s Automate and App Automate enable you to execute your tests across many different browsers, viewports, and devices at a fraction of the time it takes with other solutions.

Use the Percy dashboard to collaborate

The Percy dashboard can be used to assign failures to developers or QA teams to review, and remark on questionable changes.

Integrate Percy with Slack and MS Teams for faster collaboration on failed visual tests

If your team already uses Slack or MS Teams for collaboration, we recommend integrating Percy with Slack or Teams, which makes sharing and resolving visual bugs easier.