Free ISTQB Test Automation Engineering Exam Practice Questions

Sample Practice Questions

Try these 10 sample questions from the ISTQB Test Automation Engineering Exam practice bank. Each includes the answer and explanation. Continue with the interactive practice above to review the full question set.

1. 1Why might an automated test execute all its steps successfully yet fail to establish that a subjective quality expectation has been met?

   1. A. Execution success implies that every quality expectation has been verified.
   2. B. Automated checking requires results that a machine can interpret and an oracle can verify.
   3. C. Subjective expectations become objectively verified when execution is repeated.
   4. D. Automated checking derives all expected results from the observed behavior.

   Answer: B

   Explanation: The syllabus states: "Test automation can only check test results that can be verified by an automated test oracle" Completing actions is insufficient when the expectation cannot be checked by the automated oracle. Repetition does not supply that oracle, and actual behavior does not establish its own correctness.

   Reference: ISTQB Certified Tester Advanced Level Test Automation Engineering Syllabus v2.0 — p. 15, §1.1.1, limitations

2. 2Why should a TAE discuss test interfaces with the software architect while SUT features are being designed?

   1. A. Testability should be implemented only after acceptance testing.
   2. B. Testability is addressed solely by installing an external test runner.
   3. C. Testability should be developed alongside the other SUT features.
   4. D. Testability is a test-script concern that cannot affect SUT design.

   Answer: C

   Explanation: The syllabus states: "Testability of the SUT (i.e., availability of software interfaces that support testing, e.g., to enable control and observability of the SUT) should be designed and implemented in parallel with the design and implementation of the other features of the SUT." Early architectural discussion allows test-supporting interfaces to be designed with the product. A runner alone cannot supply missing SUT interfaces.

   Reference: ISTQB Certified Tester Advanced Level Test Automation Engineering Syllabus v2.0 — p. 18, §2.1.1

3. 3How do the project management and test management interfaces of the gTAA differ?

   1. A. Project management maps case definitions; test management tracks development progress.
   2. B. Project management tracks development progress; test management maps case definitions to automated cases.
   3. C. Project management controls SUT protocols; test management provisions the CI/CD environments.
   4. D. Project management provisions testware; test management controls the connection between SUT and TAF.

   Answer: B

   Explanation: The syllabus states: "The project management interface describes the test automation development progress." The adjacent test management description maps test case definitions to automated cases. The alternatives reverse these roles or confuse them with SUT and configuration management interfaces.

   Reference: ISTQB Certified Tester Advanced Level Test Automation Engineering Syllabus v2.0 — p. 23, §3.1.1, gTAA interfaces

4. 4A pilot must determine which of two automation approaches meets the same selected test levels and cases. Both are technically plausible, but their tradeoffs are untested. What pilot activity would support that decision?

   1. A. Build bounded prototypes and compare their pros and cons against the requirements.
   2. B. Declare the first installed approach successful before running the selected cases.
   3. C. Change the required test levels to match whichever prototype is easiest to build.
   4. D. Postpone the comparison until one approach has been deployed across all projects.

   Answer: A

   Explanation: The syllabus states: "Based on the requirements, several different initial prototypes can be created to show the pros and cons of the different approaches." Comparable bounded prototypes provide evidence for selecting a path. Premature commitment, altering requirements merely to fit a tool, or organization-wide deployment before comparison undermines the pilot's goal.

   Reference: ISTQB Certified Tester Advanced Level Test Automation Engineering Syllabus v2.0 — p. 30, §4.1.1

5. 5During a TAF build, a check verifies that data files referenced by test scripts exist at their configured paths. How does this check contribute to the pipeline?

   1. A. It acts as an acceptance test of the SUT's business workflows.
   2. B. It validates the automation project's configuration before execution.
   3. C. It establishes performance efficiency under production traffic.
   4. D. It verifies contracts between the SUT and external services.

   Answer: B

   Explanation: The syllabus states: "These tests are run during the build of a test automation project (TAF/TAS) and check that all paths to the files used in the test scripts are correct, that the files really exist and are located in the specified paths." File/path configuration checks support the TAF/TAS build. They do not establish SUT acceptance, production performance, or service-contract compliance.

   Reference: ISTQB Certified Tester Advanced Level Test Automation Engineering Syllabus v2.0 — p. 34, §5.1.1, Configuration tests

6. 6A state-transition test chooses some steps randomly and occasionally fails. What should its logging capture to help reconstruct the particular failing path?

   1. A. Only the total number of tests that passed in the run
   2. B. Only the test suite name, without the selected path
   3. C. The random choices or numbers used during that execution
   4. D. A new set of random choices produced after the failure

   Answer: C

   Explanation: The syllabus states: "When test cases have random elements (e.g., random parameters or random test steps in state transition testing), the random number/choices should be logged." The executed choices identify the actual path. Totals and suite names cannot reconstruct it, and newly generated choices may describe a different execution.

   Reference: ISTQB Certified Tester Advanced Level Test Automation Engineering Syllabus v2.0 — p. 39, §6.1.1, TAS logging

7. 7A TAE is preparing to verify a test tool on a newly provisioned agent for a particular SUT technology. Which check addresses the compatibility of the installed setup?

   1. A. Verify the tool version, required add-ins, and configuration against the SUT environment.
   2. B. Verify the main executable version and assume matching versions imply matching add-ins.
   3. C. Copy a working agent's configuration and assume it also installs the required add-ins.
   4. D. Verify that the executable starts and assume startup establishes SUT-technology support.

   Answer: A

   Explanation: The syllabus states: "may have optional or required add-ins to ensure compatibility with any given SUT environment." Compatibility can depend on required add-ins and configuration as well as the main tool. Equal executable versions, copied settings, or successful startup do not establish that the required add-ins are present.

   Reference: ISTQB Certified Tester Advanced Level Test Automation Engineering Syllabus v2.0 — p. 44, §7.1.1, Test tool installation

8. 8A test histogram highlights a small group of cases with repeated intermittent failures, alongside their error messages and screenshots. How can the TAE use this information for continuous improvement?

   1. A. Treat the most frequent failing cases as proof of the highest business risk.
   2. B. Change the expected results of those cases to match their latest execution.
   3. C. Identify fragile cases and examine their implementations for refactoring.
   4. D. Conclude that the entire suite is reliable because most cases pass.

   Answer: C

   Explanation: The syllabus states: "The test histogram also enables the TAEs to identify and select those test cases that are fragile and refactor them with additional improvements or by rethinking the actual implementation." Repeated instability identifies improvement candidates. Frequency alone does not establish business risk; changing expected results or generalizing from other passes avoids the actual problem.

   Reference: ISTQB Certified Tester Advanced Level Test Automation Engineering Syllabus v2.0 — p. 48, §8.1.1, Test histogram

9. 9Why should a project budget for automation work after its initial test suite has been delivered?

   1. A. Automation transfers all future test maintenance to the SUT developers.
   2. B. Automated tests adapt to SUT changes without implementation effort.
   3. C. A test automation solution needs ongoing development and maintenance time.
   4. D. Initial automation investment replaces subsequent work on the solution.

   Answer: C

   Explanation: The syllabus states: "Time to develop and maintain a test automation solution" Maintenance remains a cost of automation; delivery does not remove change-related work or automatically transfer responsibility.

   Reference: ISTQB Certified Tester Advanced Level Test Automation Engineering Syllabus v2.0 — p. 15, §1.1.1, disadvantages

10. 10A service can be driven through its API, but tests cannot inspect the resulting internal processing status. How would an interface exposing that status improve testability?

    1. A. It would improve observability by exposing information needed to check results.
    2. B. It would improve controllability by replacing the ability to invoke operations.
    3. C. It would remove the need for expected results when interpreting the status.
    4. D. It would establish testability by preventing tests from accessing system state.

    Answer: A

    Explanation: The syllabus states: "The SUT needs to provide interfaces that give insight into the SUT. Test cases can then use these interfaces to determine whether the actual results equal the expected results." Reading status gives insight for checking outcomes. Driving operations is controllability, while expected results remain necessary and hiding state defeats the stated goal.

    Reference: ISTQB Certified Tester Advanced Level Test Automation Engineering Syllabus v2.0 — p. 18, §2.1.1, Observability