> For the complete documentation index, see [llms.txt](https://docs.7ft10.com/flow-system/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.7ft10.com/flow-system/topics/quality/risk-based-testing.md).

# Risk-Based Testing

{% hint style="success" %}
***We use this to** ... **so that we can** ...*
{% endhint %}

## Analyse

Analyse all Stories for the sprint and assess what Business functions/areas will be affected by them 

Populate the risk table with what you have identified 

## Question

As a team, run through the risks asking the questions, If we did not test this change what would be the likelihood of something going wrong? If something did go wrong what would the damage to the business be? 

Table is populated with team assessment, and risk rating is applied to each story/change 

## Sort 

Sort the stories/changes by risk, with the highest at the top.

Table is sorted by highest rated risks.

## Mitigate 

As a team work out how the risks will be mitigated, starting with the highest-rated risks first.

Make notes on what will be done to mitigate the risk. For example, Run existing tests, Write new Tests, Peer Review of code.

## Prioritise

The Completed list should now be used as a prioritised list of work for the sprint.

Start writing/executing tests based on the priority