An API's response to a request made to the corresponding endpoint should return some specific data about a payment transaction in JSON format. In particular, your goal is to write the test automation code, keeping it as short as possible, aimed at determining whether that response includes certain properties (transaction_id, amount, status, timestamp) with the data types and formats expected. Assuming that the TAF provides all the necessary support to validate the specified API response, how would you BEST achieve your goal?

• A. Write custom code that parses the actual response data and checks whether the extracted properties, data types, and formats are as expected
• B. Use an artificial intelligence algorithm based on machine learning and image recognition to implement a self-healing capability
• C. Write a single assertion for each property to check whether the data types and formats for that property are as expected in the actual response
• D. Specify the schema for the expected response data (properties, data types, and formats) and validate the actual response data against this schema

Which factor will support maintainability of test automation solutions?

• A. Test-driven development
• B. Hardcoded parameter values
• C. Common naming conventions
• D. Keyword-driven testing

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 two months.
Until now the company has not automated test execution, but the Agile pilot identified this as a critical success factor. You are an experienced TAE and have been recruited to implement test automation, and you are now considering what the TAS for this should look like.
Which option contains the THREE MOST important considerations in determining the nature of the TAS that will be needed for this project?
i) The tool(s) chosen for functional test automation should support scripting techniques that will be compatible with a performance test tool.
ii) The tool(s) chosen for functional test automation should support scripting techniques that will be useful for usability testing.
iii) The TAS should support testing at the component integration, system, system integration and acceptance levels.
iv) The TAS should support testing at the component, component integration, system and acceptance levels.
v) The TAS should support the handling of the large quantities of data that will be needed to test the forecast reports.

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

A SUT (SUT1) is a client-server system based on a thin client. The client is primarily a display and input interface, while the server provides almost all the resources and functionality of the system. Another SUT (SUT2) is a client-server system based on a fat client that relies little on the server and provides most of the resources and functionality of the system. A given TAS is used to implement automated tests on both SUT1 and SUT2. The main objective of the TAS is to cover as many system functionalities as possible through automated tests executed as fast as possible. Which of the following statements about the automation solution is BEST in this scenario?

• A. The TAS should support mainly server-side automation for both SUT1 and SUT2
• B. The TAS should support mainly server-side automation for SUT1 and client-side automation for SUT2
• C. The TAS should support mainly client-side automation for both SUT1 and SUT2
• D. The TAS should support mainly client-side automation for SUT1 and server-side automation for SUT2

Which of the following statements about contract testing is TRUE?

• A. 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
• B. 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
• C. 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
• D. 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