Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

ISTQB CTFL-Foundation Exam - Topic 5 Question 23 Discussion

Actual exam question for ISTQB's CTFL-Foundation exam
Question #: 23
Topic #: 5
[All CTFL-Foundation Questions]

Which of the following is NOT a valid objective of testing?

Show Suggested Answer Hide Answer
Suggested Answer: D

by Leota at Sep 19, 2024, 08:23 AM

Limited Time Offer

25%

Off

Get Premium CTFL-Foundation Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Rebecka
6 months ago
Gaining confidence in the system is super important, for sure!
upvoted 0 times
...
Sabra
6 months ago
Wait, are we really saying preventing defects isn't a goal? That seems off.
upvoted 0 times
...
Gail
6 months ago
Definitely agree with option D being a key objective.
upvoted 0 times
...
Ocie
7 months ago
I think preventing defects is a valid goal too!
upvoted 0 times
...
Refugia
7 months ago
Testing is all about finding defects, not preventing them.
upvoted 0 times
...
Tammy
7 months ago
I recall discussing that gaining confidence in the system's purpose is definitely a valid objective, so maybe it's A after all.
upvoted 0 times
...
Bobbie
7 months ago
I feel like option D could also be a contender, but I think providing information for stakeholders is important too.
upvoted 0 times
...
Juan
7 months ago
I'm not so sure about that. I remember a practice question where preventing defects was considered a key objective.
upvoted 0 times
...
Carlene
8 months ago
I think option A might be the one that doesn't fit, since testing usually happens after code is written.
upvoted 0 times
...
Mona
8 months ago
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.
upvoted 0 times
...
Candida
8 months ago
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.
upvoted 0 times
...
Stephen
8 months ago
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.
upvoted 0 times
...
Lon
8 months ago
This question seems straightforward. I'll carefully read through the options and eliminate the ones that are valid objectives of testing.
upvoted 0 times
...
Dorothea
8 months ago
I remember discussing usability testing techniques like inspections and evaluations, so III might be true.
upvoted 0 times
...
Chantell
2 years ago
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!
upvoted 0 times
...
Anglea
2 years ago
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.
upvoted 0 times
...
Odette
2 years ago
This is a trick question - they're all valid objectives of testing! Gotta love these certification exams, always trying to catch you out.
upvoted 0 times
Royce
2 years ago
D) Providing information for stakeholders' decision making
upvoted 0 times
...
Merissa
2 years ago
C) Gaining confidence that the system is fit-for-purpose
upvoted 0 times
...
Hollis
2 years ago
B) Investigating and fixing defects in the software under test
upvoted 0 times
...
Tracie
2 years ago
A) Preventing defects from being introduced into the code
upvoted 0 times
...
...
Valentine
2 years ago
I'd say option D is not a valid objective. Testing is more about evaluating the system, not making decisions for stakeholders. That's their job.
upvoted 0 times
Derrick
2 years ago
User 3: Yeah, stakeholders should use the information from testing to make decisions.
upvoted 0 times
...
Tiera
2 years ago
I agree, testing is about evaluating the system, not making decisions for stakeholders.
upvoted 0 times
...
Antonette
2 years ago
I think option D is not a valid objective.
upvoted 0 times
...
...
Nakita
2 years ago
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.
upvoted 0 times
...
Elizabeth
2 years ago
I think option A is not a valid objective of testing. Testing can't really prevent defects, it can only help identify them.
upvoted 0 times
Tenesha
2 years ago
User 2: Option A is not a valid objective of testing.
upvoted 0 times
...
Bernardine
2 years ago
User 3: Testing is more about finding defects than preventing them.
upvoted 0 times
...
Ilona
2 years ago
Investigating and fixing defects is a key objective of testing.
upvoted 0 times
...
Kip
2 years ago
Testing is more about finding defects than preventing them.
upvoted 0 times
...
Maia
2 years ago
I agree, testing can't prevent defects, only identify them.
upvoted 0 times
...
Josphine
2 years ago
Option A is about preventing defects from being introduced into the code.
upvoted 0 times
...
Barney
2 years ago
I agree, testing can't prevent defects.
upvoted 0 times
...
...
Nicolette
2 years ago
I think the answer is D) Providing information for stakeholders' decision making.
upvoted 0 times
...
Junita
2 years ago
I disagree, I believe the correct answer is B) Investigating and fixing defects in the software under test.
upvoted 0 times
...
Galen
2 years ago
I think the answer is B) Investigating and fixing defects in the software under test.
upvoted 0 times
...

Save Cancel