When do you stop testing? 🤔

QA-Talk
1

We talk a lot about when testing is “done”…

But sometimes the real skill is knowing when to stop testing before you finish the plan.

A few situations where I’d seriously consider it:

1. Too many bugs :police_car_light:

If everything is breaking, the system isn’t ready for deep testing. Run a quick sanity on the critical areas, give high-level feedback… and stop. You’ll retest it all anyway after fixes.

2. Nothing interesting :zzz:

You’ve covered a good chunk and found… nothing meaningful. Maybe it’s stable. Maybe you’re just burning time. Sanity check the key flows, review risk with the team, and move on.

3. You won’t make the deadline :hourglass_not_done:

If you already know you won’t finish, ask: does it even matter? If release isn’t moving, shift your effort to where it actually helps.

Stopping testing isn’t failure. Sometimes it’s the most professional decision you can make.

I’m curious, when do you stop testing (if at all)?

Where do you disagree?

1 Like
2

100% agree with point #1.

In one case I’ve seen, testing slowed down significantly due to repeated release delays after defects were uncovered during early-stage testing.
In another case, high-priority production bugs had been patched multiple times but remained unstable, blocking further progress.

In that kind of situation, continuing to push testing forward doesn’t add much value while releases are effectively on hold.

1 Like
3

Yup… and then another issue shows up, people who start “blaming” testing for delaying the release.

Have you seen this happening in these cases as well?