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

ISTQB Exam CT-TAE Topic 1 Question 7 Discussion

Actual exam question for ISTQB's CT-TAE exam
Question #: 7
Topic #: 1
[All CT-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: B

Contribute your Thoughts:

Sharen
6 days ago
I agree with Staci. Having that common setup and teardown process in a shared function will make the test suite much more maintainable and easier to update in the future.
upvoted 0 times
...
Verlene
9 days ago
I personally think adopting a set of standard verification methods for use by all automated tests would be more beneficial in the long run.
upvoted 0 times
...
Staci
10 days ago
Option D seems like the obvious choice here. Implementing standard setup and teardown functions at the test case level will help eliminate all that redundant code we're seeing in the beginning and end of each test case.
upvoted 0 times
...
Rossana
16 days ago
I agree with Oliva. It would make the test cases more modular and easier to maintain.
upvoted 0 times
...
Oliva
17 days ago
I think implementing keywords with higher level of granularity would be the best recommendation.
upvoted 0 times
...

Save Cancel