# Release Go / No Go Report SeaLights provides a holistic view of the project's code coverage, including insights into the testing of individual user stories across various testing stages. * **Holistic quality view:** The report provides a comprehensive overview of the testing process, enabling you to track the progress of individual user stories across various stages. * **Data-driven coverage metrics:** SeaLights delivers clear and data-driven metrics, aggregated across all testing stages. You can also distinguish between unit tests and other test types. * **Release with confidence:** With the insights provided by the report, you can eliminate guesswork and make informed decisions about the release of user stories and features. {% hint style="info" %} #### Primary Users Ideally suited for **managers** to make informed release decisions for projects, features, and user stories. {% endhint %} *** {% embed url="" %} A glimpse of Release Go / No-Go report {% endembed %} ### **Centralized Insights: Code Coverage Data Hub for Go/No-Go Decisions** The Release Go / No-Go Report serves as a centralized hub for gathering and analyzing code coverage data, providing a holistic view of the project's overall code coverage status. It seamlessly integrates information from user stories, their corresponding code changes, and the associated code coverage metrics, offering granular insights at the level of each user story and its code changes. A typical workflow with the addition of SeaLights ### **The Value of Non-Unit Tests Coverage** Going beyond simple overall coverage percentages, the report delves into non-unit test coverage metrics, which are crucial for comprehensive testing. Non-unit tests, such as integration, functional, and end-to-end tests, play a vital role in verifying the functionality and behavior of software. This granularity is crucial, as high overall coverage percentages based solely on unit tests can sometimes paint an incomplete and misleading picture of the true code coverage landscape. This granular analysis is particularly valuable for identifying potential hotspots where undetected defects may lurk. By focusing on non-unit tests, which often target more complex functionalities, teams can proactively address these areas and enhance the overall quality of the software. ### Scannable Insights at a Glance To facilitate rapid evaluation of code coverage within our User Story Coverage Report, we implemented intuitive color indicators: * Red: Attention needed, coverage less than 20% * Orange: Room for improvement, coverage between 20% and 70%. * Green: Well-covered, exceeding 70% coverage. These color indicators can be customized to suit specific project requirements. Additionally, methods marked as critical will appear red if they have not been tested by any test type, or orange if they have not been tested by any non-unit test type. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.sealights.io/knowledgebase/guides/user-story-coverage/user-story-coverage-report-overview/release-go-no-go-report.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.