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?

• A. Interface segregation principle
• B. Liskov substitution principle
• C. Dependency inversion principle
• D. Open-closed principle

You have agreed with your organization's managers to conduct a pilot project to introduce test automation.
Managers' expectations about the benefits of automation are too optimistic. Which of the following is LEAST relevant when deciding the scope of the pilot project's objectives?

• A. Evaluate the suitability of different test automation tools based on the technology stack used by the applications for which the automated tests will be developed
• B. Evaluate the potential cost savings and benefits (e.g., faster test execution, better test coverage) of using automated testing versus manual testing
• C. Evaluate the knowledge and skills of people who will be involved in automating test cases for applicable test automation frameworks and technologies
• D. Evaluate the performance of an organization's network infrastructure in terms of factors such as availability, bandwidth, latency, packet loss, and jitter

A TAS is used to run on a test environment a suite of automated regression tests, written at the UI level, on different releases of a web app: all executions complete successfully, always providing correct results (i.e., producing neither false positives nor false negatives). The tests, all independent of each other, consist of executable test scripts based on the flow model pattern which has been implemented in a three-layer TAF (test scripts, business logic, core libraries) by expanding the page object model via the facade pattern. Currently the suite takes too long to run, and the test scripts are considered too long in terms of LOC (Lines of Code).
Which of the following recommendations would you provide for improving the TAS (assuming it is possible to perform all of them)?

• A. Implement a mechanism to automatically reboot the entire web app in the event of a crash
• B. Modify the TAF so that test scripts are based on the page object model, rather than the flow model pattern
• C. Split the suite into sub-suites and run each of them concurrently on different test environments
• D. Modify the architecture of the SUT to improve its testability and, if necessary, the TAA accordingly

Consider a TAS implemented to perform automated testing on native mobile apps at the UI level, where the TAF implements a client-server architecture. The client runs on-premise and allows creation of automated test scripts using TAF libraries to recognize and interact with the app's UI objects. The server runs in the cloud as part of a PaaS service, receiving commands from the client, translating them into actions for the mobile device, and sending the results to the client. The cloud platform hosts several mobile devices dedicated for use by this TAS. The device on which to run test scripts/test suites is specified at run time. You are currently verifying whether the test automation environment and all other TAS/TAF components work correctly. Which of the following activities would you perform to achieve your goal?

• A. Check whether all test scripts that will be executed by the TAS as part of a given test suite have expected results
• B. Check whether the TAF libraries that the test scripts will use to recognize and interact with the app's UI objects (widgets) function as expected
• C. Check whether the references to the device on which the given test scripts/test suites will be executed are correctly hard-coded within these test scripts/test suites
• D. Manage the infrastructure that hosts the server, including hardware, software updates, and security patches

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