Testing across environments

One of the most common tests Trakr performs is visual testing across two project environments. A project environment is a “specific version of your website/web-app“. For example, one of the most common practices for web-development is to configure:

  • development environment where new features and functionalities are deployed and tested. This environment can be somewhat unstable but is often useful to test out the website or web-app.
  • staging environment (or sometimes referred to as pre-production) where tested features and functionalities are deployed. This environment will often have contents and other assets configured to mimic the final live website/web-app. It is often used by a wider audience to review the latest features/functionalities that are ready to be finalized to the live/production environment.
  • production environment (live environment) is where the current version of the website/web-app is located. This is accessible by the intended end-users (often the public) and serves as the most stable/scalable version of your project.

Environment settings

Configure the environments

Trakr requires that you have at least the “production environment” configured as part of your project. If your web project is not live yet, you can simply input your web project’s current development URL into the production environment setting in Trakr.

(Often your staging and/or development environment can have basic authentication setup. Make sure you configure them as part of your environment setup in Trakr.)

Testing across environments

Once you have set up 2 or more environments in Trakr. You can perform a quick test between them from your project page.

Test environments

This will effectively create 2 sets of screenshot collections (one for each project environment) and trigger a visual test between them.