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 2 Question 50 Discussion

Actual exam question for BCS's ISTQB Certified Tester Advanced Level - Test Automation Engineer exam
Question #: 50
Topic #: 2
[All ISTQB Certified Tester Advanced Level - Test Automation Engineer 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:

Myra
4 days ago
Option B? Really? Improving the app's architecture? That's like putting lipstick on a pig. Just use Option D and move on with your life.
upvoted 0 times
...
Patrick
8 days ago
I'm going with Option C. Adopting a set of standard verification methods for all tests will ensure consistency and reduce errors. It's the most comprehensive solution.
upvoted 0 times
...
Apolonia
10 days ago
I agree with Eloisa, having more granularity in keywords can make the test suite more flexible and easier to maintain.
upvoted 0 times
...
Alline
12 days ago
I agree with Chery. Option D is the clear winner here. Who wants to write the same code over and over again in each test case?
upvoted 0 times
Brittni
12 hours ago
I think option D is the way to go. It will definitely save time and make the test suite more efficient.
upvoted 0 times
...
...
Eloisa
17 days ago
I think implementing keywords with higher level of granularity would be the best recommendation.
upvoted 0 times
...
Chery
17 days ago
Option D is the way to go. Implementing standard setup and teardown functions at the test case level will make the test suite much more maintainable and less redundant.
upvoted 0 times
Floyd
3 days ago
I agree, having standard setup and teardown functions will save a lot of time and effort in the long run.
upvoted 0 times
...
Major
5 days ago
Option D is definitely the best choice. It will make managing the test suite a lot easier.
upvoted 0 times
...
...

Save Cancel