30 free ISTQB CTAL-TAE practice questions from the CertStash pack of 120, each with the correct answer and a full explanation. The rule is the same for every exam: ten free on the product page, 30 free here, all 120 in the pack, and each step includes the one before it.
Get all 120 questions (US$39) · Download the first 10 as a PDF
Question 1
You have been asked to develop test automation for a legacy system that is going to go through a series of infrastructure migrations. The scripts will be used to verify basic functionality during these infrastructure changes. Your Test Analysts have some programming skills and need a solution that is simple and fast. Maintainability of the scripts is not a consideration because no changes to the software are anticipated. Which of the following is the BEST scripting approach in this situation?
Show answer and explanation
Correct answer: D. Linear scripting.
Linear scripting is the simplest and fastest scripting approach in the TAE syllabus: each test is a straight sequence of steps, usually recorded and then lightly edited, with no shared libraries. It needs little programming skill and its poor maintainability does not matter here because the software will not change.
Why the other options are wrong
- A. Structured scripting adds reusable libraries and control structures to improve maintainability, which costs extra time and effort not needed in this case.
- B. Capture-replay is a way of creating scripts rather than a scripting approach in the syllabus, and linear scripting already includes recording where helpful.
- C. Model-based scripting needs models to be built and maintained, making it the most complex and slowest option to set up.
Question 2
If model-based testing has been selected for the overall test automation approach for a project, how does that influence the layers of the TAA?
Show answer and explanation
Correct answer: A. All layers are used, but the test generation layer will be automated based on the defined model.
When model-based testing is selected, all layers of the Test Automation Architecture are still used, but the key difference is that the test generation layer becomes automated based on the defined model. The model drives the automatic creation of test cases, reducing manual test design effort. All other layers, definition, adaptation, execution, and reporting, continue to function, but the generation layer's operation is fundamentally transformed by model-driven automation.
Why the other options are wrong
- B. The execution layer is essential for running generated tests and cannot be eliminated in any TAA approach.
- C. Adaptation is still needed to bridge the gap between the generated tests and the actual system interfaces.
- D. API tests must still be designed; the model generates tests based on defined behavior, not API interfaces automatically.
Question 3
What is the PRIMARY advantage of using abstraction in the TAA?
Show answer and explanation
Correct answer: A. It makes it more flexible for future reuse and improvements.
The primary advantage of using abstraction in the Test Automation Architecture is that it makes the framework more flexible for future reuse and improvements. Abstraction separates the test logic from implementation details, allowing test scripts to remain stable when the underlying system or tool changes. This separation enables components to be reused across different tests and projects, and facilitates maintenance and evolution of the automation framework over time.
Why the other options are wrong
- B. Higher skill requirements are a disadvantage, not an advantage, of abstraction.
- C. Abstraction does not guarantee support for all scripting methods; it is an architectural principle applied within chosen methods.
- D. Abstraction can improve maintainability and flexibility but does not directly improve runtime performance of tests.
Question 4
When if the BEST time for automation to consider legal and/or standard requirements for a SUT?
Show answer and explanation
Correct answer: C. When designing a TAA.
The best time to consider legal and standard requirements for a System Under Test is when designing the Test Automation Architecture. At this architectural level, the overall framework is being planned to support the testing strategy. Addressing legal and standard requirements during TAA design ensures that compliance, security, traceability, and regulatory concerns are built into the automation foundation from the start, rather than being retrofitted later.
Why the other options are wrong
- A. Legal requirements belong in test automation planning, not in SUT implementation.
- B. Test Automation Framework design is too specific; requirements must be considered at the higher architectural level.
- D. Test Automation Scripts development is too late to incorporate legal and standard requirements into the overall automation approach.
Question 5
You are working on a web-based application called Book Vault that allows people to upload books and order books. This application must be available on all major browsers. You have been testing the application manually and management have asked you to consider automating some of the tests. You have investigated a number of commercial and free tools which can automate tests at a web browser level and one tool in particular meets your requirements and you have implemented a trial version. You have basic programming skills and the main goal is to automate a few functional tests to see if the tool is compatible with the application and can recognise the objects and controls. Which scripting technique would be MOST suitable in this scenario in order to meet the objectives?
Show answer and explanation
Correct answer: B. Capture-replay scripting.
Capture-replay scripting is the most suitable technique for this scenario. The goal is to quickly test tool compatibility with the application and verify that the tool can recognize objects and controls on a web-based application. Capture-replay allows testers with basic programming skills to rapidly record user interactions and replay them, providing immediate feedback on tool functionality without requiring complex script development. This trial implementation approach is ideal for capture-replay's strengths.
Why the other options are wrong
- A. Structured scripting requires more programming skill and design effort than needed for a compatibility trial.
- C. Data-driven scripting is designed for testing multiple data scenarios, not for tool compatibility assessment.
- D. Model-based scripting is overly complex for a quick trial phase with basic programming skills.
Question 6
You are working on a government system called “Making Tax Digital” or MTD for short. This system is being implemented to stop manual human input error and also to reduce fraudulent behaviour from companies when submitting their tax and VAT returns. The key concept is that registered companies will need to use government recommended 3rd party software for their accounts and book keeping. These 3rd party applications will have a direct interface into the government’s main system for transactions and submissions. You have been using a test execution tool successfully on the project so far, and have implemented a basic “capture/replay” approach to scripting. The management have been encouraged with the automation so far, but want the following objectives to be met: Test cases added easily Reduction in the amount of scripts and script duplication Reduction in maintenance costs Which scripting technique would be MOST suitable in this scenario in order to meet the objectives?
Show answer and explanation
Correct answer: D. Keyword-driven scripting.
Keyword-driven scripting is the most suitable technique to meet all three objectives. It reduces script duplication by using reusable keywords, allows test cases to be added easily through keyword combinations without writing new code, and significantly reduces maintenance costs because changes to application behavior only require updating the keyword implementation, not every individual script. This approach is specifically designed to address the maintenance and scalability challenges of capture-replay automation.
Why the other options are wrong
- A. Linear scripting involves coding each test separately and would not reduce duplication or maintenance costs.
- B. Structured scripting improves organization but does not as effectively reduce duplication or simplify test case addition.
- C. Data-driven scripting focuses on varying test data rather than reducing script duplication or simplifying test case creation.
Question 7
You are implementing test automation for a project that has a business critical application. A test execution tool is being used to run automated regression tests. The results from the test execution tool are very important and need to be 100% accurate. You want to merge the test automation results with the test management system that also records the manual test results so that managers can make informed decisions about the progress quickly. Which layer of the gTAA will be used to ensure the proper reporting occurs and the interfaces to the test management system are handled?
Show answer and explanation
Correct answer: C. The execution layer.
In the generic test automation architecture, the test execution layer runs the tests and also covers test logging and test reporting. It is therefore the layer that produces accurate results and handles the interface for passing them to the test management system alongside the manual results.
Why the other options are wrong
- A. There is no separate reporting layer in the gTAA; reporting is a function of the test execution layer.
- B. There is no separate logging layer in the gTAA; logging is also handled within the test execution layer.
- D. The test adaptation layer connects the test scripts to the system under test and does not handle reporting to test management.
Question 8
You are implementing test automation for a project and you want to be able to generate test cases automatically using a series of test design tools which use a variety of test design techniques such as decision tables, pairwise testing and boundary value analysis. You also want to generate test data automatically which can then be used by the tests. Initially these tests will be run manually to verify their correctness and ultimately you want to include them in the test execution tool so that they can run unattended. Which layer of the gTAA will be used to support the specification of the test cases and preparation of the test data?
Show answer and explanation
Correct answer: B. The definition layer.
The definition layer of the Test Automation Architecture is used to specify test cases and prepare test data. This layer provides the capability to define test cases using various test design techniques and to prepare test data that can be used by tests. While the generation layer may automate certain aspects, the definition layer is where test cases and test data specifications are actually captured and managed, whether they will be run manually initially or later executed by test execution tools.
Why the other options are wrong
- A. The generation layer automates the creation of tests based on definitions, but the initial specification and data preparation occur in the definition layer.
- C. The execution layer runs tests but does not manage test case specification or test data preparation.
- D. The adaptation layer handles interfaces between tests and the system, not test case definition or data preparation.
Question 9
Which of the following is considered a disadvantage of test automation?
Show answer and explanation
Correct answer: A. Automated exploratory testing is difficult to implement.
Automated exploratory testing is difficult to implement because exploratory testing inherently requires human creativity, intuition, and adaptive decision-making that cannot easily be scripted or automated. Exploratory testing involves simultaneous test design and execution with real-time learning, which conflicts with the predetermined nature of automation. Options B, C, and D mischaracterize automation: test automation does not distract from bug-finding (it enhances it), automated tests have fewer operator errors than manual testing, and automation typically provides faster feedback, not slower.
Why the other options are wrong
- B. Test automation supports bug-finding rather than distracting from it; the objective and the tool work in alignment.
- C. Automated tests eliminate operator errors during execution; human operators cause more errors than automated scripts.
- D. Automation provides faster feedback on system quality by executing tests quickly and consistently, not slower feedback.
Question 10
The Test Automation Manager has asked you to provide a solution for collecting metrics from the TAS that measures code coverage every time the automated regression test pack is run. The metrics must be trend based to ensure that the scope of the regression test pack continues to reflect enhancements made to the SUT - coverage must not drop and should ideally increase. The solution must be as automated as possible to avoid unnecessary manual overheads and errors. Which of the following approaches would BEST meet these requirements?
Show answer and explanation
Correct answer: C. The automated testware would record overall code coverage for each run, export the data to a pre-formatted Excel spreadsheet that automatically updates a trend analysis bar chart for you to distribute to stakeholders.
Option C meets all requirements: it automates code coverage collection from each test run, exports data to Excel for persistent trend tracking, and automatically updates a trend analysis chart for stakeholder distribution. This eliminates manual overhead while providing the trend-based visibility needed to ensure regression test scope remains adequate as the SUT evolves. The automated chart generation ensures stakeholders can easily identify whether coverage is increasing, stable, or declining.
Why the other options are wrong
- A. Incorrect premise that automated tests cannot measure SUT code coverage; modern test automation frameworks can instrument and measure coverage of the system under test.
- B. Requires manual chart creation and presentation, adding unnecessary overhead and not providing the automated trending analysis required.
- D. Tracks test case pass/fail rates rather than code coverage, which does not address the requirement to measure and trend the scope of regression testing against SUT enhancements.
What people say about the full CTAL-TAE pack 5.0 from 1
Cert Stash iSQI Advanced Level Test Automation Engineer CTAL-TAE practice questions cover most of questions and answers of real test.
Question 11
Your organisation has successfully implemented a Test Automaton Solution (TAS) for a new project which has since been delivered into production via a number of sprints. A series of maintenance releases are now planned. Some improvements were made to the Test Automation Architecture (TAA) as a result of feedback from the early sprints. The TAA improvements affected the TA, and the TAS was changed for the final sprint. The new version of the TAS was generally well received but some performance and usability issues were encountered with the TAS which have yet to be addressed. The test automation engineers supporting the maintenance releases must decide whether to use the enhanced TAS or the version that was used successfully for previous sprints. What is the BEST action to take next?
Show answer and explanation
Correct answer: A. Perform an analysis of risks versus benefits for the enhanced TAS and then decide which version to use.
The best action is to perform a formal analysis of risks versus benefits for the enhanced TAS and then make an informed decision based on that analysis. This approach systematically weighs the advantages of the improved TAA and TAS features against the known performance and usability issues. Rather than making an emotional decision based on risk aversion or assuming new is always better, a structured risk-benefit analysis provides the decision-making framework needed for a live system supporting maintenance releases. This analysis should consider the severity of unresolved issues, the potential benefits, and mitigation strategies.
Why the other options are wrong
- B. Refusing to use the enhanced version dismisses potential improvements without analytical evaluation of whether benefits outweigh known issues.
- C. Using the new version without analysis ignores that unresolved performance and usability issues could harm production systems and customer experience.
- D. Trial-and-switch approach creates operational instability and inconsistency in testing approaches across maintenance releases, complicating defect correlation and system understanding.
Question 12
You have implemented a keyword-driven scripting framework, which uses a test execution tool to run the tests. This has been in use for the past year and all of the teams now use this framework as the standard approach for test execution. The teams all work on different aspects of the SUT and they have all experienced significant benefits in the use of this scripting framework. However, on closer examination, you have discovered that there are numerous instances where the teams have the same functionality to test but are using different keywords. One of your objectives for improvement is to create consistency among the teams. What is the BEST way to handle this situation?
Show answer and explanation
Correct answer: D. Create a central library of keywords and associated definitions for each team to use.
A central library of keywords with standardized definitions ensures all teams use consistent terminology and implementation for the same functionality, eliminating redundancy and improving maintainability. This approach preserves the benefits each team has experienced while enabling knowledge sharing and reducing duplication across teams working on different SUT aspects.
Why the other options are wrong
- A. Moving to model-based scripting introduces significant change and overhead when the current keyword-driven framework is already successful and beneficial.
- B. Ignoring duplicate keywords across teams misses an opportunity to improve efficiency, maintainability, and team collaboration.
- C. Guidelines and naming conventions alone do not enforce consistency or prevent teams from continuing to create duplicate keywords in isolation.
Question 13
Which ONE of the four layers of the test automation architecture provides an optional capability?
Show answer and explanation
Correct answer: A. Test generation layer.
The test generation layer is the optional capability within the four-layer test automation architecture. The test definition, test execution, and test adaptation layers are all essential and standard components. Test generation (automatically creating test cases) is an advanced optional capability that not all automation frameworks implement, whereas the other three layers are fundamental to any test automation solution.
Why the other options are wrong
- B. The test definition layer is mandatory for specifying what will be tested.
- C. The test execution layer is mandatory for running automated tests.
- D. The test adaptation layer is mandatory for adjusting tests to different environments and configurations.
Question 14
You have inherited a TAS that is working well. It uses keyword-driven scripting and was well architected. The automation architect who built the system has now moved on to another company. The TAS is working across several projects and has a multiple library of keywords, categorized by project. The individual project teams maintain these keyword scripts. Based only on the given information, what is the MOST significant risk for the TAS?
Show answer and explanation
Correct answer: B. The level of abstraction, coupled with the departure of the architect may make the system hard to maintain.
The most significant risk is that the level of abstraction combined with the departure of the architect makes the system hard to maintain. Keyword-driven scripting creates a high level of abstraction that requires deep architectural knowledge to understand, modify, and extend effectively. When the architect who designed this system departs, the organization loses critical knowledge about how the system is structured, why decisions were made, and how to adapt it to new requirements. This knowledge gap poses the greatest risk to long-term TAS viability and sustainability.
Why the other options are wrong
- A. Keyword scripts becoming outdated is a maintenance burden but a manageable one with proper processes, not the most significant risk identified.
- C. New project compatibility is a concern but is secondary to understanding and maintaining the existing system architecture.
- D. Inconsistent coding standards across teams is a quality issue but is less critical than the fundamental risk of losing architectural understanding.
Question 15
New features have been added for the current release of a SUT. Which action would NOT be appropriate for the TAE to perform when evaluating the impact on the TAS?
Show answer and explanation
Correct answer: A. Gather feedback from the Business Analysts to determine if the current TAS will meet the needs of the new features.
Gathering feedback from Business Analysts about whether the current TAS meets new feature needs is not appropriate because Business Analysts define test requirements, not TAS capability evaluation. The TAE independently evaluates technical impact by reviewing keywords, running tests, and assessing tool compatibility. Business Analyst feedback informs what tests are needed, not whether technical modifications are necessary.
Why the other options are wrong
- B. Reviewing keywords for necessary modifications is essential impact assessment.
- C. Running existing tests against updated SUT is critical to identify required changes.
- D. Evaluating tool compatibility and identifying alternatives is necessary technical due diligence.
Question 16
You are testing a major enhancement to an air traffic control user interface. You have use of a sophisticated pre-production test environment, created specifically for large scale automated regression, performance and security testing. The window for regression testing is limited and must successfully conclude, with no major regressions remaining, before the non-functional testing starts. You have been using the same version of the TAS for the last few releases, each time completing the automated regression test suite in a single overnight run. However, due to the latest enhancements for the SUT, you believe there is a risk that the test suite may no longer complete overnight and therefore delay performance and security testing. Which option would be the BEST and MOST cost-efficient approach to mitigate this risk?
Show answer and explanation
Correct answer: C. Analyse the regression test suite and remove test coverage duplication and redundancy.
Analyzing the regression suite to remove duplication and redundancy is the most cost-efficient approach to reduce execution time without infrastructure investment. This improves test suite quality, maintainability, and execution speed while addressing the root cause of excessive test duration rather than adding resources or infrastructure.
Why the other options are wrong
- A. Creating a mirror environment requires significant capital investment and ongoing infrastructure costs that are unnecessary if test suite inefficiencies can be remedied.
- B. Splitting execution across consecutive nights does not solve the underlying problem and extends the testing window, delaying performance and security testing.
- D. Improving coding practices is beneficial but does not directly address the fundamental issue of test suite bloat and does not guarantee the necessary performance improvement.
Question 17
You are employed as a TAE on a project to build a purchasing system. The main requirements for the system are to: Allow users to enter details of items that they wish to have purchased and, from these details, create a purchase request. Take each purchase request through a workflow that will allow the requestor’s line manager to approve the request, reject it or return it for clarification / modification. Forward approved requests to the Purchasing Department. Allow purchasers to find the best available supplier and place the request on that supplier as a purchase order. Requirement 1 has now been delivered and has been satisfactorily tested manually. In parallel, you have developed a TAS so that functional suitability testing can be automated. You have just conducted a pilot of the TAS on the implementation of Requirement 1 and several things went wrong: One test failed because some reference data that it needed was missing, this and several other failures were difficult to diagnose. Another test failed unexpectedly because an old version of the script was used. Which THREE measures could mitigate these risks during deployment? Full test logging down to and including trace level Identification and correct configuration of all firewalls Automated creation and loading of all data to meet test preconditions Provision of proper device configuration plans Careful packaging with thorough configuration management
Show answer and explanation
Correct answer: B. a, c and e.
The three measures that directly mitigate the identified risks are: (a) Full test logging down to trace level addresses the difficulty in diagnosing failures when reference data is missing; (c) Automated creation and loading of test data ensures preconditions are met and eliminates missing reference data failures; (e) Careful packaging with configuration management prevents the use of wrong script versions. These three measures directly address the root causes of the pilot failures: lack of visibility into failures, missing test data, and version control issues.
Why the other options are wrong
- A. Firewall configuration is unrelated to the identified pilot failures about data and script versions.
- C. Device configuration plans do not address the specific issues of missing data and script versioning.
- D. Firewall configuration and device plans are infrastructure concerns unrelated to the data and version control problems encountered.
Question 18
Your company is new to test automation and as TAE, you have designed a TAS which successfully supports the SUT for the current project. There are other systems currently in operation which have been tested manually and more systems are planned over the coming years. Based on this success, your company requires test automation be rolled out to other current and future SUTs with consistency being a key objective. Which of the following is the BEST way to achieve that?
Show answer and explanation
Correct answer: B. Install the current TAS into a central repository so that other tests on different SUTs use the same version of the TAS.
Installing the proven TAS into a central repository enables all teams across current and future systems to use the same standardized version, ensuring consistency while building on a successful foundation. This approach maximizes reuse and reduces the overhead of developing and managing separate TAS instances for each system.
Why the other options are wrong
- A. Designing a new TAS for each SUT defeats the consistency objective and multiplies development and maintenance costs and effort.
- C. Checking connectivity validation is a technical task that does not address the consistency objective for TAS rollout.
- D. Tracking automation failures produces visibility but does not create the consistency needed across different SUTs.
Question 19
You are evaluating several test modelling tools and are wanting to automatically generate test cases within the tool where many different combinations of input data are created. You are then wanting to export the test cases into a .csv file which can then be read by a functional test execution tool using a data-driven or keyword-driven scripting method. You have investigated several tools and there is only one tool that provides all the necessary features defined by your team with the exception of the export facility. It does not provide an export into either .xls or .csv formats. What would be the BEST next step regarding the selection of this tool?
Show answer and explanation
Correct answer: C. Ask the vendor and use forums to see if a solution is available or going to be available in the future.
The best approach is to contact the vendor and explore community forums to determine whether the export limitation is solvable through an existing feature, third-party solution, or planned update. Many tool vendors provide export capabilities through plugins, APIs, or workarounds that may not be immediately obvious. This preserves the ability to use a tool that meets all other requirements while addressing the specific gap. Only after confirming no viable solution exists should the team consider alternatives, create custom solutions, or resort to manual processes.
Why the other options are wrong
- A. Abandoning the tool immediately ignores the possibility of vendor support; it may be premature to switch if a solution exists.
- B. Building a custom export facility is a last resort after vendor options are exhausted; it adds maintenance burden.
- D. Manual CSV generation defeats the purpose of test automation and is inefficient for a tool that otherwise meets requirements.
Question 20
In order to achieve reuse of a TAS, where SHOULD the design for reuse occur?
Show answer and explanation
Correct answer: D. At the TAA level.
Design for reuse of a Test Automation Solution (TAS) should occur at the Test Automation Architecture (TAA) level. The TAA provides the foundational structure and design patterns that enable TAS components to be reused across multiple projects and implementations. When reusability is architected at the TAA level, it creates standardized interfaces, frameworks, and patterns that can be leveraged by various TAS implementations.
Why the other options are wrong
- A. Code-level design is too granular and specific to individual implementations to provide meaningful organizational reuse.
- B. Framework level is an implementation detail beneath the architectural decisions that govern reusability strategy.
- C. The TAS itself is the output of the architecture, not the appropriate level at which to design for reuse.
Question 21
Which option correctly pairs test automation design principles and patterns with their characteristics? Hides implementation details to expose only what the testers need to create in their test cases. Creates a class file so that updates to locators need to be made in only one place. Includes the idea that components should be freely substitutable with no adverse impact. Introduces an additional facade which stores user actions that interact with page objects. Facade pattern. SOLID. Flow model. Page object model.
Show answer and explanation
Correct answer: B. 1a, 2d, 3b, 4c
The correct pairing is: (1) Hides implementation details → Page object model (a), which abstracts UI elements so testers interact only with meaningful objects; (2) Creates a class file for locators → SOLID (d), specifically the Single Responsibility Principle ensures locator maintenance is centralized; (3) Freely substitutable components → Facade pattern (b), which demonstrates the Liskov Substitution Principle; (4) Additional facade for user actions → Flow model (c), which records and organizes user interaction sequences. These pairings correctly match design patterns with their defining characteristics.
Why the other options are wrong
- A. This pairing incorrectly matches facade with hiding implementation details and flow model with substitutability.
- C. This pairing reverses several correct associations and does not properly match principles to their characteristics.
Question 22
When a continuous integration / continuous deployment (CI/CD) pipeline is split between build and deployment phases, which statements are TRUE? Component and component integration tests are part of the deployment phase. System and higher-level tests may be part of the build phase. Component and component integration tests are part of the build phase. System and acceptance tests may be executed in a separate pipeline. System integration tests cannot be run in this kind of pipeline.
Show answer and explanation
Correct answer: B. c and d.
In a CI/CD pipeline split between build and deployment phases, component and component integration tests are part of the build phase (statement c), where code quality and unit-level functionality are verified early. System and acceptance tests may be executed in a separate pipeline (statement d), often running after deployment in staging or production-like environments. Component tests belong in build for fast feedback, while higher-level system and acceptance tests typically run post-deployment, making them suitable for separate pipelines.
Why the other options are wrong
- A. Statement a is false; component tests are part of build, not deployment.
- C. Statement b is false; system tests are typically part of deployment or separate pipelines, not build.
- D. Statement e is false; system integration tests can absolutely run in split pipelines, typically in the deployment phase.
Question 23
Your project is transitioning from manual to automated testing. You have decided to implement a pilot project so that lessons learned can inform future time estimates and schedules. Which two of the following represent the types of test cases that are MOST suited to a test automation pilot project? High added value test cases that require little effort to automate. Test that are run infrequently as these will be simpler to automate. Reliability test cases that can show added value soon. Technically challenging test cases to provide the best validation of manual test conversion. Tests that are least important to the business as these are safer to trial.
Show answer and explanation
Correct answer: B. a and c.
High added-value test cases with low automation effort provide rapid ROI and demonstrate value quickly to stakeholders, while reliability test cases that show immediate value build confidence in automation capability. These selections maximize early success and lesson learning. Infrequently-run tests provide limited ROI, technically challenging cases risk pilot failure, and low-priority tests do not showcase automation value.
Why the other options are wrong
- A. While high-value cases are appropriate, infrequently-run tests do not justify automation economics and provide minimal ROI benefits.
- C. Infrequently-run tests have poor automation ROI, and technically challenging cases risk project failure before capturing lessons learned.
- D. Low-importance tests do not demonstrate business value and fail to build stakeholder confidence in the automation approach.
Question 24
Your functional regression test automation suite ran successfully for the first two sprints and no failures were encountered during the runs. The automation suite records the status of each test case as either ‘pass’ or ‘fail’ and has excellent recovery capability built in. For the third sprint, the TAS log reported several test cases with a status of ‘fail’. You investigated each test case and found that most failures were due to a defect in one of the keyword scripts, rather than in the SUT. For those where the failure was in the SUT, defect reports were raised but several were returned by the developers asking for more information to enable them to reproduce the problem. Which additional log items SHOULD you add to the TAS that would BEST improve failure analysis and defect reporting for future sprints? Dynamic measurement information about the SUT. A status of ‘TAS error’, in additional to ‘pass’ and ‘fail’, for each test case. Use of a colour coding scheme so that ‘pass’ is in red and ‘fail’ is in green. A counter to determine how many times each test case has been executed. System configuration information including software/firmware and operating system versions. A copy of the source code for all Keyword scripts executed.
Show answer and explanation
Correct answer: A. a and b.
Adding dynamic measurement information about the SUT and a 'TAS error' status enables better failure analysis. Dynamic measurements help developers reproduce issues by capturing system state during failures, while the 'TAS error' status distinguishes automation framework failures from SUT defects and keyword script defects, reducing developer requests for clarification. This directly improves defect reporting quality without adding unnecessary overhead.
Why the other options are wrong
- B. Execution counters and source code copies do not improve root cause analysis; source code copies are particularly inappropriate as they create maintenance burden and security concerns.
- C. Colour coding (red for pass, green for fail) is backwards from standard conventions and provides no analytical value for failure diagnosis.
- D. While system configuration is valuable, source code copies for all keyword scripts creates excessive overhead and maintenance issues without improving defect analysis.
Question 25
Which statements about a continuous integration / continuous deployment (CI/CD) pipeline are TRUE? The pipeline can contain configuration tests for the TAF/TAS. The pipeline cannot contain configuration tests for the TAF/TAS. Component and component integration tests should be run separately. The pipeline can contain system integration tests. The pipeline cannot contain system integration tests.
Show answer and explanation
Correct answer: A. a and d.
A CI/CD pipeline can contain configuration tests for the Test Automation Framework/Test Automation Suite (TAF/TAS), ensuring the testing infrastructure itself is properly configured and functional (statement a is true). System integration tests can be part of the pipeline, either in later stages of the build phase or in the deployment phase (statement d is true). These tests validate that the application and its environment are correctly set up. Component and component integration tests should be run together as part of the build phase for rapid feedback.
Why the other options are wrong
- B. Statement b is false; pipelines can contain TAF/TAS configuration tests. Statement c is false; component and integration tests should run together in build, not separately.
- C. Statement b is false; pipelines can contain configuration tests. Statement e is false; system integration tests can and should run in pipelines.
- D. Statement e is false; system integration tests are a valid and important part of CI/CD pipelines.
Question 26
You have investigated a new tool which enables the modelling of the SUT and can then generate test cases either manually or automatically. You have convinced your managers that the best way forward is to conduct a pilot project for this tool. You need to select a project to use for the pilot. You have the choice of the following projects: Project A: A two-year project that is critical to the business and is currently in the requirement phase. This project is for a new e-commerce web site and is mostly being developed “in-house” although the payment system is being developed and delivered by a 3rd party provider. Project B: A safety critical application for software to drive and park cars. Project C: An upgrade to an important HR timesheet tracking application that will be available on a desktop and mobile application. This is a 1month project developed in-house. Project D: The payment system from project A. Which project would be BEST for the pilot?
Show answer and explanation
Correct answer: C. Project C because it is a short, low priority project but is important.
Project C is the best choice for piloting a new test automation modeling tool because it is a short, bounded project (one month) with managed scope and relatively lower business criticality compared to alternatives. Pilot projects should be contained in scale to allow experimentation and learning without catastrophic business impact if issues arise. Project C being in-house developed provides better control and flexibility for the pilot. The short duration allows for rapid feedback and iteration on the tool approach before applying it to larger initiatives.
Why the other options are wrong
- A. A two-year critical business project in requirements phase is too large and risky for an unproven tool pilot, and the business impact of failure is too high.
- B. Safety-critical systems require proven, stable automation solutions and carry unacceptable risk for experimental tool pilots.
- D. While the payment system is smaller, piloting on only a third-party component limits learning applicability and does not demonstrate the tool's full value across the organization.
Question 27
When choosing an automation tool, which would be the BEST option for automation testers who have programming skills?
Show answer and explanation
Correct answer: B. A tool whose programming language matches that of the system under test.
When automation testers have programming skills, the best practice is to choose a tool whose programming language matches the system under test. This leverages their existing expertise, ensures consistency with the development environment, facilitates code reuse and integration with the SUT, and enables more effective debugging and maintenance of test scripts.
Why the other options are wrong
- A. Low-code or no-code solutions are designed for testers without programming skills and do not leverage programming expertise.
- C. Open-source automation tools are often excellent choices for skilled programmers and should not be avoided based on licensing alone.
- D. While COTS tools may be acceptable, they do not optimally leverage the tester's programming skills compared to language-matched tools.
Question 28
Which of the following CORRECTLY describes how automation SHOULD be applied to confirmation testing?
Show answer and explanation
Correct answer: C. Confirmation tests can be automated and incorporated into an automated regression suite to show whether defects that were previously fixed re-occur.
Confirmation testing (also called re-testing) verifies that previously failing tests now pass after a defect fix. These tests are excellent candidates for automation because they are designed to be run repeatedly, every time a defect is fixed, you want to confirm it stays fixed and doesn't regress. Automating confirmation tests and incorporating them into a regression suite ensures efficient, consistent validation that defects do not re-occur, which is the core purpose of confirmation testing.
Why the other options are wrong
- A. Confirmation tests are actually ideal for automation because they are meant to be run many times to verify that fixes remain stable.
- B. Confirmation tests should be automated regardless of initial pass/fail status; the point is to run them repeatedly as part of regression testing after any future changes.
- D. While confirmation tests are often run manually first to verify a fix, there is no requirement to delay automation until after manual execution, they should be automated promptly to enable continuous regression verification.
Question 29
Which statement about layering in a test automation framework is TRUE?
Show answer and explanation
Correct answer: B. A TAF should have one layer for each different purpose in order to get the benefits of abstraction.
Proper layering in a Test Automation Framework (TAF) follows the principle of abstraction and separation of concerns. Each layer should serve a distinct purpose, such as the UI layer, business logic layer, data access layer, and utility layer, allowing testers to work at appropriate levels of abstraction without worrying about lower-level implementation details. This purposeful layering enables better maintainability, reusability, and reduces coupling between components. Having one layer per purpose is the correct principle; the number of layers naturally emerges from the architecture's needs.
Why the other options are wrong
- A. Fewer layers does not optimize efficiency; rather, proper layering improves efficiency through reusability and reduced maintenance effort.
- C. While minimizing complexity is desirable, the goal is not to minimize layer count but to organize layers by purpose.
- D. Segregating class files is a file organization concern, not the primary purpose of layering in a framework.
Question 30
You have executed an automated test suite for a product that was released into production. Although all the tests passed, there was a major failure in production in an area that was covered well by your automated tests. You have run the automated tests again and one of the tests is now failing and this is directly related to the production defect that was raised. You decide to run the automated test suite again on the same version of the SUT and the test now passes. What SHOULD you do now to verify the validity of the automated tests?
Show answer and explanation
Correct answer: A. Remove the intermittently failing test from the test suite and investigate the reason why the test sometimes passes and sometimes fails.
An intermittently failing test that correlates with a production defect indicates a flaky test that is unreliable for regression detection. The correct action is to remove the unstable test and investigate its root cause to determine whether the issue lies in test design, environmental conditions, or test data. Once understood, the test can be redesigned to be reliable or replaced with a more stable alternative.
Why the other options are wrong
- B. The production defect is already confirmed as actual; the focus should be on the test reliability issue, not validating the production defect.
- C. Continuing to run an intermittently failing test without investigation leaves a false sense of coverage and risks missing the same issue in future releases.
- D. Simply removing the test without investigation provides no insight into why it fails, preventing improvements to the automation framework.
That was 30 of 120.
The full ISTQB CTAL-TAE pack has all 120 questions, each with the answer, the explanation and why the other options are wrong, plus a questions-only copy for timed runs. US$39, paid once, with free monthly updates and a pass-or-your-money-back guarantee.
Not ready yet? Get the first 60 free as one PDF by email. Get the Half Pack →