BCS TAE Exam - Topic 1 Question 72 Discussion

Actual exam question for BCS's TAE exam

Question #: 72
Topic #: 1

[All TAE Questions]

Consider A TAS for testing a desktop application via its GUI. All the test cases of the automated test suite contain the same identical sequences of steps at the beginning (to create the necessary objects when doing a preliminary configuration of the test environment and at the end (to remove everything created --specifically for the test itself during the preliminary configuration of the test environment). All automated test cases use the same set of assertion functions from a shared library, for verifying the values in the GUI fields ( e.g text boxes).

What is the BEST recommendation for improving the TAS?

AImplementing keywords with higher level of granularity

BImproving the architecture of the application in order to improve its testability

CAdopting a set of standard verification methods for use by all automated tests

DImplementing standard setup and teardown functions at test case level

Show Suggested Answer

Suggested Answer: A

by German at Oct 30, 2025, 12:50 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Denise

10 hours ago

C is important too. Consistent verification methods can reduce errors.

upvoted 0 times

...

Chaya

6 days ago

Not sure if D is enough, we might need more than just setup/teardown.

upvoted 0 times

...

Elizabeth

11 days ago

Wait, are we really considering B? That sounds complicated.

upvoted 0 times

...

Maryln

16 days ago

C would ensure consistency across tests.

upvoted 0 times

...

Ellsworth

21 days ago

D seems like the best option for efficiency.

upvoted 0 times

...

Jospeh

26 days ago

Implementing keywords sounds like a lot of work. I'd stick with the simple and effective option D.

upvoted 0 times

...

Thersa

1 month ago

Haha, I bet the developers wish they had better testability in the first place. Option B is a pipe dream.

upvoted 0 times

...

Johnetta

1 month ago

C looks good too. Standardizing verification methods will improve consistency across the test suite.

upvoted 0 times

...

Annabelle

1 month ago

Agreed, D is the best choice. Reduces duplication and makes the tests more readable.

upvoted 0 times

...

Nakisha

2 months ago

Option D is the way to go. Reusable setup and teardown functions are a must for maintainable test suites.

upvoted 0 times

...

Carey

2 months ago

I feel like we had a question similar to this where standardization helped a lot. C might be the way to go since it could streamline the verification process.

upvoted 0 times

...

Glory

2 months ago

I'm not entirely sure, but I think improving the architecture might be more beneficial in the long run. B could lead to better testability overall.

upvoted 0 times

...

Dean

2 months ago

I agree, but A could also help with clarity in test cases.

upvoted 0 times

...

Delbert

2 months ago

I think D is the best choice. Standard setup and teardown can streamline tests.

upvoted 0 times

...

Valda

3 months ago

I disagree, A could really streamline the process.

upvoted 0 times

...

Alesia

3 months ago

I keep thinking about how repetitive the setup steps are. Maybe implementing standard setup and teardown functions at the test case level (D) would really help reduce redundancy.

upvoted 0 times

...

Sunny

3 months ago

I remember we discussed the importance of setup and teardown functions in our last practice session. It seems like D could be a strong choice.

upvoted 0 times

...

Viola

3 months ago

I think the best option is A, implementing keywords with a higher level of granularity. That way, the test cases can be more modular and easier to maintain, even with the shared setup and teardown steps.

upvoted 0 times

...

Merlyn

4 months ago

Option B seems interesting, but I'm not sure if improving the application's architecture is the best recommendation here. The question is focused on the test automation suite, not the application itself.

upvoted 0 times

...

Pamela

4 months ago

I'm leaning towards option C. Adopting a set of standard verification methods for all the automated tests seems like it would help improve the maintainability and consistency of the test suite.

upvoted 0 times

...

Shannon

4 months ago

Hmm, I'm a bit confused. The question mentions that all the test cases already have the same sequences of steps at the beginning and end. Wouldn't that mean option D is already being done?

upvoted 0 times

...

Chuck

4 months ago

This seems like a straightforward question. I think the best approach would be to implement standard setup and teardown functions at the test case level.

upvoted 0 times

Kate

2 months ago

I agree, standard setup and teardown sounds efficient.

upvoted 0 times

...