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

Applications & PlatformsEngineering

% of tests executed/test coverage28%

% of requirements covered by testing/code coverage41%

% of total tests passed42%

% of critical tests passed36%

% of critical business flows passed31%

Project deadline is reached21%

Project budget is reached12%

Minimum acceptable defect rate is achieved12%

Go/No-Go meeting11%

Other1%

503 PARTICIPANTS
4.1k viewscircle icon2 Upvotescircle icon1 Comment
Sort by:
IT Manager in Construction2 years 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

Which tech conference do you intend to attend in person next year or have already participated in this year, and what motivated your choice?

Read More Comments

Is your organization using AI for vulnerability scanning or bug hunting?

Yes85%

No15%

I'm looking for an Application Assessment guide for Cloud Adoption. More like a decision tree which will help determine the best possible path to take an on-prem solution to the cloud. Has anyone developed such a tool?

We’re seeking recommendations for vendors that provide robust transaction reporting solutions for regulatory compliance across regimes such as EMIR, MiFIR, ASIC, SFTR, and Singapore. If you’ve worked with providers like Kaizen, Novatus, or others, we'd appreciate your insights.

When will SBOMs (software bill of material) become standard practice?

Less than 1 year29%

1-2 years24%

2-3 years27%

3-4 years7%

4-5 years3%

More than 5 years3%

Not sure4%

View Results