You are using a gTAA to create a TAS for a project. The TAS is aimed at automatically and executing test cases based on a use-case Modeling approaching that uses UML as a modeling language. All the…

Question

Options

• AThe test reporting component of the test execution layer.
• BThe Test execution component of the test generation layer
• CThe test execution (test engine of the test execution layer
• DThe Command Line Interface (CLI) component of the test adaptation layer

• A
  15% (7)
• B
  6% (3)
• C
  2% (1)
• D
  77% (37)

Explanation

Option D is correct because the Test Adaptation Layer contains interface-specific adapters that connect the TAS to the SUT - and since all SUT interaction is explicitly limited to API and GUI, a CLI adapter is simply never needed and should be excluded to keep the TAS lean.

Why the distractors are wrong:

• A (test reporting) is required in any TAS to capture and communicate results - no project should omit this.
• B (test generation component) is essential here specifically because the TAS uses a use-case/UML modeling approach to automatically generate test cases - removing it would break the core purpose.
• C (test engine) is the heart of test execution - every TAS needs it to actually run the test cases against the SUT.

Memory tip: Focus on the Test Adaptation Layer as the "plug panel" - it only needs plugs for the interfaces you actually use. If CLI isn't listed as a SUT access point, there's no plug needed, so cut it.

No community discussion yet for this question.