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 CT-TAE Topic 1 Question 12 Discussion

Actual exam question for ISTQB's CT-TAE exam
Question #: 12
Topic #: 1
[All CT-TAE Questions]

If you are tracking the frequency that a test automation code reports a defect that is not really a defect, what metric are you gathering?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Cristina
7 days ago
I believe it could also be B) Automation code defect density, as it measures the quality of the automation code in detecting real defects.
upvoted 0 times
...
Annabelle
7 days ago
I agree, D is the way to go. Gotta keep an eye on those pesky false positives!
upvoted 0 times
...
Tori
8 days ago
D) The number of false-fail results is the correct answer. We need to track the instances where the automation code reports a defect that doesn't actually exist.
upvoted 0 times
...
Idella
9 days ago
I agree with Shayne, because tracking false-fail results helps identify areas for improvement in the automation code.
upvoted 0 times
...
Shayne
10 days ago
I think the answer is D) The number of false-fail results.
upvoted 0 times
...
Patti
11 days ago
I'm not sure, but I think it might also be related to C) Trend metrics to see patterns over time.
upvoted 0 times
...
Francisca
12 days ago
I agree with Scarlet, because tracking false-fail results can help improve the accuracy of the automation code.
upvoted 0 times
...
Scarlet
14 days ago
I think the answer is D) The number of false-fail results.
upvoted 0 times
...

Save Cancel