Your testers find a critical bug the night before a major release. Should they have the power to stop the launch? Testers provide essential insights into software quality and risk. Their analysis is critical for decision-makers, so would it make sense to give them the power to veto releases?
In this insight, I explore:
- What does it mean to ‘block a release’
- Why tester analysis is vital
- Whether testers should be able to block releases
- How to ensure everyone has their finger on the pulse
What Does ‘Blocking a Release’ Really Mean?
To ‘block a release’ means to halt the deployment of software. This could be due to several factors, including those relevant to our discussion, such as quality or risk concerns.
Testers, with their deep technical knowledge and rigorous analysis, are often the first to spot issues that could impact users or business operations.
Their findings serve as key inputs for decision-makers—product owners, business stakeholders, and leadership—who must weigh technical risk against business needs.
A Real-World Horror Story – With a Twist
Years ago, I worked on an exciting new application that was rapidly approaching its go-live date.
Unfortunately, the system had significant performance issues, and many of us believed releasing it would be a disaster. Even more unfortunately, the business went ahead anyway.
The result? Months of strain, long hours, and a deluge of high-priority support tickets. Everyone on the project could see the glaringly obvious—Going live was clearly the wrong decision. If only the business had listened to the test team, they would have spared everyone months of grief and headaches.
Turns out, though, things were a little bit more complicated than they first appeared. A decade later, I learned the truth—Failure to go-live would have threatened the company’s survival.
The business stakeholders had to make a tough call; one that only they were equipped to make.
Testers Shouldn’t Have the Final Say
While testers are essential, the decision to release is fundamentally a business one.
It’s about balancing technical risk with commercial realities, timelines, and commitments. Even the most senior Head of Quality & Testing, skilled though they may be, doesn’t have the complete picture.
Tester Input Must Be Taken Seriously
That said, testers are the eyes and ears of the project and business stakeholders.
They provide unbiased, data-driven assessments of software readiness. When their input is valued and acted upon promptly, teams can address risks proactively, rather than reactively.
Test results are a source of unbiased and unfiltered truth. By focusing on testing insights and understanding key risks early, teams can prevent nasty eleventh-hour surprises.
How To Give Testing a Stronger Voice
Testers’ voices are strongest when backed by precise, accessible data, including metrics and dashboards that communicate risk in a language everyone understands.
Rather than only sharing test data at the end of phases, there needs to be complete transparency of test results and progress throughout the quality process. This ensures that issues are visible and can be addressed before go/no-go meetings.
By providing constant feedback loops, testers can help ensure that high-risk problems are addressed early, rather than left to fester until the last minute.
Decision Making is Easier With Test Management Tools
Modern test management tools, such as OpenText™ Software Delivery Management (formerly ValueEdge Quality/ALM Octane), are game changers.
These tools enable better decision-making by:
- Providing a single view of the truth
- Streamlining evidence capture
- Tracking and highlighting progress
- Making transparency the default setting
And most importantly, test management tools are always up to date; there’s no need to wait for a report to be produced. Everyone involved in the project and all stakeholders can always access a clear picture of the solution’s readiness.
Quality concerns are visible, documented, and thoroughly discussed well before release deadlines. Paving the way to an informed go/no-go decision.
Testers Shouldn’t Block Releases, But Should Enable Earlier and Better Decisions
Testers shouldn’t have the final say on releases, but their input is invaluable.
To keep your team on top of release readiness, invest in a robust test management solution such as OpenText™ Software Delivery Management.
It’s the best way to ensure your next release is not just a leap of faith, but a confident step forward and enables:
- Visibility and transparency
- Clear, defensible evidence
- Easy evidence capture and structured data
Ready To Make Better Release Decisions?
Explore OpenText™ Software Delivery Management and put your team in control of quality, risk, and readiness—every step of the way.
