Trakr is built with simplicity and ease-of-use in mind. However, there are many ways to get more out of the platform. We created the documentation portal for those looking to learn how to get more out of it or simply how to get started. The portal is being continuously updated so please make sure you check back often.
There are two primary ways to use Trakr:
- Manually through the web-based user experience
- Automatically through the Trakr API and third-party integrations
Trakr has an intuitive, simple web-based experience that guides you through the testing process. This is ideal for users with little or no technical knowledge or experience in quality assurance (QA) testing and automation. This is also useful if your deployment and DevOps process are mostly manual.
API and third-party integrations
If you already have an automated deployment process and a sophisticated DevOps pipeline (e.g. continuous integration testing, etc), you can leverage Trakr’s full suite of APIs to trigger visual testings during various stages of your deployment (e.g. pull request, pre-production deployment, and others). We are also actively working on direct integration with many DevOps platforms to make Trakr setup even easier.
The Trakr workflow is a simple 3-step process that can be easily incorporated into your DevOps flow.
Trakr takes screenshots of web pages provided by the user for different device breakpoints. (For example, desktop, tablet, mobile) The screenshots can be created manually through the user interface, scheduled or triggered through programmatically (through APIs).
2.Perform visual comparison testing
Trakr proceeds to compare screenshots taken and detects if there are visual changes detected. This again can be done manually through the web user interface, scheduled, or triggered programmatically through the API.
Finally, site owners, project managers, and other stakeholders can receive email or SLACK notification of the if visual changes are detected by the comparison.