> 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/proof-of-testing-report/how-to-generate-edit-the-report.md).

# How to Generate / Edit the Report

Track code coverage changes and optimize your testing strategy with the Proof of Testing Report.

{% embed url="<https://youtu.be/dzSBI7CaU9o>" %}

### **Here's how to get started**

1. Navigate to the SeaLights Quality Analytics tab in your SeaLights account.
2. Open the Proof of Testing page and Click the "Create New Report" button.
3. **Define your scope:**
   * **Time Range:** Choose a specific timeframe (e.g., last month, custom dates). It is common to select the last month as the time range.
   * **App & Service:** Select the app and service you want to track.
   * **Branch:** Specify the relevant branch.
   * **Test Stages:** Choose the test stages to include in your analysis.

### **Gain valuable insights**

* **Aggregated Coverage:** View the overall distribution of coverage across your chosen test stages.
* **Identify Gaps:** Easily pinpoint areas needing more attention based on test stage contributions.
* **Targeted Analysis:** Explore specific uncovered areas through direct links to Test Gaps Reports.

{% hint style="info" %}
**Remember:** Reports may take a few minutes to process depending on your codebase and test volume.
{% endhint %}


---

# 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/proof-of-testing-report/how-to-generate-edit-the-report.md?ask=<question>&goal=<user_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.
