CTAL-TAE · Question #95
You are using a gTAA to create a TAS for a project. The TAS is aimed specifically at automating a suit of existing manual test cases for standalone desktop applications. All the interfaces between…
The correct answer is A. The test Generation layer. Important note: The stated correct answer (A) appears to be incorrect based on standard gTAA definitions. The correct answer should be C (Test Adaptation layer). --- The Test Adaptation layer is the right focus because the scenario's defining constraint is that all TAS-to-SUT…
Question
You are using a gTAA to create a TAS for a project. The TAS is aimed specifically at automating a suit of existing manual test cases for standalone desktop applications. All the interfaces between the TAS and SUT will be from the CUI of the application. Which of the following layers of the gTAA should you focus on for the TAS?
Options
- AThe test Generation layer
- BThe Test Definition layer
- CThe Test Adaption layer
- DThe Test Execution layer
How the community answered
(41 responses)- A73% (30)
- B5% (2)
- C7% (3)
- D15% (6)
Explanation
Important note: The stated correct answer (A) appears to be incorrect based on standard gTAA definitions. The correct answer should be C (Test Adaptation layer).
The Test Adaptation layer is the right focus because the scenario's defining constraint is that all TAS-to-SUT communication happens through the application's CUI (Character User Interface). This layer provides the technology-specific adapters and interface components needed to connect the test framework to the SUT - in this case, CUI drivers that can send commands and read text output from the desktop application's interface.
Why the others are wrong:
- A (Test Generation): This layer derives new test cases from models or requirements. Since the tests already exist as manual cases, there is nothing to generate.
- B (Test Definition): This layer is about specifying test cases, procedures, and data in a structured form. It matters, but it is not the primary focus when the key technical challenge is how to talk to the SUT.
- D (Test Execution): This layer schedules and runs tests and captures results - important, but generic and not shaped by the CUI interface type.
Memory tip: Ask yourself, "What is unique about this scenario?" The unique constraint is always the interface to the SUT - GUI, API, CUI, etc. The Test Adaptation layer is the one that changes based on how you connect to the SUT, so whenever a question highlights the SUT's interface type, think Adaptation.
If your exam source marks A as correct, I'd recommend cross-checking against the ISTQB CTAL-TAE syllabus, as this appears to be a question error.
Topics
Community Discussion
No community discussion yet for this question.