# STEP 3: Prioritize Code Areas

{% hint style="info" %}
Typically, this step is done by QA Manager and the related Engineering Manager / Dev Team Lead / Tech Architect.
{% endhint %}

Facing a mountain of untested code changes within limited time? Don't despair! Smart prioritization is key to conquering these gaps efficiently. By focusing on a **subset** of your codebase, you can achieve **swifter progress** and **maximize the impact** of your testing efforts.

Breaking down the workload into **manageable chunks** allows you to address **high-priority areas first**. This targeted approach not only yields **faster results** in closing the gaps but also enhances your confidence in the overall **stability and reliability** of your software.

Remember, effective prioritization isn't just about completing tasks; it's about **strategically** **allocating** your **resources** for maximum impact.

***

There are several effective ways to prioritize code areas:

1. [**Add Code Labels**](/knowledgebase/guides/quality-improvement/quality-improvement-solution-overview/over-time-quality-improvement-guide/step-3-prioritize-code-areas/add-code-labels.md): Apply code labels to mark critical areas of your codebase, helping you create a subset of code that requires immediate attention.
2. [**Ignore Irrelevant Code**](/knowledgebase/guides/quality-improvement/quality-improvement-solution-overview/release-quality-improvement-guide/step-3-prioritize-code-areas/ignore-irrelevant-code.md): Exclude parts of your code that are not pertinent to the testing process. By focusing solely on the relevant sections, you can streamline your testing efforts.
3. [**Perform a Deep CSV Analysis**](/knowledgebase/guides/quality-improvement/quality-improvement-solution-overview/release-quality-improvement-guide/step-3-prioritize-code-areas/perform-a-deep-csv-analysis.md): Conduct a detailed analysis using a CSV file to gain more in-depth insights into the test gaps and identify high-priority areas.

We highly recommend starting with the implementation of code labels as the first step to create a subset of your code.


---

# 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/quality-improvement/quality-improvement-solution-overview/release-quality-improvement-guide/step-3-prioritize-code-areas.md?ask=<question>
```

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.