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?
Suggested Answer: C
Get Premium CTAL-TAE Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
12 comments · newest first
EL
Elke
1 month ago
C seems risky. Using coordinates is not reliable for automation.
IZ
Izetta
1 month ago
I agree, but B could also be important. Browser differences might affect identification.
RO
Rosalind
1 month ago
I think A is the best choice. Contacting the provider can clarify issues.
YA
Yan
2 months ago
D feels a bit off, naming standards won’t fix the core problem.
AL
Alyce
2 months ago
I’m surprised this is an issue, thought all components would be identifiable!
CH
Chun
2 months ago
C is a workaround, but not ideal for maintainability.
GE
Georgeanna
2 months ago
B seems important too, could be a browser issue.
KA
Katie
2 months ago
I’d go with A, definitely need to check with the providers first.
MI
Mitzie
2 months ago
I feel like using coordinates could be a workaround, but it seems like a last resort. I’d want to explore other options first before going that route.
BE
Bernardo
3 months ago
I practiced a similar question before, and I chose to verify the testability support. It just makes sense to get information directly from the source.
PH
Phung
3 months ago
I'm not entirely sure, but I remember something about browser compatibility affecting GUI identification. Maybe checking that first could help narrow down the issue?
MA
Maryann
3 months ago
I think the first step should be to verify the testability support with the providers of the third party components. That seems logical since they would know best about their own products.