You are using a gTAA to create a TAS for a project. The TAS is aimed at automatically and executing test cases based on a use-case Modeling approaching that uses UML as a modeling language. All the interaction between TAS and SUT will only be at the API and GUI level. Which of the following components of the gTAA would you EXCLUDE from the TAS?
A. The test reporting component of the test execution layer.
B. The Test execution component of the test generation layer
C. The test execution (test engine of the test execution layer
D. The Command Line Interface (CLI) component of the test adaptation layer
What is NOT a factor in considering when you are asked to ensure an effective transition from manual to automated tests?
A. Complexity to automate the manual test cases
B. Correctness of test data and test cases
C. The look and feel of the SUT
D. The controllability of the SUT
Your functional regression test automation suite ran successfully for the first two sprints and no failures were encountered during the runs. The automation suite records the status of each test case as either 'pass' or 'fail' and has excellent
recovery capability built in.
For the third sprint, the TAS log reported several test cases with a status of 'fail'. You investigated each test case and found that most failures were due to a defect in one of the keyword scripts, rather than in the SUT. For those where the
failure was in the SUT, defectreports were raised but several were returned by the developers asking for more information to enable them to reproduce the problem.
Which additional log items SHOULD you add to the TAS that would BEST improve failure analysis and defect reporting for future sprints?
a) Dynamic measurement information about the SUT.
b) A status of TAS error
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?
A. Move to a model-based approach to scripting where the models include the keywords.
B. Do nothing, each team are working in isolation and they are all experiencing significant benefits in the way they are currently working.
C. Provide each team with a set of guidelines and naming conventions for keywords.
D. Create a central library of keywords and associated definitions for each team to use.
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
If you are tracking the frequency that a test automation code reports a defect that is not really a defect, what metric are you gathering?
A. Tool scripting metrics
B. Automation code defect density
C. Trend metrics
D. The number of false-fail results
You have investigated a new tool which enables the modelling of the SUT and can then generate test cases either manually or automatically. You have convinced your managers that the best way forward is to conduct a pilot project for this
tool. You need to select a project to use for the pilot. You have the choice of the following projects:
Project A: A two-year project that is critical to the business and is currently in the requirement phase. This project is for a new e-commerce web site and is mostly being developed "in-house" although the payment system is being developed
and delivered by a 3rd party provider.
Project B: A safety critical application for software to drive and park cars.
Project C: An upgrade to an important HR timesheet tracking application that will be available on a desktop and mobile application. This is a 1-month project developed in- house.
Project D The payment system from project A.
Which project would be BEST for the pilot?
A. Project A because it is a large project and has high visibility and is in the requirement phase.
B. Project B because it is a safety critical system and has high visibility.
C. Project C because it is a short, low priority project but is important.
D. Project D because it is a small part of a larger project and will help show the tool's capabilities.
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
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.
In the 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 is TRUE?
A. The approach used for deployed this tool is aligned to the standard success factor for deployment
B. The pilot project should have been critical so that maximum benefits were delivered
C. The target defined for the project was inappropriate, because the automation regime for the automated tests at the end of the pilot is not yet mature.
D. The test process should be radically changed to gain additional benefits from using the tool.
A project consists of distributed teams working in a 24-hour environment, where activities happen at all hours of the day. This project adopts a CI (Continuous Integration) process when developer check-in code and consists of automated activities that include generating a build and deploying it to a test environment. Automated integration tests are run multiple times a day. The project have asked for a report containing the automation test results for every build, which must be available 24/7 to the project team.
Which of the following would be the BEST way to automatically provides this report?
A. Store the execution results of the integration tests for the last build to a database (without overwriting the results from the previous builds), use this database to automatically update a dashboard containing the build history and test results accessible to the project team.
B. Store the execution result of the integration tests for the last build to a database (overwriting the results from the previous build), automatically create a test execution report for this build send It via e-mail to the project team
C. Store the execution results of the integration tests for the last build to a database (without overwriting the results from the previous builds). Automatically create a test execution report for this build and send it via e-mail to the project team
D. Store the code coverage results of the integration tests for the last build to a database (without overwriting the results from the previous builds). And automatically create a chart showing the trend in code coverage and send via email to the project team.
