Q: 8
What if the project isn't big enough to justify extensive testing..?
Options
Discussion
Option B, had something like this in a mock. Risk-based analysis is ISTQB's default for small projects.
Makes sense to go with B here. Risk-based analysis helps focus testing effort where it matters most if time or size is limited, rather than automating everything. Pretty sure this is what ISTQB stresses.
B. not C. Automation is often a trap for small projects since setup overhead isn't justified, ISTQB wants risk-based picks here.
I don’t think automation (A) makes sense for a small project. Usually ISTQB expects us to pick B, risk-based analysis, since it helps focus testing where it matters. A is a trap if you go by cost-benefit. Open to thoughts if anyone's seen something different in the syllabus!
B tbh, similar question popped up in a recent mock exam and risk-based was marked correct.
C tbh
C , ISTQB loves their risk-based analysis stuff but in practice, automation can actually help even with small scope if you reuse scripts or need quick regression. Always feels like exam questions ignore real project realities. Maybe it's just me.
B , seen risk-based testing mentioned a lot in the official guide and practice exams for this scenario.
B . Official syllabus and example tests all stress risk-based first for this setup.
B tbh. If a project is too small, automation (A) probably doesn’t make sense unless you have repeat tests or big regression needs, which isn’t common for tiny projects. Risk-based analysis (B) is the way ISTQB pushes in these edge cases since it helps you cover only what matters. Somebody might argue for C if the scenario had more about reusability or long-term maintenance.
Be respectful. No spam.
