CT-TAEPreview

A major component of your organisation's Test Automaton Solution (TAS) is a popular open-source third-party capture-replay tool for automated functional testing.
Which two of the following must the Test Automation Engineer (TAE) ensure happens for this TAS? a) The third party tool is placed under configuration management control. b) The annual support and maintenance costs are agreed with the tool's vendor. c) It is Important to obtain information about updates and new versions of the tool so that the third party tool is kept up to date. d) Ensure that the TAS test scripts are integrated into the tool's framework. e) Ensure that no changes are made to the tool, because modifications are not allowed for third party products.

If model-based testing has been selected for the overall test automation approach for a project, how does that influence the layers of the TAA?

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, defect reports 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’, in additional to pass' and 'fail', for each test case. c) Use of a colour coding scheme so that 'pass’ is in red and fail' is in green. d) A counter to determine how many times each test case has been executed. e) System configuration information including software/firmware and operating system versions. f) A copy of the source code for all Keyword scripts executed.

Your TAS has been running successfully on a Windows/GUI based SUT for some years. The SUT has undergone minimal change over the years to maintain business as usual, deploying six-monthly releases for minor enhancements and bug fixes using a waterfall lifecycle.
The TAS has not changed at all during this period. The current project for the SUT will be using the Scrum methodology to deliver a more modern, competitive, user interface. It is in the release planning stage with an agreed release backlog and set of sprints outlined.
The move from lengthy waterfall releases to shorter sprints has led you to conduct a review of the current TAS to make sure it is robust and fully optimised for the timescale challenges of the new project.
What two steps would be BEST to undertake during the review?
a) Ensure that new automation code is using the same naming conventions as existing code. b) Perform a full regression run in Sprint 1 to identify what improvements could be made to the TAS for future sprints. c) Ensure that the TAS is using the latest libraries for the operating system. d) Review the functions that act upon the controls for the GUI for possible consolidation. e) Involve the test team to see what ease-of-use improvements they would like to see made to the TAS.

You are working on a government system called “Making Tax Digital" or MTD for short. This system is being implemented to stop manual human input error and also to reduce fraudulent behaviour from companies when submitting their tax and VAT returns.
The key concept is that registered companies will need to use government recommended 3rd party software for their accounts and book keeping. These 3rd party applications will have a direct interface into the government's main system for transactions and submissions.
You have been using a test execution tool successfully on the project so far. and have implemented a basic “capture/replay” approach to scripting.
The management have been encouraged with the automation so far, but want the following objectives to be met:
• Test cases added easily
• Reduction in the amount of scripts and script duplication
• Reduction in maintenance costs
Which scripting technique would be MOST suitable in this scenario in order to meet the objectives?

The Test Automation Manager has asked you to provide a solution for collecting metrics from the TAS that measures code coverage every time the automated regression test pack is run. The metrics must be trend based to ensure that the scope of the regression test pack continues to reflect enhancements made to the SUT - coverage must not drop and should ideally increase. The solution must be as automated as possible to avoid unnecessary manual overheads and errors.
Which of the following approaches would BEST meet these requirements?

Which of the following is considered a disadvantage of test automation?

New features have been added for the current release of a SUT.
Which action would NOT be appropriate for the TAE to perform when evaluating the impact on the TAS?

You are implementing test automation for a project that has a business critical application A test execution tool is being used to run automated regression tests. The results from the test execution tool are very important and need to be 100% accurate.
You want to merge the test automation results with the test management system that also records the manual test results so that managers can make informed decisions about the progress quickly.
Which layer of the gTAA will be used to ensure the proper reporting occurs and the interfaces to the test management system are handled?

What is the PRIMARY advantage of using abstraction in the TAA?

Which of the following describes how a test execution report is likely to be used?

As the TAE, you are working with the organisation's Test Manager to decide which external metrics and which internal metrics should be gathered for the new TAS.
Which of the following represents the BEST internal metric that would help measure the quality of the TAS and the number of problems associated with the TAS?

You are evaluating several test modelling tools and are wanting to automatically generate test cases within the tool where many different combinations of input data are created.
You are then wanting to export the test cases into a csv file which can then be read by a functional test execution tool using a data-driven or keyword-driven scripting method.
You have investigated several tools and there is only one tool that provides all the necessary features defined by your team with the exception of the export facility. It does not provide an export into either .xls or .csv formats.
What would be the BEST next step regarding the selection of this tool?

You are testing a major enhancement to an air traffic control user interface. You have use of a sophisticated pre-production test environment, created specifically for large scale automated regression, performance and security testing. The window for regression testing is limited and must successfully conclude, with no major regressions remaining, before the non-functional testing starts.
You have been using the same version of the TAS for the last few releases, each time completing the automated regression test suite in a single overnight run. However, due to the latest enhancements for the SUT, you believe there is a risk that the test suite may no longer complete overnight and therefore delay performance and security testing.
Which option would be the BEST and MOST cost-efficient approach to mitigate this risk?

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?

When if the BEST time for automation to consider legal and/or standard requirements for a SUT?

When the SUT provides insight into the behaviour of the system, providing the users the with the status of the various actions performed so that they can check that expected behaviour equals actual behaviour, what is this called?

You are a TAE working for a software house which provides quarterly releases of its software to its customers. There are many different versions of the SUT that need to be tested simultaneously by different tests teams.
Your TAS is complex and you need to ensure it remains consistent across the different SUT environments. What is the BEST and MOST efficient way to ensure each of the test teams use the same version of the TAS to test the different versions of the SUT?

You are implementing test automation for a project and you want to be able to generate test cases automatically using a series of test design tools which use a variety of test design techniques such as decision tables, pairwise testing and boundary value analysis.
You also want to generate test data automatically which can then be used by the tests.
Initially these tests will be run manually to verify their correctness and ultimately you want to include them in the test execution tool so that they can run unattended.
Which layer of the gTAA will be used to support the specification of the test cases and preparation of the test data?

Which of the following is an important success factor for any significant automation project?

In order to achieve re-use of a TAS, where SHOULD the design for reuse occur?

What are the four horizontal layers of the gTAA?

What represents good practice when automating a manual regression test suite?

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?