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 4 Question 45 Discussion

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

Dwight
4 months ago
I'm going with B. Granular keywords will make the tests more readable and easier to maintain in the long run. Plus, it's just a more elegant solution, don't you think?
upvoted 0 times
Penney
3 months ago
D) Establishing an error recovery process for TAS and SUT
upvoted 0 times
...
Bo
3 months ago
C) Changing the wait mechanism to explicit hard-coded waits
upvoted 0 times
...
Olive
3 months ago
B) Implementing keywords with a higher level of granularity
upvoted 0 times
...
Gilma
4 months ago
A) Changing the scripting approach to data-driven scripting
upvoted 0 times
...
...
Lili
5 months ago
Haha, good thing they're not asking us to change the scripting approach to data-driven. That would be a nightmare!
upvoted 0 times
...
Dawne
5 months ago
Hmm, I'm not sure. B and C both sound like viable options, but I'm leaning towards C. Hard-coded waits are just more robust, you know?
upvoted 0 times
...
Tyra
5 months ago
C seems like the best option to me. Changing the wait mechanism to explicit hard-coded waits will ensure the tests are more reliable and less flaky.
upvoted 0 times
Corazon
3 months ago
Yes, it's important to have a reliable wait mechanism in place for accurate test results.
upvoted 0 times
...
Craig
3 months ago
I agree, explicit hard-coded waits can help in making the tests more stable.
upvoted 0 times
...
Wai
4 months ago
C seems like the best option to me. Changing the wait mechanism to explicit hard-coded waits will ensure the tests are more reliable and less flaky.
upvoted 0 times
...
Samira
4 months ago
C) Changing the wait mechanism to explicit hard-coded waits
upvoted 0 times
...
Hannah
4 months ago
B) Implementing keywords with a higher level of granularity
upvoted 0 times
...
Latonia
4 months ago
D
upvoted 0 times
...
Cordelia
4 months ago
A) Changing the scripting approach to data-driven scripting
upvoted 0 times
...
Frankie
4 months ago
C
upvoted 0 times
...
...
Allene
5 months ago
I think establishing an error recovery process for TAS and SUT is crucial for robustness.
upvoted 0 times
...
Youlanda
5 months ago
I believe implementing keywords with a higher level of granularity could also be beneficial.
upvoted 0 times
...
Nobuko
5 months ago
I think the answer is B. Implementing keywords with a higher level of granularity. This will help reduce the repetition and make the tests more maintainable.
upvoted 0 times
Jaime
5 months ago
That makes sense. It would definitely help in reducing repetition and making the tests easier to maintain.
upvoted 0 times
...
Beula
5 months ago
I think the answer is B. Implementing keywords with a higher level of granularity.
upvoted 0 times
...
...
Louis
5 months ago
I agree with Cyril, it would help in reducing repeated instances of identical sequences.
upvoted 0 times
...
Cyril
6 months ago
I think we should consider changing the scripting approach to data-driven scripting.
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