Your organisation has successfully implemented a Test Automaton Solution (TAS) for a new project which has since been delivered into production via a number of sprints. A series of maintenance releases are now planned.
Some improvements were made to the Test Automation Architecture (TAA) as a result of feedback from the early sprints. The TAA improvements affected the TA, and the TAS was changed for the final sprint.
The new version of the TAS was generally well received but some performance and usability issues were encountered with the TAS which have yet to be addressed.
The test automation engineers supporting the maintenance releases must decide whether to use the enhanced TAS or the version that was used successfully for previous sprints.
What is the BEST action to take next?
Answer : D
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
Answer : C
You have executed an automated test suite for a product that was released into production. Although all the tests passed, there was a major failure in production in an area that was covered well by your automated tests.
You have run the automated tests again and one of the tests is now failing and this is directly related to the production defect that was raised. You decide to run the automated test suite again on the same version of the SUT and the test now passes.
What SHOULD you do now to verify the validity of the automated tests?
Answer : A
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?
Answer : B
A SUT has an existing automated test suite.
Which of the following statements relating to the introduction of new features in the SUT is TRUE?
Answer : B
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?
Answer : A
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
Answer : A