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

ISTQB Exam ISTQB-CTFL Topic 1 Question 22 Discussion

Actual exam question for ISTQB's ISTQB-CTFL exam
Question #: 22
Topic #: 1
[All ISTQB-CTFL Questions]

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?

Show Suggested Answer Hide 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.


Contribute your Thoughts:

Earnestine
10 hours 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
...
Christiane
2 days 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
5 days 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
8 days 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
9 days 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
...
Daniel
9 days ago
I agree with Haley, involving users early on through prototyping can help ensure the software meets their expectations.
upvoted 0 times
...
Haley
10 days ago
I think the answer is C) Working software over comprehensive documentation.
upvoted 0 times
...

Save Cancel