Quality gate rules are checkpoints that make sure only work items that meet your
quality criteria move to the next pipeline stage. Use quality gate rules to maintain code
quality, ensure reliable deployments, and identify issues early in the application lifecycle.
When a quality gate rule fails, you can analyze the reason and resolve any issues before
attempting to promote the work item again.
Required Editions
Available in: Lightning Experience
Available in: Enterprise, Performance, Professional (API
access required), Unlimited, and Developer Editions
Quality gate rules use any of these criteria:
Severity level threshold – If any test with a severity equal to or higher than the
threshold fails, the quality gate rule fails. For example, if the severity threshold is set
to 3, test failures of severity 1, 2, or 3 cause this quality gate rule to fail.
Test pass percentage – If the overall test pass rate is below the set percentage, the
quality gate rule fails. For example, if the test pass percentage is 90% and fewer than 90%
of the tests in the test suite pass, this quality gate rule fails.
Check for essential test failures – If any test fails that's marked as essential, the
quality gate rule fails.
You can assign quality gate rules to each test suite assigned to a pipeline stage. When a
work item is promoted, DevOps Testing runs the test suites and evaluates the quality gate
rules. If all quality gate criteria are met, the work items containing the changes are moved
to the next pipeline stage. If any criterion isn't met, the test suite run automatically
fails.
Create a Quality Gate Rule Create a quality gate rule based on your testing goals. We recommend establishing criteria that are realistic yet strict enough to maintain quality.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.