ISTQB CT-TAE Exam - Topic 1 Question 61 Discussion

Actual exam question for ISTQB's CT-TAE exam

Question #: 61
Topic #: 1

You are working on a TAS for standalone application. The automated tests are developed based on a automation framework that allows interaction with GUI elements using on object orientated API. The GUI elements include menus, buttons, radio buttons, text toolbars and their properties.

Whilst automating a test, you have discovered that the GUI elements of some third party components are not identifiable by the automated tool you are using.

Which of the following is the FIRST step that you take to investigate this issue?

AVerify the testability support with the providers of the third party components

BVerify whether the GUI identification depends on the browser.

CAdopt an approach that uses the coordinates of the GUI elements instead

DVerify whether naming standards for variables and have been defined for the current automation solution

Show Suggested Answer

Suggested Answer: A

by Jackie at Jan 05, 2026, 05:16 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Vivan

3 days ago

B) Checking if it's browser-dependent is a good idea, but I'd start with the provider.

upvoted 0 times

...

Ronny

8 days ago

D) Naming standards? Really? That's not gonna help with unidentifiable GUI elements.

upvoted 0 times

...

Dorathy

13 days ago

C) Using coordinates could work, but that's a bit of a hack. I'd start with the provider first.

upvoted 0 times

...

Tawny

18 days ago

A) Seems like the most logical step to take. Gotta get the provider's input on this.

upvoted 0 times

...

Dottie

24 days ago

I recall that naming standards can help with identification, but if the elements are not identifiable at all, I think we need to check with the providers first. So, A seems right.

upvoted 0 times

...

Rochell

29 days ago

I feel like using coordinates could work in some cases, but it seems like a workaround rather than a solution. I’d lean towards option A.

upvoted 0 times

...

Yoko

1 month ago

I'm not entirely sure, but I remember a similar question where checking browser compatibility was important. Maybe option B could be relevant too?

upvoted 0 times

...

Geraldo

1 month ago

I think the first step should be to verify the testability support with the providers of the third party components. That seems logical.

upvoted 0 times

...

Luisa

1 month ago

This question is making me a little nervous. I don't have much experience with automating tests for third party components. I guess I'll just have to read through the options carefully and try to figure out the best approach.

upvoted 0 times

...

Miesha

2 months ago

Okay, I think I've got a strategy here. I'll start by checking with the third party component providers to see if they have any guidance on how to automate testing their GUI elements. If that doesn't work, then I'll look into the other options.

upvoted 0 times

...

Gregoria

2 months ago

I'm a bit confused by this question. I'm not sure if I should be looking at the browser or the naming standards first. Maybe I'll just go with option A and see if that helps me get started.

upvoted 0 times

...

Kattie

2 months ago

Hmm, this seems like a tricky one. I'd probably start by verifying the testability support with the providers of the third party components. That seems like the most logical first step to me.

upvoted 0 times

...