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

Rosina

3 months ago

Wait, they haven’t changed the TAS at all? That’s wild!

upvoted 0 times

...

Diane

3 months ago

I’d go with b and c, regression is key for new sprints!

upvoted 0 times

...

Carli

3 months ago

Not sure about d, seems like a lot of work for little gain.

upvoted 0 times

...

Bernardine

4 months ago

Totally agree, we need to keep the TAS updated.

upvoted 0 times

...

Daryl

4 months ago

I think c and d are solid choices!

upvoted 0 times

...

Wai

4 months ago

Consolidating functions sounds good, but I wonder if just focusing on the naming conventions is enough. I might lean towards d and e, but I'm not completely confident.

upvoted 0 times

...

Nan

4 months ago

I practiced a question similar to this, and I think performing a full regression run in Sprint 1 could really highlight issues early on. So, b might be important too.

upvoted 0 times

...

Matilda

4 months ago

I'm not entirely sure, but I think involving the test team could really help identify what improvements are needed. Maybe option d and e together?

upvoted 0 times

...

Alva

5 months ago

I remember we discussed the importance of using the latest libraries to ensure compatibility, so option c seems like a good choice.

upvoted 0 times

...

Maryann

5 months ago

I think the key here is to optimize the TAS for the new Scrum-based development process. Reviewing the GUI functions for consolidation and getting feedback from the test team on ease-of-use improvements seems like the most logical approach to me.

upvoted 0 times

...

Lauran

5 months ago

Okay, I've got this. We need to ensure the new automation code is using the same naming conventions as the existing code, and then perform a full regression run in Sprint 1 to identify any improvements that could be made to the TAS for future sprints. That's the way to go.

upvoted 0 times

...

Laticia

5 months ago

This question seems straightforward. I think reviewing the functions that act upon the GUI controls for possible consolidation and involving the test team to get their input on ease-of-use improvements would be the best approach.

upvoted 0 times

...

Eden

5 months ago

Hmm, I'm a bit confused. Should we be focusing on ensuring the TAS is using the latest libraries for the operating system or doing a full regression run in Sprint 1? I'm not sure which two steps would be best.

upvoted 0 times

...

Tammy

5 months ago

Creating the actual advertisement content seems like the most important first step to me. You need to have the message and creative ready before you can do anything else.

upvoted 0 times

...

Dorothy

5 months ago

I'm confident I know the answer to this one. Option C uses the `window.open()` method correctly to open a new browser window.

upvoted 0 times

...

Claribel

1 year 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 year ago

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

upvoted 0 times

...

Latosha

1 year ago

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

upvoted 0 times

...

Elin

1 year ago

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

upvoted 0 times

...

Annett

1 year ago

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

upvoted 0 times

...

Mary

1 year 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

1 year ago

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

upvoted 0 times

...

Lura

1 year ago

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

upvoted 0 times

...

Jacklyn

1 year ago

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

upvoted 0 times

...

Dion

1 year ago

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

upvoted 0 times

...

Alisha

1 year ago

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

upvoted 0 times

...

Valentin

1 year 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

1 year ago

B) b and c

upvoted 0 times

...

Niesha

1 year ago

A) c and d

upvoted 0 times

...

Merilyn

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

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