Which of the following success factors for a test automation project is TRUE?

A. Automated tests must be designed to capture only the data that is strictly needed for comparing expected and actual results

B. The test cases to be automated first must always be selected based on the number of times a test will need to be run

C. The test cases to be automated must have a high dependency on particular data values

D. Automated tests that fail due to changes in the requirements of the SUT should be promptly fixed rather than disabled from the test suite

Consider a TAS deployed into production. The SUT is a web application and the test suite consists of a set of automated regression tests developed via GUI. A keyword-driven framework has been adopted for automating the regression tests. The tests are based on identification at low-levels of the web page components (e.g class indexes, tab sequence indexes and coordinates) in the next planned release the SUT will be subject to significant corrective maintenance (bug-fixes) and evolution (new features) Maintenance costs to update the test scripts should be as low as possible and the scripts must be highly reusable. Which of the following statements is most likely to be TRUE?

A. The keyword-driven framework is not suitable, it would be better to adopt a structured-scripting approach

B. False positive errors are likely to occur when running the automated tests on the new releases without modifying the test

C. The total execution time of the automated regression test suite will decrease for each planned release.

D. The keyword-driven framework introduces a level abstraction that is too high and makes it difficult what really happens

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

A. Summary of the test execution results

B. System/Application under test and its version

C. Defect clusters identified during test execution

D. Environment in which the tests have been executed

Consider a TAS that exclusively uses the APIs of a SUT. To make this work, significant changes have been required to the SUT by adding a set of dedicated test interfaces to the APIs. All the automated tests will use these test interfaces when interacting with the SUT. Assume that you are currently verifying the correctness of the automated test environment and test tool setup. Which of the following would you expect to be the MOST specific risk associated with this scenario?

A. The connectivity from the TAS to the dedicated test interfaces will not work

B. The process of configuring the TAS will be error-phone due to manual intervention

C. The automated test cases will not contain the expected result

D. False alarms, that are unlikely to occur in the real world, will be observed during testing

Consider A TAS for testing a desktop application via its GUI. All the test cases of the automated test suite contain the same identical sequences of steps at the beginning (to create the necessary objects when doing a preliminary configuration of the test environment and at the end (to remove everything created – specifically for the test itself during the preliminary configuration of the test environment). All automated test cases use the same set of assertion functions from a shared library, for verifying the values in the GUI fields ( e.g text boxes).

What is the BEST recommendation for improving the TAS?

A. Implementing keywords with higher level of granularity

B. Improving the architecture of the application in order to improve its testability

C. Adopting a set of standard verification methods for use by all automated tests

D. Implementing standard setup and teardown functions at test case level