iSQI ISTQB Certified Tester Advanced Level, Test Automation Engineering CTAL-TAE Exam Questions

Page: 1 / 14
Total 80 questions
Question 1

Which of the following descriptions of what some test automation tools can be used to do is TRUE?



Answer : D

TAE recognizes a range of supporting capabilities offered by test tools beyond pure scripted execution, including reporting, evidence capture, and run artifacts that help stakeholders understand what was tested. Video recording of UI test sessions is a common feature in several UI automation ecosystems and cloud device/browser platforms, used to provide visual evidence of steps performed, failures observed, and the application's look-and-feel during execution. This supports debugging and communication with non-technical stakeholders. Option A overstates what test automation tools do: autonomously designing intuitive UIs and evaluating UX is largely outside typical test automation tool scope and requires human-centered design methods. Option C is also overstated: exploratory testing is inherently human-driven; tools can assist (session notes, heuristics support, telemetry) but do not truly conduct exploratory testing autonomously based on charters in the general TAE framing. Option B touches on advanced analytics and AI/ML-assisted quality insights; while some platforms offer risk prediction features, the phrasing implies broad predictive defect capability, which is not a standard, dependable tool function emphasized in TAE compared with concrete capabilities like artifact capture. Therefore, the clearly true, commonly supported capability is making video recordings of UI testing sessions.


Question 2

(In User Acceptance Testing (UAT) for a new SUT, in addition to the manual tests performed by the end-users, automated tests are performed that focus on the execution of repetitive and routine test scenarios. In which of the following environments are all these tests typically performed?)



Answer : C

TAE distinguishes test environments by purpose and risk. User Acceptance Testing is typically performed in an environment that is as production-like as feasible (configuration, data shape, integrations) but still controlled and safe for testing activities. This is commonly referred to as preproduction (often ''staging''): it supports realistic end-to-end flows, allows business users to validate that the SUT meets acceptance criteria, and enables running routine/repetitive automated checks without risking live operations. A build environment is focused on compiling/packaging and basic verification, not business acceptance. An integration environment is used to validate interactions among components/systems, but may not reflect full production-like configuration, and it's often shared and volatile---less suitable for formal acceptance activities involving end users. Production is generally avoided for UAT because acceptance testing can alter live data, disrupt users, and introduce unacceptable business risk; production testing is typically limited to tightly controlled smoke checks, monitoring, or specific ''in-production'' validation patterns with strong safeguards. Therefore, the environment in which both end-user manual UAT and supporting automated routine scenarios are typically executed is the preproduction environment, aligning with TAE's guidance on balancing realism with risk containment.


Question 3

(Which of the following answers describes the LEAST relevant concern in selecting suitable test automation tools for a test automation project?)



Answer : C

TAE tool selection focuses on factors that materially affect feasibility, total cost of ownership, and long-term sustainability of the Test Automation Solution (TAS): technical fit, skill fit, integration capability, licensing/legal constraints, and cost model. Option A is directly relevant because the team's capability strongly influences whether a code-heavy tool and framework approach is realistic and maintainable. Option B is relevant because licensing constraints can affect usage rights, redistribution, modification, internal compliance, and legal risk---critical for tool adoption in many organizations. Option D is also highly relevant because commercial licensing costs and licensing models (named user vs. floating, execution limits, parallelism add-ons, feature tiers) impact budgeting and scaling, and therefore the project's viability. Option C, while important for general team effectiveness, is not a primary criterion for selecting automation tools; it does not describe tool capability, integration constraints, cost, or risk in a way that distinguishes one tool from another. TAE typically treats team collaboration/communication and roles as project and organizational concerns (e.g., governance and processes) rather than tool-selection criteria. Therefore, among the provided choices, ''team personality mix'' is the least relevant concern for choosing suitable test automation tools in a TAE-focused tool selection.


Question 4

Which of the following statements about the relationship between TAA, TAS and TAF is true?



Answer : A

In TAE terminology, the Test Automation Architecture (TAA) is the conceptual, high-level blueprint that describes how automation will be structured, what layers exist, how components interact, and how the automation connects to the SUT and supporting systems. The Test Automation Solution (TAS) is the concrete realization of that architecture in a specific context---tools, infrastructure, pipelines, conventions, and components assembled to deliver automated testing capability. The Test Automation Framework (TAF) is a structured set of reusable libraries, guidelines, and mechanisms that supports efficient development, execution, reporting, and maintenance of automated tests; it is commonly a key part used to build the TAS. TAE documents commonly present this relationship as: TAA (design) implemented as TAS (solution) constructed using one or more TAFs (framework elements) plus tools and environment components. Options B, C, and D invert these relationships and misrepresent the concept that architecture is implemented by a solution, not the other way around. Therefore, the statement that a TAF can be used to implement a TAS, which is an implementation of a TAA, is the correct relationship.


Question 5

Consider a TAS aimed at implementing and running automated test scripts at the UI level on web apps. The TAS must support cross-browser compatibility for a variety of supported browsers, by ensuring that the same test script will run on such browsers in the same way without making any changes to it. This is achieved by introducing appropriate abstractions into the TAA for connection and interaction with different browsers. Because of this, the TAS will be able to make direct calls to the supported browsers using each different browser's native support for automation. Which of the following SOLID principles was adopted?



Answer : A

The scenario describes introducing abstractions so that test scripts do not depend directly on concrete browser-specific automation implementations. Instead, tests depend on an abstraction (e.g., a ''BrowserDriver'' interface), while each concrete browser implementation (Chrome, Firefox, Edge, etc.) provides its own adapter using native automation support. This is a classic application of the Dependency Inversion Principle (DIP): high-level modules (test scripts and business-level actions) should not depend on low-level modules (specific browser drivers); both should depend on abstractions. Additionally, details (browser-specific integrations) depend on the abstraction, not the reverse. TAE emphasizes that this reduces coupling and improves maintainability: you can add or update browser implementations with minimal impact on test definitions. While Open-Closed is also supported (extending with new browser adapters without modifying existing tests), the key phrase ''introducing appropriate abstractions'' specifically to decouple tests from concrete drivers is DIP. Liskov Substitution relates to substituting implementations without breaking correctness, and Interface Segregation concerns keeping interfaces small and specific---neither is as directly targeted by the described architectural decoupling. Therefore, the SOLID principle most clearly adopted is Dependency Inversion.


Question 6

Which of the following layers within the TAA contains technology-specific implementations that enable automated tests to have the execution of their logical actions result in actual interaction with the appropriate interfaces of the SUT?



Answer : D

TAE describes layered automation architectures where higher layers express intent and test logic, while lower layers handle concrete interaction with specific technologies and interfaces. The test adaptation layer is the layer that ''adapts'' abstract test actions to the real SUT interaction mechanisms. It typically contains technology-specific adapters, drivers, wrappers, or connectors (e.g., browser drivers, mobile automation bridges, API clients, message-bus connectors, database utilities) that translate logical operations like ''click login,'' ''submit order,'' or ''query customer'' into the correct low-level calls for the target interface. This is where the details of protocols, locator strategies, synchronization primitives, data access methods, and tool-specific APIs live, shielding higher layers from churn when technologies change. The test execution layer is responsible for orchestrating execution (running suites, scheduling, collecting results, reporting), but not primarily for implementing the technology-specific SUT interaction itself. The test definition layer focuses on how tests are specified (scripts, keywords, models, data), and the test generation layer concerns deriving tests (e.g., model-based generation). Therefore, the layer containing technology-specific implementations enabling actual interaction with SUT interfaces is the test adaptation layer.


Question 7

An automated test script makes a well-formed request to a REST API in the backend of a web app to add a single item for a product (with ID = 710) to the cart and expects a response confirming that the product is successfully added. The status line of the API response is HTTP/1.1 200 OK, while the response body indicates that the product is out of stock. The API response is correct, the test script fails but completes, and the message to log is: The product with ID = 710 is out of stock. Cart not updated. When this occurs, you are already aware that both the failed test and the API are behaving correctly and that the problem is in the test data. The TAS supports the following test logging levels: FATAL, ERROR, WARN, INFO, DEBUG. Which of the following is the MOST appropriate test logging level to use to log the specified message?



Answer : D

TAE logging guidance focuses on making logs actionable while reflecting severity and intent. Here, the test failed due to an expected, non-system fault condition: the product is out of stock, which is a valid business-state response and confirms the API behaved correctly. The issue is that the test data (product availability) did not satisfy the test's precondition. This is not a fatal condition (FATAL) because execution continues and the overall system is not unusable. It is not best treated as ERROR either (not offered as an option here) because an error-level message usually indicates a defect, malfunction, or unexpected failure needing immediate engineering attention. INFO would be too low because it may be lost among normal run messages and does not adequately flag that the test outcome is affected by a precondition violation requiring action (e.g., reseeding data, choosing a different product ID). DEBUG is typically reserved for highly detailed diagnostic traces intended for deeper troubleshooting, not for highlighting a test-data problem affecting test validity. WARN is intended for abnormal or noteworthy conditions that do not indicate a product defect but may require attention to maintain test reliability. Therefore, WARN is the most appropriate level.


Page:    1 / 14   
Total 80 questions