Q: 8
What if the project isn't big enough to justify extensive testing..?
Options
Discussion
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 . 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.
B
If the project is too small for full-blown testing, B is best. Risk-based analysis lets you focus on what’s critical instead of testing everything. Automation (A) often isn’t worth it unless there’s repeat value or lots of tests to run, which isn’t usually the case in small projects. I’m pretty sure ISTQB wants B here, unless they mention needing speed or coverage above all else. Disagree?
I don’t think automation is the main focus here, C feels like a trap. B.
It’s B, automation (A) is tempting but risk-based analysis fits ISTQB logic for scoped projects. C is a common trap here.
Option B
Be respectful. No spam.
