# How do you capture risks?

**URL:** <https://club.ministryoftesting.com/t/how-do-you-capture-risks/64460>\
**Category:** Discussions\
**Tags:** exploratory-testing, risks, heuristics, oracles\
**Created:** [12 January 2023 12:45 UTC](https://club.ministryoftesting.com/t/how-do-you-capture-risks/64460 "2023-01-12T12:45:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![simon\_tomes](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/simon_tomes/32/14009_2.png) [@simon\_tomes](https://club.ministryoftesting.com/u/simon_tomes)\
**Post date:** [12 January 2023 12:45 UTC](https://club.ministryoftesting.com/t/how-do-you-capture-risks/64460/1 "2023-01-12T12:45:41Z")

</div>

I recently enjoyed reading @darktelecom’s article on [using risks to guide Exploratory Testing](https://docs.getxray.app/display/XEA/Using+risks+to+guide+Exploratory+Testing). I like the way it provides practical examples. It’s full of useful advice! Do check it out.

Got me thinking about how I would capture risks before capturing charters to explore. One approach a colleague and I developed — whilst working on a product called TestBuddy – was called “Risks and Questions”. It starts by capturing the value of the thing you’re about to test. Have a look at [this YouTube video](https://youtu.be/Wu4xTnoreLY) if you’re interested to learn more about the simple technique.

How about you – how do you capture risks? What do you do with them? What advice can you share when it comes to thinking in terms of risks and testing?

---

<div class="post-metadata">

**Author:** ![darktelecom](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/darktelecom/32/4957_2.png) [@darktelecom](https://club.ministryoftesting.com/u/darktelecom)\
**Post date:** [12 January 2023 15:56 UTC](https://club.ministryoftesting.com/t/how-do-you-capture-risks/64460/2 "2023-01-12T15:56:36Z")

</div>

Thanks for mentioning @simon_tomes . I also be interested on knowing how others depict risks for their exploratory testing, if you follow a process or if it’s something mote unstructured.