> 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/test-gaps-analysis-report/how-to-generate-edit-the-report.md). # How to Generate / Edit the Report Watch the video tutorial to learn how to generate the report. {% embed url="" %}
What does the time range in the report represent? The time range in the report captures all the builds that have been reported to SeaLights within that specified range. It's important to note that the time range does not directly correspond to when the tests were executed. This means that tests can be executed outside of the specified time range, yet their coverage will still be included in the report. The time range serves as a reference point for aggregating the relevant builds and their associated test coverage data, providing a comprehensive view of your testing efforts.
What are Code Labels for? Code labels are essential for organizing and filtering your data in SeaLights. When you apply code labels to an app or specific parts of the app, it allows you to focus on those labeled areas in SeaLights reports. This helps you obtain coverage and gaps data for specific, targeted sections of your codebase. If you are already familiar with code labels and using them on the apps you are examining, make sure to include the relevant labels when generating your report. By doing so, you can refine your analysis and gain more valuable insights into the quality of the labeled areas in your code. For more details about code labels and how to use them effectively, refer to the upcoming pages.
Generating the Test Gaps report may take a few minutes, as it depends on the size of your codebase and the number of tests in your project. The report needs to analyze and identify untested code changes, which can take some time to process. However, once the report is ready, you'll have valuable insights into the areas that require testing attention, helping you prioritize your efforts and improve your software's quality. --- # 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/test-gaps-analysis-report/how-to-generate-edit-the-report.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.