ISTQB CT-TAE Exam - 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

Ivory

4 months ago

A counter for test executions could be useful for trends.

upvoted 0 times

...

Leonardo

4 months ago

Wait, why would 'pass' be red? That sounds wrong.

upvoted 0 times

...

Luz

4 months ago

Color coding? That's just confusing!

upvoted 0 times

...

Huey

4 months ago

I think a status for TAS errors would help too.

upvoted 0 times

...

Alline

4 months ago

Adding system configuration info is a must!

upvoted 0 times

...

Melynda

5 months ago

I think having a counter for test case executions might help track flaky tests, but I'm not convinced it's the best option compared to others like e.

upvoted 0 times

...

Rory

5 months ago

I practiced a similar question where we talked about the need for dynamic measurement info. It seems like option a could provide valuable insights for failure analysis.

upvoted 0 times

...

Carmelina

5 months ago

I'm not entirely sure, but I feel like adding a status for TAS errors could help clarify issues, so maybe option b is worth considering too.

upvoted 0 times

...

Leonor

5 months ago

I remember discussing the importance of system configuration information in class, so I think option e would be really helpful for defect reporting.

upvoted 0 times

...

Mayra

5 months ago

I think the best approach is to go with d and e. Tracking the execution count of each test case and capturing the system/software versions will give you a lot of helpful context for analyzing failures. The other options seem like they could be overkill or not as directly useful.

upvoted 0 times

...

Esteban

5 months ago

Hmm, I like the idea of adding a 'TAS error' status in addition to pass and fail. That could help differentiate between issues with the test automation itself versus the system under test. And system configuration info is always important for reproducing defects.

upvoted 0 times

...

Scarlet

5 months ago

I'm a bit confused by the options here. It seems like a, b, and e could all be useful, but I'm not sure which combination would be the "best" approach. I'll need to think this through carefully.

upvoted 0 times

...

Ronna

5 months ago

This seems like a straightforward question about improving the test automation suite. I think the key is to focus on adding more detailed logging and information to help with failure analysis and defect reporting.

upvoted 0 times

...

Andrew

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

Hassie

9 months ago

Yeah, I don't think using a colour coding scheme for 'pass' and 'fail' is a good idea. It could cause confusion.

upvoted 0 times

...

Kaitlyn

10 months ago

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

upvoted 0 times

...

Annett

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

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

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

11 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

Aleisha

9 months ago

Yeah, color coding and dynamic measurements might be nice to have, but having detailed system information and tracking test case executions seem more essential for effective failure analysis.

upvoted 0 times

...

Rikki

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

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

11 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

11 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

11 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

12 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

...