> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/guides/quality-improvement/quality-improvement-solution-overview/release-quality-improvement-guide/step-7-make-a-go-no-go-decision-based-on-quality-gate.md). # Step 7: Make a Go / No Go Decision Based on Quality Gate {% hint style="info" %} Typically, this step is done by QA Manager/Architect or Engineering Manager. {% endhint %} 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. {% embed url="" %} **Making the Call:** 1. **Analyze Coverage:** Has your release reached the threshold? 2. **Gap Exploration:** If below, delve into the gaps. Are they non-critical? Proceed cautiously to production. 3. **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. {% hint style="info" %} 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. {% endhint %} 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. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.sealights.io/knowledgebase/guides/quality-improvement/quality-improvement-solution-overview/release-quality-improvement-guide/step-7-make-a-go-no-go-decision-based-on-quality-gate.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.