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?

• A. FATAL
• B. WARN
• C. DEBUG
• D. INFO

Your company is about to start a project to replace an old sales and merchandising system with a new version that will be based on modern platforms. The main requirements for the system are:
1. Loading sales data, sent electronically from the stores each evening, into a central database.
2. Producing sales reports for the merchandisers, whose job is to manage stock levels in stores.
3. Producing forecast reports, used to predict future demand for each product, based on a combination of sales history and forecasting parameters. The parameters will be entered by the merchandisers into a browser-based front end and the reports will be produced overnight. The users will be able to retrieve the reports, on screen or in print, via an interactive feature.
Requirements 1 and 2 were already met by the old system and will be rewritten in the new system with some minor functional changes. The sales data will, as before, be loaded in an overnight batch run. There have been problems with the old system at peak periods when this run has taken longer than scheduled, so that dependent jobs could not finish before the start of the next working day. The Data Centre manager requires that the new system's overnight batch runs take 10% less time than the old one, including the new reports, to allow time for all jobs to complete.
Requirement 3 is new. The functionality provided by the UI will be simple and the Sales & Merchandising manager requires that it be easy to use.
The data for testing the reports will be extracted from the old system in production and will be anonymized before use.
The system will be developed using an Agile lifecycle with iterations of fixed length. This will be the first full deployment of this methodology, which has just completed a successful pilot. It is a relatively simple development and is expected to be completed in three releases, each taking approximately 2 months.
You are an experienced TAE and have been recruited to implement test automation on this project and have started to evaluate candidate tools to automate functional and some non-functional testing. It is already clear that no single tool will meet all requirements, and that the developers' existing Integrated Development Environment will meet the automation needs of their testing. The TAS will need to support CI/CD.
When reviewing your tool comparison table, what two tool capabilities will be MOST beneficial for this project?
i) The ability to support multiple and configurable test environments.
ii) The ability to manage test data in a way that supports version control of the data sets.
iii) The ability to be compatible with other tools that are likely to be used on the project.
iv) The ability to expand the overall test architecture and to be scalable and modifiable.
v) The ability for non-technical users to enter requests for customizable reports.

• A. ii and iii
• B. i and v
• C. i and iv
• D. iii and iv

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 the TAF libraries that the test scripts will use to recognize and interact with the app's UI objects (widgets) function as expected
• B. Manage the infrastructure that hosts the server, including hardware, software updates, and security patches
• C. Check whether all test scripts that will be executed by the TAS as part of a given test suite have expected results
• D. 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

Which option correctly pairs test automation design principles and patterns with their characteristics?
1. Hides implementation details to expose only what the testers need to create in their test cases.
2. Creates a class file so that updates to locators need to be made in only one place.
3. Includes the idea that components should be freely substitutable with no adverse impact.
4. Introduces an additional facade which stores user actions that interact with page objects.

• A. Flow model
• B. Facade pattern
• C. SOLID
• D. Page object model