ISTQB-CTFL Exam - Topic 1 Question 22 Discussion

Actual exam question for ISTQB's ISTQB-CTFL exam

Question #: 22
Topic #: 1

In addition to thorough testing of the requirements specification, a development team aims to involve users as early as possible in the development process, using practices such as prototyping, to ensure that the software systems being developed will meet the users' expectations. This approach is especially useful at mitigating the risks associated with one of the seven testing principles, which one?

ATests wear out

BAbsence-of-errors fallacy

CWorking software over comprehensive documentation.

DDefects cluster together

Show Suggested Answer

Suggested Answer: C

Test Management tools are designed to support the planning, execution, and monitoring of the testing process. They provide features for managing test cases, test runs, tracking defects, and reporting on testing activities. However, the statement in option C describes Test Management tools as monitoring and reporting on the system's behavior during testing activities, which is not accurate. Test Management tools focus on the testing process itself rather than on the behavior of the system under test.

Test data preparation tools (A) indeed create and manage test data for use during test execution.

Test execution tools (B) automate the execution of test cases and the comparison of actual outcomes against expected results.

Test comparators (D) are tools that compare actual outcomes with expected outcomes, highlighting discrepancies.

Therefore, option C is the correct answer as it inaccurately describes the function of Test Management tools.

by Lashaun at Jun 01, 2024, 07:53 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Chau

5 months ago

Totally agree, involving users early is key!

upvoted 0 times

...

Katheryn

5 months ago

Wait, are we sure this really mitigates that risk?

upvoted 0 times

...

Lyda

6 months ago

Prototyping helps catch issues early, for sure!

upvoted 0 times

...

Xuan

6 months ago

I think it's more about defects clustering together.

upvoted 0 times

...

Hector

6 months ago

Definitely the absence-of-errors fallacy!

upvoted 0 times

...

Iluminada

6 months ago

I practiced a similar question where user involvement was linked to reducing risks, and I think it was about the absence-of-errors fallacy too.

upvoted 0 times

...

Carmela

7 months ago

I feel like the principle about defects clustering might also be relevant, but I can't recall the specifics on how it ties into user involvement.

upvoted 0 times

...

Franchesca

7 months ago

I think it's definitely related to the absence-of-errors fallacy since getting user feedback early can help identify issues that might not be obvious from just the specs.

upvoted 0 times

...

Marvel

7 months ago

I remember discussing the absence-of-errors fallacy in class, but I'm not entirely sure how it connects to involving users early.

upvoted 0 times

...

Lenita

7 months ago

This is a tricky one. I'm going to review the testing principles quickly and see if I can identify the one that's most relevant to user involvement and expectations. Gotta be careful not to overthink it.

upvoted 0 times

...

Jose

7 months ago

Okay, I've got an idea. Since the question mentions involving users early and using practices like prototyping, that suggests the principle it's referring to is probably the "absence-of-errors fallacy." Prototyping can help catch issues that requirements alone might miss.

upvoted 0 times

...

Lawrence

7 months ago

Hmm, I'm a bit unsure about this one. The testing principles aren't something I'm super familiar with. I'll have to think it through carefully and try to eliminate the options that don't seem to fit.

upvoted 0 times

...

Tegan

7 months ago

This question seems straightforward. I think the key is to focus on the testing principles and how involving users early can help mitigate the risks associated with one of them.

upvoted 0 times

...

Catarina

7 months ago

Hmm, this seems like a tricky one. I'll need to carefully compare the key differences between RADIUS and TACACS+ to figure this out.

upvoted 0 times

...

Lilli

7 months ago

Okay, let me start by breaking down the differences between common and local roles. Common roles can be granted to both local and common users, while local roles are only for local users. That's a good starting point.

upvoted 0 times

...

Carin

1 year ago

Prototyping, huh? Sounds like a great way to get user feedback and avoid costly mistakes. As long as the users don't try to redesign the entire system during the first prototype review.

upvoted 0 times

Ona

11 months ago

C) Working software over comprehensive documentation.

upvoted 0 times

...

Stefan

11 months ago

B) Absence-of-errors fallacy

upvoted 0 times

...

Marisha

11 months ago

A) Tests wear out

upvoted 0 times

...

Lindsay

1 year ago

I hope the exam doesn't have any 'trick questions' like 'Tests wear out.' That would just be cruel!

upvoted 0 times

Jovita

11 months ago

C) Working software over comprehensive documentation.

upvoted 0 times

...

Fairy

12 months ago

B) Absence-of-errors fallacy

upvoted 0 times

...

Vivan

12 months ago

A) Tests wear out

upvoted 0 times

...

Earnestine

1 year ago

I'm going with B. Absence-of-errors fallacy. It just makes the most sense in the context of involving users early to ensure the software meets their expectations.

upvoted 0 times

Rasheeda

12 months ago

I think B makes sense too. It's important to address any potential fallacies early on in the development process.

upvoted 0 times

...

Rasheeda

12 months ago

I agree, involving users early can help catch errors before they become bigger issues.

upvoted 0 times

...

Christiane

1 year ago

C, Working software over comprehensive documentation, is an interesting choice, but I don't think it's the best fit for this question. The focus seems to be on mitigating risks, not on the Agile Manifesto principles.

upvoted 0 times

...

Margart

1 year ago

D, Defects cluster together, seems like the most relevant option here. By involving users early, the team can identify and address any defects that tend to cluster in certain areas of the software.

upvoted 0 times

...

Kristian

1 year ago

I'm not sure, but it makes sense that involving users early can help prevent the absence-of-errors fallacy.

upvoted 0 times

...

Maddie

1 year ago

I think the answer is B. Absence-of-errors fallacy. This principle highlights the risk that just because no defects are found during testing, it doesn't mean the software is free of issues. Involving users early on can help address this risk.

upvoted 0 times