ISTQB Exam CT-TAE Topic 1 Question 12 Discussion

Actual exam question for ISTQB's CT-TAE exam

Question #: 12
Topic #: 1

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?

ATool scripting metrics

BAutomation code defect density

CTrend metrics

DThe number of false-fail results

Show Suggested Answer

Suggested Answer: C

by Nichelle at Jul 09, 2023, 09:28 AM

Limited Time Offer

25%

Off

Get Premium CT-TAE Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Brianne

2 months ago

This question is making me feel like a detective trying to catch the culprit false-fail results. Time to put on my virtual deerstalker cap!

upvoted 0 times

Dacia

18 days ago

C) Trend metrics

upvoted 0 times

...

Ronny

23 days ago

B) Automation code defect density

upvoted 0 times

...

Levi

1 months ago

A) Tool scripting metrics

upvoted 0 times

...

Terrilyn

2 months ago

D all the way! I hate it when my automation code cries wolf. Gotta keep those false alarms in check.

upvoted 0 times

Daren

9 days ago

D) The number of false-fail results

upvoted 0 times

...

Clay

1 months ago

C) Trend metrics

upvoted 0 times

...

Claribel

1 months ago

B) Automation code defect density

upvoted 0 times

...

Trinidad

1 months ago

A) Tool scripting metrics

upvoted 0 times

...

Latonia

2 months ago

Hmm, I was leaning towards C) Trend metrics, but I guess that wouldn't capture the false-fail issue specifically. Good catch, everyone!

upvoted 0 times

...

Cristina

2 months 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

2 months ago

I agree, D is the way to go. Gotta keep an eye on those pesky false positives!

upvoted 0 times

Lettie

17 days ago

D) The number of false-fail results

upvoted 0 times

...

Dana

1 months ago

C) Trend metrics

upvoted 0 times

...

Abel

1 months ago

Yeah, false positives can really mess up the testing process.

upvoted 0 times

...

Renea

1 months ago

B) Automation code defect density

upvoted 0 times

...

Yaeko

2 months ago

I think D is the most important metric to track.

upvoted 0 times

...

Kattie

2 months ago

A) Tool scripting metrics

upvoted 0 times

...

Tori

2 months 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

2 months ago

I agree with Shayne, because tracking false-fail results helps identify areas for improvement in the automation code.

upvoted 0 times

...

Shayne

2 months ago

I think the answer is D) The number of false-fail results.

upvoted 0 times

...

Patti

2 months 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

2 months ago

I agree with Scarlet, because tracking false-fail results can help improve the accuracy of the automation code.

upvoted 0 times

...

Scarlet

2 months ago

I think the answer is D) The number of false-fail results.

upvoted 0 times

...