Which of the following practices can be used to specify the active (i.e., actually available) features for each release of the SUT and determine the corresponding automated tests that must be executed for a given release?

• A. The use of feature files
• B. Feature-driven development
• C. Test-driven development
• D. The use of feature toggles

A CI/CD pipeline consists of two phases: build and deployment. The build phase, among other activities, runs automated test cases at the following test levels: Component Testing (CT) and Component Integration Testing (CIT). If the build phase is successful, the deployment phase is started. The deployment phase first provisions the test environment infrastructure needed to deploy the SUT, then deploys the SUT to this environment, and finally triggers another separate pipeline that runs automated test cases at the following test levels: System Testing (ST) and Acceptance Testing (AT). Which of the following statements is TRUE?

• A. Automated test cases for CT-CIT can act as quality gates, while automated test cases for ST-AT cannot act as quality gates
• B. Automated test cases for CT-CIT cannot act as quality gates, while automated test cases for ST-AT can act as quality gates
• C. Neither automated test cases for CT-CIT nor automated test cases for ST-AT can act as quality gates
• D. Both automated test cases for CT-CIT and ST-AT can act as quality gates

A new TAS allows the implementation of automated data-driven test scripts. All the tasks planned for the initial deployment of this TAS, aimed at installing and configuring the TAS components and provisioning the infrastructure, will be performed manually by a dedicated, specialized team. This TAS is expected to be deployed in the future in other similar environments. As a TAE, you see a risk that the correct and reproducible deployment of the TAS cannot be guaranteed. Which of the following options is BEST suited for mitigating this risk?

• A. Review data-driven test scripts to better organize test libraries by adding test functions containing identical sequences of actions commonly implemented in a relevant number of scripts
• B. Nothing needs to be done, because the team that will manually perform the specified tasks, as they are specialized, will not make mistakes and will therefore be able to ensure a correct and reproducible deployment
• C. Try to automate most of the tasks related to the installation and configuration of the TAS components and those related to the provisioning of the infrastructure
• D. Partition the data tables containing test data used by data-driven test scripts into smaller data tables, using an appropriate logical criterion, to make them more manageable

(Which of the following aspects of "design for testability" is MOST directly associated with the need to define precisely which interfaces are available in the SUT for test automation at different test levels?)

• A. Architecture transparency
• B. Observability
• C. Controllability
• D. Autonomy

Automated tests at the UI level for a web app adopt an asynchronous waiting mechanism that allows them to synchronize test steps with the app, so that they are executed correctly and at the right time, only when the app is ready and has processed the previous step: this is done when there are no timeouts or pending asynchronous requests. In this way, the tests automatically synchronize with the app's web pages. The same initialization tasks to set test preconditions are implemented as test steps for all tests. Regarding the pre- processing (Setup) features defined at the test suite level, the TAS provides both a Suite Setup (which runs exactly once when the suite starts) and a Test Setup (which runs at the start of each test case in the suite).
Which of the following recommendations would you provide for improving the TAS (assuming it is possible to perform all of them)?

• A. Implement the initialization tasks aimed at setting the preconditions of the tests within the Suite Setup feature at the test suite level
• B. Adopt a manual synchronization with the app's web pages using hard-coded waits instead of the current automatic synchronization
• C. Implement the initialization tasks aimed at setting the preconditions of the tests within the Test Setup feature at the test suite level
• D. Adopt a manual synchronization with the app's web pages using dynamic waits via polling instead of the current automatic synchronization