# Visualising levels of testing to identify areas for test to explore

**URL:** <https://club.ministryoftesting.com/t/visualising-levels-of-testing-to-identify-areas-for-test-to-explore/12274>\
**Category:** Archive\
**Tags:** exploratory-testing\
**Created:** [21 December 2017 23:14 UTC](https://club.ministryoftesting.com/t/visualising-levels-of-testing-to-identify-areas-for-test-to-explore/12274 "2017-12-21T23:14:36Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![a\_miller](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/a_miller/32/5669_2.png) [@a\_miller](https://club.ministryoftesting.com/u/a_miller)\
**Post date:** [21 December 2017 23:14 UTC](https://club.ministryoftesting.com/t/visualising-levels-of-testing-to-identify-areas-for-test-to-explore/12274/1 "2017-12-21T23:14:36Z")

</div>

Hi, When working with suites of automated unit, platform, CDC, Service & User Journey tests in a continuous delivery environment and tasked with understanding what is automated at different levels to identify what additional testing, further automation or exploration is required/not required/desirable. Has anyone seen any concise ways of visualising existing automated tests against new tests?

---

<div class="post-metadata">

**Author:** ![rforjoe](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/rforjoe/32/111_2.png) [@rforjoe](https://club.ministryoftesting.com/u/rforjoe)\
**Post date:** [15 May 2023 23:48 UTC](https://club.ministryoftesting.com/t/visualising-levels-of-testing-to-identify-areas-for-test-to-explore/12274/2 "2023-05-15T23:48:22Z")

</div>

Curious to know if you ever got this. answered somewhere?

---

<div class="post-metadata">

**Author:** ![conrad.connected](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/conrad.connected/32/10123_2.png) [@conrad.connected](https://club.ministryoftesting.com/u/conrad.connected)\
**Post date:** [16 May 2023 03:02 UTC](https://club.ministryoftesting.com/t/visualising-levels-of-testing-to-identify-areas-for-test-to-explore/12274/3 "2023-05-16T03:02:49Z")

</div>

This feels like a necro @rforjoe , but the working of the question is so cool and clear to me too. Can I use a “workflow” tracking tool to measure manual-vs-automated “test coverage” in one easy to compare and view pane of glass that looks into all of my “system” tests? Is what I read.