Option A is clearly the best answer. If you haven't discovered every single bug in the program, then the testing is not complete. Anything less is just a waste of time. (Psst, hey Jannette, I heard you're using magic to test your code. Want to share your secrets?)
I'm going to have to go with Option B on this one. Testing every possible path in the code is the only way to be truly confident that the software is bug-free. Unless you're using magic, of course.
Option D is the way to go. If you've completed every test in the test plan, then the testing is complete, regardless of whether you found any bugs or not. Simple as that!
Option D is the way to go. If you've completed every test in the test plan, then the testing is complete, regardless of whether you found any bugs or not. Simple as that!
I'm not sure I agree with that. Reaching the scheduled ship date is the true definition of complete testing - who cares about bugs as long as the software ships on time, right? (just kidding, that's a terrible answer).
Option B seems the most accurate definition of complete testing. Testing every statement, branch, and combination of branches is the ideal way to ensure thorough coverage.
Vashti
4 months agoCorinne
2 months agoLacresha
2 months agoLaurel
2 months agoLoren
2 months agoKristeen
2 months agoGianna
3 months agoJaclyn
3 months agoGeorgiana
3 months agoKayleigh
3 months agoJannette
4 months agoBernardo
3 months agoDorsey
4 months agoTasia
4 months agoGilma
4 months agoEun
4 months agoKirk
4 months agoKenneth
3 months agoTrinidad
3 months agoFernanda
4 months agoMakeda
4 months agoTasia
4 months agoMaryann
4 months agoOlene
4 months agoDenae
4 months agoBrittani
5 months agoHannah
4 months agoMadelyn
5 months ago