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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

BCS Exam TAE Topic 5 Question 47 Discussion

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

by Maricela at Jul 14, 2024, 03:43 PM

Limited Time Offer

25%

Off

Get Premium TAE Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Evette
8 days ago
Wait, you mean I can't just use the 'make it work' approach? Darn, there goes my plan.
upvoted 0 times
...
Yolando
9 days ago
Establishing an error recovery process is always a good idea, but it doesn't directly solve the problem of repeated keyword sequences.
upvoted 0 times
...
Jamal
13 days ago
Changing to explicit waits might be a band-aid fix. I'd prefer a more robust solution that addresses the root cause.
upvoted 0 times
...
Merrilee
14 days ago
Implementing more granular keywords could help, but I'm not sure if that alone will address the code duplication issue.
upvoted 0 times
...
Domitila
25 days ago
I think option D is crucial for error handling in TAS and SUT.
upvoted 0 times
...
Charlene
29 days ago
I prefer option C, hard-coded waits seem more reliable.
upvoted 0 times
...
Ronald
1 months ago
I disagree, I believe option B is more effective.
upvoted 0 times
...
Marla
1 months ago
The data-driven approach seems like the best solution here. Reducing code duplication and increasing reusability is key for a large test suite.
upvoted 0 times
Lina
11 days ago
D) Establishing an error recovery process for TAS and SUT
upvoted 0 times
...
Georgiana
14 days ago
C) Changing the wait mechanism to explicit hard-coded waits
upvoted 0 times
...
Martin
21 days ago
B) Implementing keywords with a higher level of granularity
upvoted 0 times
...
Omega
27 days ago
A) Changing the scripting approach to data-driven scripting
upvoted 0 times
...
...
Gwenn
1 months ago
I think option A is a good idea.
upvoted 0 times
...

Save Cancel