Skip to main content
No Result Found

Run a sample App Percy build with Appium and C Sharp

Get hands-on experience on running App Percy with Appium and C-Sharp using our sample repository

Prerequisites

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

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

Run your App Percy build

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

Clone the sample application

Clone the sample application and install the required dependencies:

Copy icon Copy

Upload the sample application

Upload the sample application to BrowserStack App Automate:

Copy icon Copy
Copy icon Copy

After the command runs successfully, you get a response similar to the following:

Copy icon Copy

Make a note of the app url.

To know more about uploading an app to App Automate, refer to the Upload an App REST API documentation.

Create an App Percy project

Sign in to Percy and create a new app project, for example, test-project. After you’ve created the project, you’ll be shown a Percy Access Token. Use it in the next step.

Create an App Percy project

Set Percy token as an environment variable

Export the token environment variable:

Copy icon Copy

Usually this would only be set up in your CI environment, but to keep things simple we’ll configure it in your local shell so that Percy is enabled in your local environment.

Generate the first build

Check out a new branch for your work in this tutorial (we’ll call this branch tutorial-example), then run tests & take screenshots:

$ git checkout -b tutorial-example
$ npm install
$ npm install -g @percy/cli@latest

Minimum required @percy/cli version is 1.15.0 for this to work correctly. If you already have @percy/cli installed, please update it to latest or minimum required version with npm update -g @percy/cli.

Go to appropriate directory, depending on your protocol - JSONWire or W3C (we will continue this tutorial with JWP):

Copy icon Copy
Copy icon Copy

Use your text editor to edit JWP/Android/Android.cs & JWP/Ios/Ios.cs to update USER_NAME, ACCESS_KEY and APP URL with BrowserStack User name, Access key, and App URL that you received in step 2.

Copy icon Copy
Copy icon Copy

In general, your Test would look like below. Whenever you have to capture a screenshot for visual testing, use Screenshot function.

Copy icon Copy

Now, it is time to run your tests:-

make test-android
make test-ios

This will run the app’s Java Appium tests, which contain calls to create Percy screenshots. The screenshots will then be uploaded to Percy for comparison. Percy will use the PERCY_TOKEN you used in Step 2 to know which organization and project to upload the screenshots to.

You can view the screenshots in Percy now if you want, but there will be no visual comparisons yet. You’ll see that Percy shows you that these screenshots come from your tutorial-example branch.

Modify the sample application

Now, it’s time to introduce some visual changes to your app. Replace the search_input.send_keys in your test script as shown below.

search_input.send_keys("BrowserStack again")
search_input.send_keys("BrowserStack again")

Commit your changes

Create a commit with the changes.

Copy icon Copy

Run tests again

Run the tests with screenshots again.

make test-android
make test-ios

This will run the tests again and take new screenshots of our modified application. The new screenshots will be uploaded to Percy and compared with the previous screenshots, showing any visual diffs.

At the end of the test run output, you will see logs from Percy confirming that the screenshots were successfully uploaded. The logs will also give you a direct URL to check out any visual diffs.

View visual differences on dashboard

Visit your project in Percy and you’ll see a new build with visual comparisons between the two runs. Click anywhere on the Build 2 row (we are assuming here that you are using a new project to test things out). You can see the original screenshots on the left, and the new screenshots on the right.

Percy has highlighted what’s changed visually in the app! Screenshots with the largest changes are shown first You can click on the highlight to reveal the underlying screenshot.

View visual differences

If you scroll down, you’ll see that no other test cases were impacted by our changes to text. The unchanged screenshots are shown under an Unchanged filter and are hidden by default.

Congratulations!

From here, you can try making your own changes to the app and tests, if you like. If you do, re-run the tests and you’ll see any visual changes reflected in Percy.

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