A.  

Outliers in test execution times

B.  

Security vulnerabilities in automated test cases

C.  

Unstable automated test cases

D.  

Maintainability issues in automated test cases

A.  

Manage the infrastructure that hosts the server, including hardware, software updates, and security patches

B.  

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

C.  

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

D.  

Check whether all test scripts that will be executed by the TAS as part of a given test suite have expected results

A.  

First upgrade the OS, then implement the change in the API authentication method, and finally run all the updated test scripts

B.  

Implement one change at a time and run a subset of the updated test scripts after each change, and finally run all the updated test scripts

C.  

First implement the change in the API authentication method, then upgrade the OS, and finally run all the updated test scripts

D.  

Implement one change at a time and run a subset of the updated test scripts after each change

A.  

Create scripts to automatically install and configure the TAS in the test environment from the central repository

B.  

Check whether the TAS connectivity to all required internal systems, external systems, and interfaces is available

C.  

Run a given suite multiple times using TAS to determine whether all regression test scripts always provide the same result

D.  

Check whether all regression test scripts in a given suite have expected results

A.  

Use a Network Time Protocol (NTP) server to ensure that the clocks of the machines running TAS and SUT are synchronized with a common time source

B.  

Log all the messages in memory using a circular buffer and periodically flush the buffer to the corresponding log files associated with the specific execution

C.  

Avoid logging the messages that occur during the specified bursts to minimize any potential performance overhead in test execution

D.  

Log all the messages directly on the corresponding log files associated with the specific execution to ensure the permanent storage of test execution logs

A.  

Release notes/change logs on past changes to the API

B.  

Details about the parameters accepted by each API endpoint

C.  

Authentication mechanisms required to access the API

D.  

Details about the format of the API responses

A.  

Log the stack trace and amount of memory available to the SUT at the start and end of each test in the suite, in the SUT log files

B.  

Split the generated log file into smaller parts, load them into external files that are loaded into the browser in transparent mode when needed

C.  

Log all expected logging data in the final test execution log file, not only for keywords that fail, but also for keywords that execute successfully

D.  

Use appropriate colors to effectively visually highlight different types of information in the test execution log files

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.  

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.  

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

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.  

Test-driven development

B.  

Keyword-driven testing

C.  

Data-driven testing

D.  

Linear scripting

A.  

Autonomy

B.  

Architecture transparency

C.  

Controllability

D.  

Observability

A.  

In Agile software development, automated regression test suites sometimes grow so large that they can become difficult to maintain, and thus, it becomes crucial to invest in test automation at multiple test levels

B.  

In a Waterfall model, automated tests are usually executed only during the last phase of the development lifecycle, but their implementation occurs in the early stages

C.  

In Agile software development, regardless of context (e.g., type of application to be developed, tools available), test automation must be based on the test automation distribution known as the test pyramid model

D.  

Unlike Agile software development, where automated unit tests are written by developers, often in a test-first fashion, in a V-model, automated unit tests are written by testers as part of unit testing

A.  

The test progress report should indicate, for each test in the suite, the timestamps related to the test steps

B.  

The content of the test progress report should not be affected by the stakeholders to whom the report is intended

C.  

The test progress report should indicate the test environment in which the tests were performed

D.  

The test progress report should indicate, for each test in the suite, the start and end timestamps of the test