# Risk Map

## Risk Map

TestBrain RiskMap is designed to assist the manual test team to prioritize which areas of the code to test.

RiskMap shows all commits for a specified period, their risk of containing at least one defect, and the functional areas of the code affected by each commit.

By showing the number of high-risk commits in each functional code area, RiskMap acts as a guide to prioritize which areas of the code to test first and how much time to spend testing each area.

The outer ring is a list of all commits, coded for risk:&#x20;

* <mark style="color:red;">Red</mark> for **high** risk,&#x20;
* <mark style="color:orange;">Orange</mark> for **medium** risk,&#x20;
* <mark style="color:green;">Green</mark> for **low** risk.&#x20;

The inner ring maps the commits to the functional areas of the code affected. Commits that affect multiple code areas are listed on the outer ring separately for each code area.&#x20;

In other words, if a commit affects 3 different code areas, the same commit will be shown in 3 separate places on the outer ring.

Code areas are colored to match the highest risk of any commit that touches that area. Code areas that are not shown in the inner ring have not been changed.

Give manual testers a Flash light in the dark to select a window of time and where to focus their Exploratory Testing!

<figure><img src="/files/6w6l1wmmpK8vuSm8bex4" alt="Riskmap to the bugs" width="563"><figcaption><p>Heat Map to the Bugs!</p></figcaption></figure>

By showing the number of high-risk commits in each functional code area, RiskMap acts as a guide to prioritize which areas of the code to test first and how much time to spend testing each area.


---

# 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.appsurify.com/management/risk-map.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.
