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…

Question

Options

• 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

• A
  13% (2)
• C
  81% (13)
• D
  6% (1)

Explanation

When third-party GUI elements cannot be identified by the object-oriented API, switching to coordinate-based identification (C) is the immediate, practical first investigative step - it confirms whether the elements can still be interacted with at all, just not through object recognition, which scopes the problem before any escalation.

Why the distractors are wrong:

• A (verify testability with providers) is a vendor escalation step - useful later, but not the first hands-on investigation you perform.
• B (check browser dependency) is irrelevant here; the question explicitly states this is a standalone application, not a web/browser-based one.
• D (naming standards for variables) addresses a code quality concern unrelated to why the tool fails to recognize third-party GUI elements.

Memory tip: Think of the order as "try locally before calling for help." Coordinates are always available as a fallback identification method - using them first tells you what is broken before you escalate why. Also flag the word "standalone" in exam questions as a red-flag eliminator for any browser-related answer choices.

No community discussion yet for this question.