> 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/over-time-quality-improvement-guide/step-6-write-tests.md). # STEP 6: Write tests {% hint style="info" %} Typically, this step is done by QA / Automation Engineers / and other relevant individuals involved in test creation. {% endhint %} ### Bridging the Gap: Effectively Addressing Identified Test Gaps Comprehensive coverage is essential for ensuring software quality and resilience. However, **unaddressed test gaps** represent vulnerabilities waiting to be exploited. This guide empowers you to effectively address these gaps. #### **Step 1: Charting the Course:** * **Open your Test Gaps Report:** Remember that baseline you set? This report helps track progress! * **Focus on Specifics:** Narrow your field by choosing a single functionality, transaction, or feature to tackle. This makes tracking progress and prioritizing gaps easier. #### **Step 2: Prioritize Critically:** * **Download the CSV:** This goldmine of data lets you filter and focus on the most crucial gaps. * **Watch the Video Tutorial:** Learn how to filter effectively and zero in on high-priority areas. * **Tackle Criticals First:** By addressing these gaps first, you'll see a significant boost in overall coverage and quality. {% embed url="" %} #### **Step 3: Write and Refine:** * **Create New Tests (or Modify Existing Ones):** Fill those gaps! Ensure comprehensive coverage to strengthen your code's armor. * **Regenerate the Report:** After each checkpoint, see how far you've come with a fresh report. #### **Step 4: Communication is Key:** * **Utilize Code Labels:** They help testers and developers speak the same language, fostering clear communication. * **Consult When Uncertain:** Don't hesitate to ask the code contributor or Technical Architect for clarity on specific changes (The Test Gaps report provides information about the contributor associated with each method). #### **Step 5: Efficiency is Everything:** * **Multi-Gap Targeting:** One well-crafted test can often address multiple gaps simultaneously, maximizing your effort. * **Iterative Progress:** Focus on one functionality at a time until all critical areas are covered, gradually reaching your overall goal. This approach allows you to incrementally increase your overall code coverage and improve the quality of your software. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.sealights.io/knowledgebase/guides/quality-improvement/quality-improvement-solution-overview/over-time-quality-improvement-guide/step-6-write-tests.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.