Sign Up for a Free Trial
Head to the VisualTest free trial page https://try.smartbear.com/visualtest:
Complete the required fields. Note: your entity's VisualTest account is linked permanently to the email address you use in this step.
Check your inbox for the confirmation email.
Click the verification link in your email. It opens the VisualTest login screen.
Log in with your SmartBear credentials.
When you first launch VisualTest, an Example Project is loaded automatically to give you a first look at the functionality:
To configure VisualTest, you need to:
- Generate a project-specific token
- Integrate VisualTest into your automated UI tests
- Run VisualTest
- Review differences found
Generate project token
At launch, VisualTest shows the Projects screen. Click on Create Project and name your Project, as shown below:
- Click Create. VisualTest generates your project and a project-specific token.
Copy your project token, as in the following image. You need this to integrate VisualTest into your functional test scripts.
The following video shows these steps:
If ever you need to find your project token later, it is available from project settings:
Integrate VisualTest into your UI tests
To integrate VisualTest into your UI tests:
Install one of the Software Development Kits (SDKs) to add screenshot capture commands where you’d like to add visual coverage.
The following video gives an example of inserting the project token into your script.
Choose from one of the following capture formats:
- Fullpage – captures the whole page
- Viewport – captures the visible portion of the page
- Element – captures a specific visual element
Run your tests
VisualTest is designed to run using your existing functional UI test flows and framework. Simply run your VisualTest integrated test scripts using your test framework’s command of choice, either locally or via any CI/CD systems.
The following video shows an example of running a test.
Regardless of how you run your tests, VisualTest returns a console log output (see below) containing a link to accept and review any found image differences in your GUI.
Review any visual differences
There are two ways to review found differences:
Follow the output link given in the console log.
Open the VisualTest platform.
Accept or reject differences. Read how in Comparisons.
Your team can find all your test runs in any given Project, listed chronologically by default, as in the following image.
Each test run presents at a high level all the images that need review, and each review status is timestamped. Any team members who have access to the VisualTest platform can approve or reject any of the visual differences found.