I'm feeling pretty confident about this one. The key is to identify the objective that's not directly related to the testing process itself. Gaining confidence in the system's fitness is more of an outcome than an objective of testing.
Okay, I've got this. Preventing defects, investigating and fixing them, and providing info for stakeholders - those are all valid testing objectives. The one that's not valid is gaining confidence that the system is fit-for-purpose. That's more about validation than testing.
Hmm, I'm a bit unsure about this one. I know testing is important, but I'm not totally clear on the different objectives. I'll have to think it through carefully.
I'm going with option A. Testers are like the superheroes of the software world - we don't prevent crime, we just swoop in and save the day when it's already happened!
Option A is clearly the odd one out. Preventing defects is the job of the developers, not the testers. We're here to catch what they missed, not stop them from making mistakes in the first place.
Definitely option A. Testing is all about finding defects, not preventing them. Developers should be doing that before the code even reaches the testing phase.
Rebecka
3 months agoSabra
3 months agoGail
3 months agoOcie
4 months agoRefugia
4 months agoTammy
4 months agoBobbie
4 months agoJuan
4 months agoCarlene
5 months agoMona
5 months agoCandida
5 months agoStephen
5 months agoLon
5 months agoDorothea
5 months agoChantell
1 year agoAnglea
1 year agoOdette
1 year agoRoyce
1 year agoMerissa
1 year agoHollis
1 year agoTracie
1 year agoValentine
1 year agoDerrick
1 year agoTiera
1 year agoAntonette
1 year agoNakita
1 year agoElizabeth
1 year agoTenesha
1 year agoBernardine
1 year agoIlona
1 year agoKip
1 year agoMaia
1 year agoJosphine
1 year agoBarney
1 year agoNicolette
1 year agoJunita
1 year agoGalen
1 year ago