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

% of total tests passed43%

% of critical tests passed37%

% of critical business flows passed29%

Project deadline is reached19%

Project budget is reached11%

Minimum acceptable defect rate is achieved11%

Go/No-Go meeting10%

Other1%

505 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

Is your business looking for a payment orchestration platform to have a single solution that can manage all your payment needs?

Yes65%

No34%

Are context engineering skills a high priority for your organization right now? How does that skill set compare to prompt engineering?

How do you encourage a peer who hasn’t been able to land a job due to ageism?

Read More Comments

What "tells" have you noticed for AI-generated text (i.e., typical words/phrases, or other patterns indicative of GenAI)?

Read More Comments

Have you seen a measurable improvement in developer productivity since adopting AI coding tools?

Yes, we’ve seen a marked improvement18%

Maybe, we believe productivity has improved but can’t measure it43%

No, we’ve seen little to no improvement29%

I’m not sure10%

We’re not using AI coding tools

View Results