New Year Sale ! 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 12 Question 58 Discussion

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

Anna
18 hours ago
I believe adopting a set of standard verification methods for use by all automated tests could also be a good option.
upvoted 0 times
...
Whitney
22 hours ago
Hmm, I think B might be the best option. Improving the application's testability at the architectural level can have a more profound impact on the overall TAS than just optimizing individual test cases.
upvoted 0 times
...
Tamie
4 days ago
I agree with Mireya. It would make the test suite more maintainable and reusable.
upvoted 0 times
...
Golda
6 days ago
I'd go with C. Adopting a set of standard verification methods for all automated tests ensures consistency and reliability in the test results. Plus, it's easier to maintain the shared library than duplicating the same assertion functions in each test case.
upvoted 0 times
...
Mireya
6 days ago
I think implementing keywords with higher level of granularity would be the best recommendation.
upvoted 0 times
...
Tamekia
10 days ago
D for sure! Implementing standard setup and teardown functions at the test case level is the most efficient way to avoid repeating the same steps across multiple test cases. Keeps the code clean and maintainable.
upvoted 0 times
...

Save Cancel