ISTQB Exam CT-TAE Topic 1 Question 25 Discussion

Actual exam question for ISTQB's CT-TAE exam

Question #: 25
Topic #: 1

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

AChanging the scripting approach to data-driven scripting

BImplementing keywords with a higher level of granularity

CChanging the wait mechanism to explicit hard-coded waits

DEstablishing an error recovery process for TAS and SUT

Show Suggested Answer

Suggested Answer: C

by Glenn at Apr 11, 2024, 09:12 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Yuki

2 months ago

Wait, did they just say 'keyword-driven framework'? That's so 2010! I bet they're still using a dot-matrix printer, too.

upvoted 0 times

...

Ruth

2 months ago

Establishing an error recovery process for the TAS and SUT sounds like a great idea. Option D could help us handle any unexpected issues more gracefully.

upvoted 0 times

Darrin

28 days ago

Yes, having a plan for error recovery can make our automated tests more robust and reliable.

upvoted 0 times

...

Yuriko

1 months ago

I agree. It's important to be prepared for any errors that may occur during the testing process.

upvoted 0 times

...

Maynard

1 months ago

That's a good point. Having an error recovery process in place can definitely help us handle unexpected issues.

upvoted 0 times

...

Darrin

3 months ago

I'm a big fan of data-driven scripting, so option A is definitely appealing. But I wonder if that would really address the root cause of the repeated keyword sequences.

upvoted 0 times

Quentin

1 months ago

C) Changing the wait mechanism to explicit hard-coded waits

upvoted 0 times

...

Claribel

1 months ago

B) Implementing keywords with a higher level of granularity

upvoted 0 times

...

Verdell

1 months ago

C) Changing the wait mechanism to explicit hard-coded waits

upvoted 0 times

...

Evan

2 months ago

A) Changing the scripting approach to data-driven scripting

upvoted 0 times

...

Carisa

2 months ago

B) Implementing keywords with a higher level of granularity

upvoted 0 times

...

Devon

2 months ago

A) Changing the scripting approach to data-driven scripting

upvoted 0 times

...

Rolande

3 months ago

Option C looks interesting, but I'm not sure that switching to explicit hard-coded waits is the best solution. The synchronous sampling approach might have its issues, but it could still be optimized.

upvoted 0 times

...

Zena

3 months ago

Hmm, this seems like a tricky one. I'm leaning towards option B - implementing keywords with a higher level of granularity. That way, we can avoid repetitive sequences and make the tests more maintainable.

upvoted 0 times

...