You are working on a web-based application called Book Vault that allows people to upload books and order books. This application must be available on all major browsers.
You have been testing the application manually and management have asked you to consider automating some of the tests.
You have investigated a number of commercial and free tools which can automate tests at a web browser level and one tool in particular meets your requirements and you have implemented a trial version.
You have basic programming skills and the main goal is to automate a few functional tests to see if the tool is compatible with the application and can recognise the objects and controls.
Which scripting technique would be MOST suitable in this scenario in order to meet the objectives?
Which of the following success factors for a test automation project is TRUE?
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?
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?
You have implemented a keyword-driven scripting framework, which uses a test execution tool to run the tests. This has been in use for the past year and all of the teams now use this framework as the standard approach for test execution.
The teams all work on different aspects of the SUT and they have all experienced significant benefits in the use of this scripting framework. However, on closer examination, you have discovered that there are numerous instances where the teams have the same functionality to test but are using different keywords.
One of your objectives for improvement is to create consistency among the teams.
What is the BEST way to handle this situation?
