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 coverage30%

% of requirements covered by testing/code coverage43%

% of total tests passed45%

% of critical tests passed38%

% of critical business flows passed29%

Project deadline is reached21%

Project budget is reached14%

Minimum acceptable defect rate is achieved12%

Go/No-Go meeting11%

Other1%

505 PARTICIPANTS
4k 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

Do you think Low Code / No Code platforms will result in fewer developer jobs?

Yes49%

No46%

Unsure3%

View Results

Do you accept payments in crypto currency?

Yes, we do today.10%

No, but we plan to in the next 6 months.34%

No, but we plan to further in the future.10%

No, and we have no plans to.44%

View Results

What are the fundamental leadership capabilities that are needed for an era of exponential technology and AI innovation?

Read More Comments

Do you find it hard to say no to unreasonable requests for your software team? How do you frame your “no” so it doesn’t cause problems with the team making requests?

Read More Comments

How are you diversifying threat intelligence sources? Have you been able to reduce reliance on CISA for TI?