What factors help your team decide that it's time to stop software testing for a release? Choose the top 3.

EngineeringRisk Management

% of tests executed/test coverage30%

% of requirements covered by testing/code coverage43%

% of total tests passed45%

% of critical tests passed38%

% of critical business flows passed30%

Project deadline is reached20%

Project budget is reached14%

Minimum acceptable defect rate is achieved12%

Go/No-Go meeting11%

Other1%

503 PARTICIPANTS
4k viewscircle icon2 Upvotescircle icon1 Comment
Sort by:
IT Manager in Constructiona year ago

I am really happy to see how some drivers like deadline and budget, at least for us, aren't the pilot of that stage but I believe (see for example the game industry...) the reality is different.

I found and I am pleased to share this useful article: https://testingmint.com/when-to-stop-testing-exit-criteria-in-software-testing/

Content you might like

Thoughts on self-healing applications? Any approaches or tools that look promising to you?

Does someone have advice on how they have balanced the risk/reward as it relates to introducing Open-Source Software to organization? My org is dipping its toe into the OSS world and the architecture and risk governance teams are looking to get ahead of these requests by coming up with policies and standards for OSS technology being brought into our environment. To clarify, this is not for software development and CI/CD pipelines, SDLC etc. This is for installing solutions that already exist out there (Zabbix, GreyLog, Prometheus etc.) into the organization's environment. We are looking to provide a balance on the obvious risk with the ability to move fast (like everyone else now).

What are the biggest technical challenges preventing organizations from being able to use their existing data to enable digital transformation?

Finding data and putting it to good use13%

Controlling the security and privacy of data45%

Understanding how data is currently being used20%

All of the above19%

None of the above1%

View Results

AI and Research in Marketing and Communications: How Are You Ensuring Quality and Truth Over Speed? As AI becomes embedded in our day-to-day marketing operations, from customer insight to content strategy, it’s clear we’re gaining speed and scale. But are we sacrificing veracity and quality of output in the process? One of the biggest challenges I'm seeing is the rise of hallucinated content in AI-generated research.   - How do we ensure AI systems are surfacing trustworthy, contextually accurate, and well-sourced information? - Are we building enough verification layers into our AI-driven content and research workflows? - And how are you educating teams (and execs) to challenge AI outputs, rather than accept them at face value? - What frameworks, tools, or governance models have you adopted to maintain integrity and depth in AI-led research and insight creation? - Have you had success (or struggles) balancing speed vs. substance in AI-powered strategies? Your thoughts, examples, and recommendations would be incredibly valuable in helping others try to navigate this shift responsibly.

As technology leaders, where are you seeing the most challenges or gaps?

Executive Support10%

Projects vs. Operations68%

Building a culture of Security15%

Team Completeness5%

View Results