Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

BCS Exam TAE Topic 6 Question 66 Discussion

Actual exam question for BCS's TAE exam
Question #: 66
Topic #: 6
[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?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Tesha
2 days ago
I'd have to go with C. Adopting a set of standard verification methods will ensure consistency and reduce duplication across the test suite.
upvoted 0 times
...
Vincent
3 days ago
Agreed, D is the way to go. Sharing setup and teardown logic across test cases is a common best practice in test automation.
upvoted 0 times
...
Royal
4 days ago
I agree with Odette, having more specific keywords would make the TAS more efficient.
upvoted 0 times
...
Odette
12 days ago
I think implementing keywords with higher level of granularity would be the best recommendation.
upvoted 0 times
...
Earlean
18 days ago
Option D seems like the obvious choice here. Implementing standard setup and teardown functions at the test case level will make the test suite much more modular and maintainable.
upvoted 0 times
Fidelia
3 days ago
B) Improving the architecture of the application in order to improve its testability
upvoted 0 times
...
Nickolas
9 days ago
A) Implementing keywords with higher level of granularity
upvoted 0 times
...
...

Save Cancel