Do you delete tests as part of your testing strategy?

Now people have time to reflect on the Crowdstrike incident, discussing parasite paradoxes, watermelon tests, shift right and left…we wonder.

  • Yes
  • No
0 voters

:wastebasket: Bonus points for sharing why.

3 Likes

I test what ever is reasonable.
Sometimes I take over notes/plans/designs from previous testing in the same area.

What you mean by ‘tests’ here? Some types of artifacts? Approaches of testing?
I find the term ‘test’ very ambiguous. For me its mostly an activity.
Do you maybe mean test cases like at execution automation or manual execution?

5 Likes

We just actually deleted an automated test (or automated check, if you prefer), due to the conditions for it no longer applying to the application.

Basically, we created it to capture a bug a few years ago, but now the path to that bug is effectively no longer possible…but maintaining the test was causing headaches and taking time away from developers and testers that could be put to better use.

1 Like

I’m not sure I’ve ever truly deleted a test.

Sometimes I’ve marked them so they don’t get run, or perhaps they would only get run on older versions of the software, which are no longer supported.

Maybe I’m a test hoarder, I never throw anything out :wink:

4 Likes