Skip to main content
Transform your testing process with: Company-wide Licences, Test Observability & App Percy
No Result Found

Run a sample Percy build with Playwright

Get hands-on experience on running Percy with Playwright using our sample repository

With Percy, you can automate the visual testing of web applications, ensuring visual consistency across different releases and preventing visual regressions. This page demonstrates how to use Percy Standalone and Percy with Automate to run visual tests on a sample web application.

Prerequisites

Before you start, ensure that you have the following installed:

Run your Percy build

Follow these steps to clone the sample web application, run a build, and view the results of the visual comparison:

Clone the sample application
Clone the example-percy-playwright application, change the directory, and compile the sample application by running these commands:

Copy icon Copy
$ git clone https://github.com/percy/example-percy-playwright-python.git
$ cd example-percy-playwright-python
# create virtual environment
$ python3 -m venv env
$ source env/bin/activate
# update the pip if not updated already using [python3 -m pip install --upgrade pip]
# install the required packages
$ pip3 install -r requirements.txt
$ npm install
Copy icon Copy
$ git clone git@github.com:percy/example-percy-playwright.git
$ cd example-percy-playwright
$ npm install
Copy icon Copy
$ git clone git@github.com:percy/example-percy-playwright-java
$ cd example-percy-playwright-java
$ mvn compile
$ npm install
Copy icon Copy
$ git clone git@github.com:percy/example-percy-playwright-dotnet.git
$ cd example-percy-playwright-dotnet
$ npm install

You can explore the sample application by opening the src/main/resources/index.html file.

Create a Percy project
To create a project, follow these steps:

  1. Sign in to Percy.
  2. In Percy, create a project of the type, Web.
  3. Name the project. After the project is created, Percy generates a token.
  4. Note down the token. You have to use it to set your environment variable in the next step.

For details on creating a project, see Create a Percy project.

Set the project token as an environment variable
Run the given command to set PERCY_TOKEN as an environment variable:

Copy icon Copy
export PERCY_TOKEN="<your token here>"
Copy icon Copy
$Env:PERCY_TOKEN="<your token here>"
Copy icon Copy
set PERCY_TOKEN="<your token here>"

To learn about environment variables in Percy, see Percy environment variables.

Generate the first build
In this step, we run the sample test script to take a few snapshots using the percy.snapshot method. The sample application contains an file in which the method is called. The goal is to have a visual build with which to compare a later build.

Copy icon Copy
$ npx percy exec -- python3 tests/web/test.py
Copy icon Copy
$ git checkout -b tutorial-example
$ npm run test-web
Copy icon Copy
$ npx percy exec --verbose  --  mvn test -P web-percy-test
Copy icon Copy
$ cd web
$ npx percy exec --verbose  -- dotnet test --filter "Category=web-percy-test"

On completion, you see logs from Percy confirming that the snapshots were successfully uploaded and a direct URL to the dashboard. There are no visual comparisons yet.

Screenshot of the sample application on the Percy dashboard

Modify the sample application

Copy icon Copy
$ npx percy exec -- python3 tests/web/after_test.py
Copy icon Copy
<button class="clear-completed" style="font-weight:bold">Clear completed</button>
Copy icon Copy
$ npx percy exec --verbose  --  mvn test -P web-percy-after-test
Copy icon Copy
$ npx percy exec --verbose  -- dotnet test --filter "Category=web-percy-after-test"

Commit your changes

Commit the changes that you made to the sample application.

Generate the second build
Run the test script again.

Follow Step 4 to generate your second build.

This takes new screenshots of our modified application, uploads them to Percy, and compares them with the previous screenshots to show visual differences.

View results

  1. Open your project dashboard to view your builds.
  2. Open the second build to view the visual differences in comparison to the first build.

On the third pane, you see the screenshots from the first build on the left, and from the second, on the right.

Percy highlights what’s changed visually in the application. Use the options on the screen to review the changes on different browsers and widths.

Congratulations!

You’ve successfully run the sample Percy build. As you’ve seen, Percy helps you capture visual differences in your application that go undetected with functional testing alone.

This was just a sneak peek. Percy can do a lot more. To make the best out of it, integrate Percy with your test suite. To know more check out the related topics.

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