CTAL-TAE · Question #93
The GUI of a Customer Relationship Management (CRM) application has been delivered through internet Explorer with proprietary Active X and Java controls. This implementation enables rich client…
The correct answer is D. Structure scripting. Structured scripting is the most suitable technique here because the goal is to evaluate whether commercial tools can correctly recognize and capture tester interactions with a complex, proprietary GUI (ActiveX and Java controls). Structured scripting uses control structures…
Question
The GUI of a Customer Relationship Management (CRM) application has been delivered through internet Explorer with proprietary Active X and Java controls. This implementation enables rich client capabilities, but specific commercial automation tools are necessary to automate test cases at GUI of functional test cases. This is to demonstrate whether a small set of the commercial are able to properly recognize actions taken by a tester when interacting with GUI of the CRM application. Which of the following scripting techniques would be MOST suitable in this scenario?
Options
- AData-driven scripting
- BKeyword-driven scripting
- CLinear scripting
- DStructure scripting
How the community answered
(27 responses)- A7% (2)
- B11% (3)
- D81% (22)
Explanation
Structured scripting is the most suitable technique here because the goal is to evaluate whether commercial tools can correctly recognize and capture tester interactions with a complex, proprietary GUI (ActiveX and Java controls). Structured scripting uses control structures and reusable subroutines, giving enough organization to meaningfully demonstrate tool capability across different GUI interactions without requiring elaborate framework setup - it's the right fit for a tool proof-of-concept on a technically complex interface.
Why the distractors are wrong:
- A (Data-driven): Separating test logic from external data sources is overkill when the objective is simply proving a tool can recognize GUI actions - not running the same tests across many data sets.
- B (Keyword-driven): Requires significant upfront framework design and keyword libraries, which is far too heavy for a small-scale tool evaluation exercise.
- C (Linear): Pure record-and-playback is too fragile and primitive; with proprietary controls like ActiveX and Java, linear scripts fail to adequately demonstrate whether the tool handles complex object recognition reliably across different scenarios.
Memory tip: Think "structure before scale." When the task is evaluating tools on complex GUIs, you need just enough structure (subroutines, control flow) to be meaningful - structured scripting hits that middle ground. Data-driven and keyword-driven are for scaling, not evaluating.
Topics
Community Discussion
No community discussion yet for this question.