Step 7: Make a Go / No Go Decision Based on Quality Gate
Typically, this step is done by QA Manager/Architect or Engineering Manager.
The Code Changes Coverage threshold serves as a critical quality gate for your release, determining the minimum acceptable level of quality before promoting a build to production. Choose your quality gate wisely:
Soft Gate (recommended initially): Serves as a warning flag, allowing manual overrides based on gap analysis.
Hard Gate: The ultimate gatekeeper, automatically blocking builds below the threshold.
Learn how to add a new soft quality gate by watching the video tutorial.
Making the Call:
Analyze Coverage: Has your release reached the threshold?
Gap Exploration: If below, delve into the gaps. Are they non-critical? Proceed cautiously to production.
Critical Gaps: Address the gaps now or post-release?
Post-release: Create a dedicated backlog for swift resolution. Incorporated the backlog into the test automation process for new functionality and complete it after the release.
Delay the release: Prioritize quality, address gaps first.
Remember! While reviewing the coverage, it is advisable to exclude the Unit Tests coverage if it exists in your report, as it may create a false impression of complete functionality testing.
By following these steps, you can effectively utilize the data from the reports, make informed decisions about production readiness, and ensure that important test gaps are addressed promptly.
Evolving Gates:
After successfully implementing the soft quality gate for several releases and it becomes an essential part of your Go/No Go decision-making process, you can evaluate the possibility of integrating it into your automated gates. However, if you consistently proceed to production even when the quality level is below the gate, it may indicate that the automated implementation is premature for your organization.
Last updated