You have been asked to determine a TAS for a new release of a SUT,test should be automated wherever. The new release will consist of 5 new interfaces and an amendment to 3 existing interfaces. The new and amended interface will be deliver incrementally in 3 sprints, each lasting 2 weeks.
What would be the BEST Test Automation Solution (TAS) design in this scenario?
Consider the followingexample of TAS metrics.
Time to execute automated tests
Speed and efficiency of TAS components
Which of the following statements is TRUE?
Which of the following success factors for a test automation project is TRUE?
You identified a suitable project to pilot an automation tool and planned and conduced a pilot. The pilot has been successful and tool Is being deployed within your organization, with a plan to increase tool use by the one project at a time. During this rollout some test processes will be changed slightly to gain additional benefits from using the tool.
Inthe pilot project, a small set of manual tests were automated for the first time. You are currently monitoring the test automation efficiency and this reveals that the automation regime for the tests is not yet mature.
Which of the following statements isTRUE?
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 writingthe 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
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?
The GUI of a Customer Relationship Management (CRM) application has been delivered through internet Explorer with proprietary Active X and Java controls. This implementation enables rich client capabilities, but specific commercial automation tools are necessary to automate test cases at GUI of functional test cases. This is to demonstrate whether a small set of the commercial are able to properly recognize actions takenby a tester when interacting with GUI of the CRM application.
Which of the following scripting techniques would be MOST suitable in this scenario?
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?
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?
Consider A TAS for testing adesktop 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?
