Cyber Monday 2024! 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 9 Question 42 Discussion

Actual exam question for BCS's TAE exam
Question #: 42
Topic #: 9
[All TAE Questions]

Consider a TAS that uses a keyword-driven framework. The SUT is a web application and there is a large set of keywords available for writing the automated tests that relate to highly specific user actions linked directly to the GUI of the SUT. The automated test written with the keywords are statically analyzed by a custom tool which highlight's repeated instances of identical sequence of keywords. The waiting mechanism implemented by the TAS for a webpage load is based on a synchronous sampling within a given timeout. The TAS allows checking a webpage load every seconds until a timeout value

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Cristy
6 months ago
I'd go with B as well. Modularizing the keywords into more specific actions will not only reduce repetition, but also make the tests more readable and maintainable.
upvoted 0 times
...
Wava
6 months ago
Haha, these test automation engineers must be having a tough time with all these keywords! I bet they're dreaming of a world where they can just write plain old code instead of this 'keyword-driven' nonsense.
upvoted 0 times
...
Ernie
6 months ago
D is an interesting option, but it doesn't really address the root cause of the issue. Establishing an error recovery process is always a good idea, but it won't solve the problem of repeated keyword sequences.
upvoted 0 times
Paulina
6 months ago
C) Changing the wait mechanism to explicit hard-coded waits
upvoted 0 times
...
Mammie
6 months ago
B) Implementing keywords with a higher level of granularity
upvoted 0 times
...
Shizue
6 months ago
A) Changing the scripting approach to data-driven scripting
upvoted 0 times
...
...
James
6 months ago
C seems like the easiest fix, but it might not be the best long-term solution. Relying on hard-coded waits could make the tests less reliable in the long run.
upvoted 0 times
Edelmira
5 months ago
D
upvoted 0 times
...
Marion
5 months ago
C
upvoted 0 times
...
Lisha
5 months ago
C) Changing the wait mechanism to explicit hard-coded waits
upvoted 0 times
...
Tandra
5 months ago
A) Changing the scripting approach to data-driven scripting
upvoted 0 times
...
Samira
6 months ago
C) Changing the wait mechanism to explicit hard-coded waits
upvoted 0 times
...
Gerry
6 months ago
B) Implementing keywords with a higher level of granularity
upvoted 0 times
...
Dell
6 months ago
A) Changing the scripting approach to data-driven scripting
upvoted 0 times
...
...
Dick
7 months ago
I think B is the way to go - breaking down the keywords into more granular actions will help reduce the repetition and make the tests more maintainable.
upvoted 0 times
Cyril
6 months ago
That sounds like a good idea, it will definitely make the tests easier to manage.
upvoted 0 times
...
Alex
6 months ago
B) Implementing keywords with a higher level of granularity
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77