doc.overops.com

OverOps Quality Gates

These are the six configurable OverOps quality gates that are designed to mark a build as unstable.

1. New Error Gate
This gate is used to check for any new errors in the build. This is critical to ensure no new errors are introduced into production. If any new errors are detected, the build will be marked as unstable.

2. Resurfaced Error Gate
This gate is used to check for any resurfaced errors in the build. This is critical to ensure a previously fixed issued does not find it way back into production. If any resurfaced errors are detected, the build will be marked as unstable.

3. Total Error Volume Gate
This gate is used to check the total number of errors for the build. If there is one unique error happening 15K times, then the total error volume would be 15K.

  • Example:
    If the value is set to 10K and after all test(s) are run, there are 15K total events, the build will be marked as unstable.

4. Unique Error Volume Gate
This gate is used to check the total number of unique errors for the build. If there is one unique error happening 15K times, then the total unique error volume would be 1.

  • Example:
    If the value is set to 10 and after the regression test(s) run, there are 12 unique events, the build will be marked as unstable.

5. Critical Exception Types Gate
This gate is used to identify new critical exceptions (you define) in your application. If any of the critical exceptions occur during your regression test(s), the build will be marked as unstable.

  • Example:
    • Values set in configuration: NullPointerException, IndexOutOfBoundsException, YourCustomException
    • Regression test(s) run and if any of the configured exceptions occurs, the build will be marked as unstable.

6. Increasing Errors Gate
This gate is used to compare an Active Time Window (either the current build as defined in the Deployment Name or the time set in the Active Time Window) to a Baseline Time Window. Once the windows are defined, the algorithm looks at several components to identify real issues.

Event Types

The following error types can appear in the result:

  • New - new errors that introduced to the build
  • Severe New - errors introduced to the build that are considered severe based on the regression parameters.
  • Regressions - existing errors that have increased but are not considered severe based on the regression parameters.
  • Severe Regressions - existing errors that have increases - existing errors that have increased that are considered severe based on the regression parameters.

Related Documentation

OverOps CI/CI Pipeline Integrations
Configuring the CI/CD Pipeline Quality Gates

Updated 6 days ago

OverOps Quality Gates


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.