Q: 1
The effect of testing is to:
Options
Discussion
A , since often testing is meant to raise the overall software quality. Think B's a trap here.
I get why A tempts people but testing alone doesn't raise software quality, it just tells you how good (or bad) things are right now. Pretty sure it's B since that's what ISTQB expects. Open to counterpoints if anyone thinks otherwise.
B , that's what the ISTQB official guide says about testing's main effect. Practice tests keep showing similar wording too, so pretty sure that's safest. Always worth checking the syllabus for this topic.
B . Testing just points out where quality stands, doesn't actually boost it by itself. A's a trap since quality only improves if defects found get fixed.
B tbh, testing just gives you a snapshot of quality. It doesn't guarantee software is bug-free or that quality actually goes up.
B imo, since testing just shows you the current quality, doesn't really improve it directly. That's what the syllabus focuses on. Could be wrong but that's how I remember it from the practice questions.
Seen this on lots of practice exams, always goes with B. The official guide makes it clear too.
Seriously, ISTQB loves to nitpick on 'effect' vs 'goal'. Anyone else get tripped up by this wording B.
This kind of wording is always confusing in ISTQB exams. A tbh, since when you run tests and find bugs, the whole process eventually boosts quality, right? The intention behind testing is to drive improvements, even if inspecting alone doesn't fix stuff. Maybe missing something in the official syllabus, but that's how it plays out in real life. Anyone else see it this way on practice tests?
I don’t think it’s B. A. Finding defects helps boost software quality, right?
Be respectful. No spam.
