ISTQB Exam CT-TAE Topic 2 Question 36 Discussion

Actual exam question for ISTQB's CT-TAE exam

Question #: 36
Topic #: 2

Your TAS has been running successfully on a Windows/GUI based SUT for some years. The SUT has undergone minimal change over the years to maintain business as usual, deploying six-monthly releases for minor enhancements and bug fixes using a waterfall lifecycle.

The TAS has not changed at all during this period. The current project for the SUT will be using the Scrum methodology to deliver a more modern, competitive, user interface. It is in the release planning stage with an agreed release backlog and set of sprints outlined.

The move from lengthy waterfall releases to shorter sprints has led you to conduct a review of the current TAS to make sure it is robust and fully optimised for the timescale challenges of the new project.

What two steps would be BEST to undertake during the review?

a) Ensure that new automation code is using the same naming conventions as existing code.

b) Perform a full regression run in Sprint 1 to identify what improvements could be made to the TAS for future sprints.

c) Ensure that the TAS is using the latest libraries for the operating system.

d) Review the functions that act upon the controls for the GUI for possible consolidation.

e) Involve the test team to see what ease-of-use improvements they would like to see made to the TAS.

Ac and d

Bb and c

Ca and b

Dd and e

Show Suggested Answer

Suggested Answer: B

by Nydia at Aug 22, 2024, 08:52 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Claribel

2 months ago

Dude, you gotta stay on top of those libraries. Can't have your TAS running on ancient software. c and d are the way to go.

upvoted 0 times

Reid

1 months ago

Let's make sure the TAS is ready for the new project with these optimizations.

upvoted 0 times

...

Latosha

1 months ago

Agreed, c and d seem like the best steps to take during the review.

upvoted 0 times

...

Elin

2 months ago

Consolidating functions for the GUI controls can also help streamline the TAS.

upvoted 0 times

...

Annett

2 months ago

Definitely, keeping up with the latest libraries is crucial for optimal performance.

upvoted 0 times

...

Mary

3 months ago

Naming conventions? Really? I'd much rather focus on making the TAS user-friendly for the test team. d and e for the win!

upvoted 0 times

Lyla

2 months ago

Great choice! Prioritizing ease-of-use improvements will make a big difference in the long run.

upvoted 0 times

...

Lura

2 months ago

Absolutely, involving the test team in the process is crucial for success.

upvoted 0 times

...

Jacklyn

2 months ago

That sounds like a good plan. Making the TAS easier for the test team will definitely be beneficial.

upvoted 0 times

...

Dion

2 months ago

I agree, focusing on user-friendly improvements is key. Let's go with d and e.

upvoted 0 times

...

Alisha

3 months ago

I think option D and E would be the best steps to undertake during the review.

upvoted 0 times

...

Valentin

3 months ago

Ah, the age-old battle between waterfall and Agile. A full regression in Sprint 1? Bold move, Cotton. Let's see if it pays off!

upvoted 0 times

Donette

3 months ago

B) b and c

upvoted 0 times

...

Niesha

3 months ago

A) c and d

upvoted 0 times

...

Merilyn

3 months ago

I agree with that. We should also review the functions that act upon the controls for the GUI for possible consolidation.

upvoted 0 times

...

Salley

4 months ago

The move to Scrum is a big change, so reviewing the TAS for optimization is crucial. I think c and d are the best steps - keeping the libraries up-to-date and consolidating the GUI functions.

upvoted 0 times