visual-regression-tracker

Open source, self hosted solution for visual testing and managing results of visual testing.


Keywords
cypress, docker, hacktoberfest, image-comparison, playwright, regression-tests, testing, visual-testing, visual-tests
License
Apache-2.0
Install
pip install visual-regression-tracker==4.0.0

Documentation

Stand With Ukraine

Visual Regression Tracker logo

Visual Regression Tracker

Open source, self hosted solution for visual testing and managing results of visual testing.

Hello

How it works

Service receives images, performs pixel by pixel comparison with it’s previously accepted baseline and provides immediate results in order to catch unexpected changes.

Demo

Features

  • Automation framework independent - no need to stick with specific automation tool, integrate with existing one
  • Platform independent - web, mobile, desktop etc. as long as you could make a screenshot
  • Baseline history - track how baseline image changed since the beginning
  • Ignore regions - improve stability by ignoring not important or not controllable parts of image
  • Language support - JS, Java, Python, .Net or any other via REST API (need more?)
  • Easy setup - everything is inside Docker images
  • Self-hosted - keep your data save inside your intranet
  • Can compare PDF too - use standalone jar to compare pdf and images from a folder

Glossary

  • TestVariation - historical record of Baselines by Name + Branch + OS + Browser + Viewport + Device,
  • Baseline - validated and accepted image, latest will be used as expected result in TestRun
  • TestRun - result of comparing image against Baseline
  • Build - list of TestRuns
  • Project - list of Builds and TestVariations

Set up

Use any of the below ways to setup the server. Docker has to be installed on the machine.

Quick Setup

Linux, macOS, WSL

  1. Download the installation script
curl https://raw.githubusercontent.com/Visual-Regression-Tracker/Visual-Regression-Tracker/master/vrt-install.sh -o vrt-install.sh
chmod a+x vrt-install.sh
  1. Run the installation script

./vrt-install.sh

Command line arguments

Installs the Visual Regression Tracker

Usage: ./vrt-install.sh

Arguments:
    -h | --help
    -a | --frontend-url <url>   Set the Front-end url. Default: http://localhost:8080
    -r | --backend-url <url>    Set the API url. Default: http://localhost:4200
    --jwt-secret <secret>       Set the JWT secret. Default: randomly generated
Manual Setup
  1. Copy docker-compose.yml

$ curl https://raw.githubusercontent.com/Visual-Regression-Tracker/Visual-Regression-Tracker/master/docker-compose.yml -o docker-compose.yml

  1. Copy .env

$ curl https://raw.githubusercontent.com/Visual-Regression-Tracker/Visual-Regression-Tracker/master/.env -o .env

  1. In .env file, ensure that the REACT_APP_API_URL has the right address. If it will be accessed from other machines, change localhost with IP or other resolvable name. Ensure the ports being used are free to use.

  2. Start service

$ docker-compose up

Wait until you see your creds printed.

New users and projects could be created via frontend app by default on http://localhost:8080

Success setup

Run VRT with logging enabled in Elasticsearch

This is for the users who want to monitor VRT logs via Kibana. It is expected to have basic knowledge of Elastic stack (especially Kibana) for the admin so that the logs can be managed and dashboards created in Kibana. Since logging will be retained by Elasticsearch, it will consume a little more memory and CPU. If you see error in the console, please consult Elasticsearch documentation.

It is recommended to run the program as root user which will ensure permission and ownership related issues will not have to be dealt with.

  1. Clone or download this repository.

  2. Move to the downloaded/cloned repository. In .env file, ensure that the REACT_APP_API_URL has the right address. If it will be accessed from other machines, change localhost with IP or other resolvable name. Ensure the ports being used are free to use.

  3. Follow either of below sub steps.

    • If your organization does not have Elasticsearch server running or if you want to start Elastic stack on your own, start service by giving below command.

      $ docker-compose -f docker-compose.yml -f docker-compose.elastic.logging.yml up

    • If you want to re-use the already running Elasticsearch server in your organization, go to filebeat/config/filebeat.yml and edit hosts to point to the Elasticsearch server. Also, point ELASTIC_URL to this server in .env file. Start service by giving below command.

      $ docker-compose -f docker-compose.yml -f docker-compose.logging.yml up

  4. If you are not using root user, in some OS, you may see an error Exiting: error loading config file: config file ("filebeat.yml") must be owned by the user identifier (uid=0) or root. In that case, press Ctrl+C, and follow Elasticsearch instructions. Once done, start the service again.

Integration

Use implemented libraries to integrate with existing automated suites by adding assertions based on image comparison. We provide native integration with automation libraries, core SDK and Rest API interfaces that allow the system to be used with any existing programming language.

Agents

Core SDK

Basic wrapper over API to be used for integration with existing tools

Getting started guide

Videos

Wiki

Integration examples

Here you could find examples

Contribution

  1. Try it, raise tickets with ideas, questions, bugs and share feedback :)
  2. More language support for SDK
  3. More integration with specific testing frameworks (agents)

Contributors ✨

Thanks goes to these wonderful people (emoji key):

Pavel Strunkin
Pavel Strunkin

πŸ’» πŸ’Ό πŸ€” πŸ”Œ
Daniel Crowe
Daniel Crowe

πŸ”Œ πŸ‘€
Surat Das
Surat Das

πŸ’» πŸ”Œ
Oleksandr Romanov
Oleksandr Romanov

πŸ”Œ
Terentev Denis
Terentev Denis

πŸ”Œ
JustSittinHere
JustSittinHere

πŸ”Œ
Dekara VanHoc
Dekara VanHoc

πŸ”Œ
maddocnc
maddocnc

πŸ’»
Aaron Chelvan
Aaron Chelvan

πŸ’» πŸ“–
marcm-qa
marcm-qa

πŸ”Œ
Eduard-iCH
Eduard-iCH

πŸ”Œ
Roman
Roman

πŸ’»
Dimitri Harding
Dimitri Harding

πŸ’»
vkostromin94
vkostromin94

πŸ”Œ
Bruno Ferreira
Bruno Ferreira

πŸ’»
Loïc PÉRON
Loïc PÉRON

πŸ’» πŸ”Œ
Alexey Volkov
Alexey Volkov

πŸ”Œ πŸ’»
Egor Lipskiy
Egor Lipskiy

πŸ”Œ
nitschSB
nitschSB

πŸ’»
polyvisual
polyvisual

πŸ’»
Juga Paazmaya
Juga Paazmaya

πŸ”Œ πŸ’»
Sebastian Weigand
Sebastian Weigand

πŸ’»

This project follows the all-contributors specification. Contributions of any kind welcome!