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

Which of the following statements about contract testing is TRUE?

• A. Contract testing, regardless of the approach chosen (provider-driven or consumer-driven) does not need to rely on the creation of stubs/mocks since it is used to implement integration testing, not unit
  /component testing
• B. The differences between the two approaches to contract testing stem primarily from which side creates the contract: this creation is done by the provider for the provider-driven approach and by the consumer (s) for the consumer-driven approach
• C. Contract testing can be viewed as a specialized form of API testing that can be applied to effectively and efficiently test integration between microservices, but only if they interact with REST APIs
• D. Contract testing can be viewed as a specialized form of API testing that can be applied to effectively and efficiently test integration between systems, but only if they interact synchronously

A TAS that performs automated testing in a single test environment was successfully manually installed and configured from a central repository, with all its components in the correct versions. It was also verified that all TAS components in this environment are capable of providing reliable and repeatable performance. The TAS will be used to run several suites of automated regression test scripts on various SUTs in the test environment. Your current goal is to complete all preliminary verifications to ensure that the TAS works correctly. Which of the following activities would you perform FIRST?

• A. Run a given suite multiple times using TAS to determine whether all regression test scripts always provide the same result
• B. Create scripts to automatically install and configure the TAS in the test environment from the central repository
• C. Check whether the TAS connectivity to all required internal systems, external systems, and interfaces is available
• D. Check whether all regression test scripts in a given suite have expected results

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. The use of feature toggles
• D. Test-driven development