ISTQB Exam CT-TAE Topic 2 Question 49 Discussion

Actual exam question for ISTQB's CT-TAE exam

Question #: 49
Topic #: 2

Your functional regression test automation suite ran successfully for the first two sprints and no failures were encountered during the runs. The automation suite records the status of each test case as either 'pass' or 'fail' and has excellent recovery capability built in.

For the third sprint, the TAS log reported several test cases with a status of 'fail'. You investigated each test case and found that most failures were due to a defect in one of the keyword scripts, rather than in the SUT. For those where the failure was in the SUT, defect reports were raised but several were returned by the developers asking for more information to enable them to reproduce the problem.

Which additional log items SHOULD you add to the TAS that would BEST improve failure analysis and defect reporting for future sprints?

a) Dynamic measurement information about the SUT.

b) A status of TAS error', in additional to pass' and 'fail', for each test case.

c) Use of a colour coding scheme so that 'pass' is in red and fail' is in green.

d) A counter to determine how many times each test case has been executed.

e) System configuration information including software/firmware and operating system versions.

f) A copy of the source code for all Keyword scripts executed.

Aa and b

Bd and e

Ca and c

Db and e

Show Suggested Answer

Suggested Answer: D

by Rebbecca at Mar 09, 2025, 07:04 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Andrew

27 days ago

This exam question is like a bug in the SUT - it's giving me a headache! But at least we can all agree that the right answer is not c) 'pass' in red and 'fail' in green. That would just be asking for trouble.

upvoted 0 times

Kaitlyn

3 days ago

I agree, those additions would definitely improve failure analysis and defect reporting for future sprints.

upvoted 0 times

...

Annett

15 days ago

I think adding dynamic measurement information about the SUT and a status of 'TAS error' for each test case would be really helpful.

upvoted 0 times

...

Jacquelyne

28 days ago

Hold on, did someone say 'color coding'? I'm all for that! C) a and c gets my vote. Might as well make the test results look pretty while we're at it, right? It's not like the developers are going to be able to reproduce the issues anyway.

upvoted 0 times

...

Denae

30 days ago

I'm leaning towards D) b and e. Having a 'TAS error' status and system configuration details would give us a much clearer picture of what's going on. This is a certification exam, so let's focus on the essentials!

upvoted 0 times

...

Lashon

1 months ago

Really? C) a and c? Color coding the test results and having dynamic measurement information about the SUT? That sounds like a waste of time. We need practical solutions, not fancy gimmicks.

upvoted 0 times

Rikki

8 days ago

I agree, having software/firmware versions and knowing how many times a test case has been executed would definitely help in identifying patterns of failure.

upvoted 0 times

...

Deeanna

15 days ago

I think D) b and e would be more practical. Having system configuration information and a counter for test case executions would be more useful.

upvoted 0 times

...

Denae

1 months ago

I think the answer is B) d and e. Tracking the number of times each test case has been executed and having system configuration information would definitely help with failure analysis and defect reporting.

upvoted 0 times

...

Bobbie

2 months ago

I think adding system configuration information and a copy of the source code for keyword scripts executed would also be beneficial for future sprints.

upvoted 0 times

...

Sharee

2 months ago

I agree with Jutta. Having more detailed information about the system under test and additional error status will definitely help in improving failure analysis and defect reporting.

upvoted 0 times

...

Jutta

2 months ago

I think we should add dynamic measurement information about the SUT and a status of 'TAS error' for each test case.

upvoted 0 times

...