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)?

Which of the following statements about the reuse of TAS artefacts is TRUE?

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 defect in a SUT has been resolved and validated by an automated defect re-test in the current release of the software. This retest has now been added to the automated regression test suite.

Which statement BEST describes a reason why this defect could re-occur in future releases?

Designing the System Under Test (SUT) for testability is important for a good test automation approach and can also benefit manual test execution.

Which of the following is NOT a consideration when designing for testability?

What is NOT a factor in considering when you are asked to ensure an effective transition from manual to automated tests?

You are using a gTAA to create a TAS for a project. The TAS is aimed specifically at automating a suit of existing manual test cases for standalone desktop applications. All the interfaces between the TAS and SUT will be from the CUI of the application.

Which of the following layers of the gTAA should you focus on for the TAS?

You are evaluating the best approach to implement automated tests at the UI level for a web app. Specifically, your goal is to allow test analysts to write automated tests in tabular format, within files that encapsulate logical test steps related to how a user interacts with the web UI, along with the corresponding test data. These steps must be expressed using natural language words that represent the actions performed by the user on the web UI. These files will then be interpreted and executed by a test execution tool. Which of the following approaches to test automation is BEST suited to achieve your goal?

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?

(Which of the following statements about how test automation is applied across different software development lifecycle models is TRUE?)

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 façade 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 web application was released into production one year ago, it has regular release which follow a V-model lifecycle and testing is well-established and fully integration into the development lifecycle. You have been asked to implement a TAS for the regression test suite. The regression tests have been developed via the GUI and are expected to be run at least four times a month, for each planned release, for the whole operation solution life of the system (six years). Each screen of the GUI uses several third-party controls which are not compatible with the existing automation solutions. The environment for the automation will be stable, fully controllable and separated from other environments (development, staging, production).

What could be the MOST problematic for this TAS?

A release candidate of a SUT, after being fully integrated with all other necessary systems, has successfully passed all required functional tests (90% were automated tests and 10% were manual tests). Now, it is necessary to perform reliability tests aimed at evaluating whether, under certain conditions, that release will be able to guarantee an MTBF (Mean Time Between Failures) in the production environment higher than a certain threshold (expressed in CPU time). Which of the following test environments is BEST suited to perform these reliability tests?

In a first possible implementation, the automated test scripts within a suite locate and interact with elements of a web UI indirectly through the browsers using browser-specific drivers and APIs, provided by an automated test tool used as part of the TAS. In an alternative implementation, these test scripts locate and interact with elements of the same web UI directly at the HTML level by accessing the DOM (Document Object Model) and internal JavaScript code. The first possible implementation:

Consider a SUT that small run on multiple platform during the execution of automated test runs. In each test run an automated test suite needs to be executed, with the same version of the TAF, against the same version of the SUT of each platform. Each platform shall have its own dedicated test environment. Your goal is to implement a process as automated as possible ( i.e with minimal manual intervention) that allows implementing a consistent setup of the TAS across the multiple test environments.

Which two of the following aspects are MOST relevant for achieving your goal in this scenario?

The configuration of the TAS uses automated installation scripts

The TAF saves the logs needed to debug errors in XML format

C) Features of the TAF not used by the automated tests have been tested

D) All the automated test cases contain the expected results

E) The TAS components are under configuration management

Consider the following layers of the gTAA structure:

a. Test generation layer

b. Test definition layer

c. Test execution layer

d. Test execution layer

Consider the following capabilities associated with these layers.

Acquire all the necessary resources before each test and release all after run, in order to avoid interdependences between test

Allow the automated test scripts on an abstract level to interact with components, configurations and interfaces of the SUT.

Design test directives that allow configuring the algorithms used to automatically produce the test cases a given model of the SUT.

Allow the definition and implementation of test cases and data by means of templates and/or guidelines.

Which of the following BEST matches each layer with the appropriate capability?

Which of the following is the BEST example of how static analysis tools can help improve the test automation code quality in terms of security?

Which of the following attributes should NOT be included in a test execution report associated with a suite of automated tests?

Which of the following statements about contract testing is TRUE?

You are using a gTAA to create a TAS for a project. The TAS is aimed at automatically and executing test cases based on a use-case

Modeling approaching that uses UML as a modeling language. All the interaction between TAS and SUT will only be at the API and GUI level.

Which of the following components of the gTAA would you EXCLUDE from the TAS?

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?

(Which of the following answers describes the LEAST relevant concern in selecting suitable test automation tools for a test automation project?)

Which of the following recommendations can help improve the maintainability of test automation code?

Consider a TAS that uses a keyword-driven framework. The SUT is a web application and there is a large set of keywords available for writing the automated tests that relate to highly specific user actions linked directly to the GUI of the SUT. The automated test written with the keywords are statically analyzed by a custom tool which highlight’s repeated instances of identical sequence of keywords. The waiting mechanism implemented by the TAS for a webpage load is based on a synchronous sampling within a given timeout. The TAS allows checking a webpage load every seconds until a timeout value