Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

ISTQB CTFL-Foundation Exam - Topic 1 Question 46 Discussion

Actual exam question for ISTQB's CTFL-Foundation exam
Question #: 46
Topic #: 1
[All CTFL-Foundation Questions]

When is testing complete?

Show Suggested Answer Hide Answer
Suggested Answer: B

Sometimes time/money does signify the end of testing, but it is really complete when everything that was set out in advance has been achieved.

Testing is considered complete when sufficient information has been gathered to assess the quality of the software and to make an informed decision about its release. This includes understanding the risks of any remaining defects, the test coverage achieved, and the test results. It is not practical to wait until all possible test cases have been executed or until no defects remain, as these conditions are often impossible to meet within typical project constraints.


Contribute your Thoughts:

0/2000 characters
France
1 day ago
D sounds impossible, right? How can you test everything?
upvoted 0 times
...
Janae
6 days ago
C is definitely a must before release.
upvoted 0 times
...
Malcolm
11 days ago
A is just a recipe for disaster!
upvoted 0 times
...
Lera
17 days ago
I think B makes the most sense.
upvoted 0 times
...
Cheryll
22 days ago
B) When there is enough information for sponsors to make an informed decision about release. This is the most practical answer.
upvoted 0 times
...
Bev
27 days ago
A) When time and budget are exhausted. Sounds about right for most projects I've worked on.
upvoted 0 times
...
Mi
2 months ago
D) When every data combination has been exercised successfully. Haha, good luck with that! Testing is never really complete.
upvoted 0 times
...
Tamar
2 months ago
C) When there are no remaining high priority defects outstanding. This is the only correct answer in my opinion.
upvoted 0 times
...
Winifred
2 months ago
B) When there is enough information for sponsors to make an informed decision about release.
upvoted 0 times
...
Francis
2 months ago
I’m torn between B and C. I know we need to address high priority defects, but what if we have enough info for a release?
upvoted 0 times
...
Stephanie
2 months ago
I feel like testing can't be complete just because time and budget are up. That seems too risky, right?
upvoted 0 times
...
Casie
2 months ago
I remember a practice question that emphasized the importance of high priority defects. So, maybe option C is the right choice?
upvoted 0 times
...
Aja
3 months ago
I think testing is complete when we have enough information for sponsors to make a decision, but I'm not entirely sure.
upvoted 0 times
...
Cory
3 months ago
B seems like the best answer to me. Testing is about providing the right information to decision-makers, not just checking boxes or running out of time. That's a good strategy to keep in mind for this type of question.
upvoted 0 times
...
Desire
3 months ago
I'm a little confused on this one. I was leaning towards D, since thorough testing should cover all possible scenarios. But I can see the logic behind B as well. Guess I'll have to think it through more.
upvoted 0 times
...
Bong
3 months ago
I'm pretty confident the answer is B. The point of testing is to assess the product's readiness, not just to check every possible data combination or run out of resources.
upvoted 0 times
...
Kaycee
3 months ago
Hmm, I'm not sure. I was thinking C might be the right answer, since we want to make sure there are no critical issues before release. But B also makes sense.
upvoted 0 times
...
Jesusita
3 months ago
I think the answer is B. The goal of testing is to provide enough information for stakeholders to make an informed decision, not just to run out of time and money.
upvoted 0 times
...

Save Cancel