# Is test case management dead?

**URL:** <https://club.ministryoftesting.com/t/is-test-case-management-dead/84370>\
**Category:** Discussions\
**Tags:** polls, test-case-management, is-it-dead-yet\
**Created:** [23 April 2025 11:32 UTC](https://club.ministryoftesting.com/t/is-test-case-management-dead/84370 "2025-04-23T11:32:43Z")\
**Posts on this page:** 1\
**Showing post:** 32

<div class="post-metadata">

**Author:** ![kristof](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/kristof/32/10839_2.png) [@kristof](https://club.ministryoftesting.com/u/kristof)\
**Post date:** [14 May 2025 06:11 UTC](https://club.ministryoftesting.com/t/is-test-case-management-dead/84370/32 "2025-05-14T06:11:52Z")

</div>

> [@andrewkelly2555](#):
>
> I’ve felt in the past that it often became a managers people management tool rather than a test management tool.
> 
> Often used to address trust issues and put more emphasis on evidence of testing rather than good testing which in turn added gamification to the testing and changed its focus.

I totally agree, I’m currently in a big hierarchy company 😕  
But currently our teams either have: no test scenario’s/cases or very very poorly documented and if they are absent, nobody knows what to test (since other people have to step in but have either: no product knowledge or don’t know how to test).

Then again, currently there is no single overview of what which team or tester is doing. It’s not our intention to control people but more like, what if someone gets sick. Because they only know their own application and cannot help on other projects.

> [@andrewkelly2555](#):
>
> I do though recognise that it can often be a trust problem particularly when something goes wrong and someone want’s proof of testing, they are then not interested in that proof at all until the next time something goes wrong.

For each release to prod, we have to submit proof of testing, which now is … well either an email saying “sure/GO” or “Our tester did everything” without any legit proof of testing. Or without any knowledge of the tester… since this is asked to the scrum master and sometimes not even consulted with the tester (… but that’s a different problem 😃 )

* * *

One of the main problems is architecture, they made changes I don’t even dare to explain since they are so bad for quality & testing (literally pushed back testing by 3-6 WEEKS PER RELEASE) . So yea for me there are a whole lot of reasons that our team wants this.

One of the reasons I wanted to do this: [The unbelievable Powerpoint?](https://club.ministryoftesting.com/t/the-unbelievable-powerpoint/84066)

---

_[View the full topic](https://club.ministryoftesting.com/t/is-test-case-management-dead/84370)._