Why I ask this question: Sometimes, that final release decision became really critical for testers to make: to ship on time or to hold back for quality. So I would love to hear stories from you, what happened when you raised the flag and stand on a product bug: how did your team respond? I would r…

Yes, I’ve been in that situation. Once during a release, everything looked fine until the final round of sanity checks when we stumbled upon a critical bug in the search filters; users could search, but the filters weren’t working at all. Imagine going live with an web app where customers can’t na…

It’s not the tester’s job to decide whether to launch or not, and they should not do so. In most cases there will be a product owner or project manager, and it’s their responsibility. The tester’s role is to provide them with information such as known issues, unknown factors, risks and consequences.…

100% with you. Our role as testers is being an advisor. “I’ll be you, I wouldn’t do it. But I’m not you and it’s fine.” We are the providers of confidence. We don’t green or red light but we help people doing it to do their job with the right amount of information.

I’ve never personally stopped a release. It should never be on one person to stop a release. But we do share information that we know is highly likely to have one outcome. This has happened more than once but this is when the relationships that we build are vital. It lets me share what I’ve found, …

From around 2005 to 2011, I worked at two companies where it was our role as the QA team to make the final release call. We’d release every two weeks. And often we’d stop the release due to an unexpected major bug. While many folks baulk at that approach, looking back on it now, we were probably be…

Yes! The details are too specific to share on a public forum, but it was a critical bug hard to reproduce in the test environment. I was working from home on that day, and I called the PO immediately after the discovery. They decided to postpone the release.

Something similar to this: [image] How would you handle a critical bug found just before release? shooting_starDiscussions This has happened few times actually, not anymore thankfully. If you are the person who signs off the release so decision is on you & and…

Simon, did you have any visibility of the other factors that should be taken into account in a release decision, such as all the business factors? It’s inconceivable that quality was the only factor taken into account. Even releasing without all the planned new features isn’t a decision testers shou…

I was working as developer in a government project where we were renewing competitive bidding system for public sector. Near the deadline of the project we noticed one area of the new application was really broken, not just one or two bugs but multiple issues here and there and the development team …

would it have been possible to disable that specific feature for the 2 months?

Have you ever stopped a release because of an unexpected bug, found at the last minute?

Discussions

aimantirmizi (Aiman B T Syed) 15 September 2025 09:37 8

Something similar to this:

Topic		Replies	Views
How would you handle a critical bug found just before release? Discussions tools , learning , automation	5	585	6 August 2025
How do you define a release blocker? Discussions learning , process , quality , bugs , bug-reporting	8	384	9 October 2024
Release with the known issues dilemma Archive	6	746	24 May 2018
"sign off" from testers? Or others? Discussions learning , process	9	185	18 May 2025
Go / No Go - criteria Archive process , requirements	7	1681	30 June 2021

Have you ever stopped a release because of an unexpected bug, found at the last minute?

Related topics