Quality Gate

Learn how to use Quality Gate in Test Observability.

All engineering teams want to move faster, but when it comes to promoting code from one environment to another, or merging code - quality engineering teams need confidence. Verifying your builds can be a daunting task - multiple tests can fail, with many false negatives and inconsequential failures delaying the entire development cycle.

BrowserStack addresses this challenge with Quality Gate in Test Observability, a tool designed to automate the verification of builds and help users automate PR merges and deployments, and set quality standards.

How does Quality Gate work?

Users can configure a number of Quality Profiles containing rules.
The Quality Gate analysis will automatically be run once a build is complete, with the active Quality Profiles configured for that build.
Once the Quality Gate finishes calculating, users can instantly see the Profiles and Rules that have passed and failed for a build by navigating to their build.
Users can also easily integrate the Quality Gate status into their CI/CD or SCM tooling for automation.

Use Cases of Quality Gate

The Quality Gate can be implemented in multiple ways to suit your organizational needs:

Choose to allow a deployment if all your P0/P1 test cases pass, but a few P2/P3 test cases fail.
An instant roll-back tool if tests are breaking in Production.
Set organization-wide standards on flakiness, test performance and more.
Set thresholds for different failure categories from test results, like Product Bugs, Automation Issues, Network Issues and more - all powered by our ML-powered auto failure analysis.
Ensure that a minimum number of tests ran (especially your critical tests) before allowing any code to be merged.