Selection of Test Automation Approach and Planning of Deployment/Rollout
Which are the objectives of the pilot project?
A) Identify initial target projects
B) Deploy the TAS in the selected projects
C) Assess whether the benefits can be achieved at a reasonable cost
D) Provide training and coaching/mentoring for new users
C) Assess whether the benefits can be achieved at a reasonable cost
Reference page 45
What is a potential technical issue that may arise with the TAS?
a) Staffing issues
b) Cumbersome data tables
c) Difficulty in maintaining the code base
d) Inability to track non-standard objects
b) Cumbersome data tables
Reference page 47
Which of the following is not a type of maintenance?
A) Preventive maintenance
B) Corrective maintenance
C) Perfective maintenance
D) Active maintenance
D) Active maintenance
Reference page 49
The pilot should be treated as a regular development project, this is part of
A)Identify a suitable project
B)Plan the pilot
C)Conduct the pilot
D)Evaluate the pilot
B)Plan the pilot
Reference page 46
What is a risk mitigation strategy for maintenance deployment of the TAS?
a) Test the TAS for new functionality and regressions
b) Create the infrastructure for the TAS
c) Define the infrastructure in which the TAS will run
d) Make sure the test suite gets enough time to be executed entirely
a) Test the TAS for new functionality and regressions
Reference page 48
What is the purpose of maintenance in test automation solutions?
A) To make them more complex
B) To reduce their performance
C) To make them compliant with new laws and regulations
D) To make them less testable
C) To make them compliant with new laws and regulations
Reference page 49
After two years of arguments, you have finally convinced your manager to conduct a pilot with a test automation tool you think will work well in your organization. You now need to select the project to use for the pilot. You have a choice of the following:
Project A – a two year project that is currently in early requirements elicitation. This project is for a new e-commerce web site and is being developed mostly in house. The shopping cart component is being developed by a 3rd party but will be integrated by your developers.
Project B – A safety-critical supply chain product that is 6 months behind schedule and has been deemed in “red” status by upper management.
Project C – An upgrade to an HR timesheet tracking application that will be supported on desktop and mobile devices. This is a 4 month project and is being developed entirely in house.
Project D – The shopping cart component of Project A.
Which of these projects is best suited for a pilot project for the test automation tool?
a) Project A because it is a large project and in the early phases
b) Project B because it provides an opportunity to showcase the capabilities of the tool while helping to pull the project back on schedule.
c) Project C because it is a relatively short project and non-critical but also non-trivial
d) Project D because it is a small part of a larger project and will help to show the tool’s capability to work with third party applications
c) Project C because it is a relatively short project and non-critical but also non-trivial
This is the right size project and the righ level of criticality to be a good pilot project.
You have inherited a TAS that is working well. It uses keyword-driven scripting and was wellarchitected. The automation architect who built the system has now moved on to another company. The TAS is working across several projects and has multiple libraries of keywords, categorized by project. These keyword scripts are maintained by the individual project teams.
Given just this information, what is the most significant risk for the TAS?
a) The keyword driven scripts may become out of date if not maintained
b) The level of abstraction, coupled with the departure of the architect may make the system difficult to maintain
c) New projects may not work as well with the TAS as the current projects
d) Because the keyword scripts are maintained by different teams, there is a likelihood that good coding standards are not being followed
b) The level of abstraction, coupled with the departure of the architect may make the system difficult to maintain
The keyword-driven scripts use a
high level of abstraction and the architect has
created this complex TAS which, although
working well now, may be difficult to maintain
without his knowledge and background.
Your team has been working on creating a strong and maintainable TAS. The TAS is expected to be used for at least five years, so good maintainability is critical.
The team has done the following:
Created an impact analysis process for all proposed changes to the system
Documented the usage for the TAS
Documented the third party dependencies, including contacts within the third party
organization
Verified that the TAS runs in an environment separate from the SUT environment
Given this information, what is a major factor of maintainability that has not been addressed?
a) The TAS must be modular, so key components can be replaced as needed
b) The TAS must be a copy of the gTAA
c) The SUT must reside in the same environment as the TAS
d) The TAS must unite the test scripts with the TAF
a) The TAS must be modular, so key components can be replaced as needed
The TAS must be modular for maintainability
Senior management wants to implement test automation into your organization and has asked you to lead this initiative. The organization has a number of systems of varying criticality, some of which may benefit from automation once a TAA is mature. You have been given direction to start with a pilot.
How do you select a suitable project for the TAS?
a) A high visibility project in order to highlight the success of the pilot
b) A non-critical project in order to mitigate any delays the TAS may cause
c) A project that is simple and easy to automate
d) A new project that is immature and still in development
b) A non-critical project in order to mitigate any delays the TAS may cause
The pilot should have minimal impact upon normal business but should be conducted with a realistic project
You have inherited a TAS that is working well. It uses keyword-driven scripting and was wellarchitected. The automation architect who built the system has now moved on to another company. The TAS is working across several projects and has multiple libraries of keywords, categorized by project. These keyword scripts are maintained by the individual project teams.
What is the best risk mitigation strategy for this TAS?
a) Require all test scripts to be developed in a data-driven form rather than keyword-driven to reduce abstraction
b) Define coding practices to be followed by all users of the TAS
c) Document the TAS architecture and the abstraction approach of the TAS so that future maintenance will be easier to understand
d) Stop allowing the individual project teams to maintain scripts and create a central team for script writing
c) Document the TAS architecture and the abstraction approach of the TAS so that future maintenance will be easier to understand
The biggest risk with this system is
that the TAS may be difficult to understand and
the person who architected it has left.
Documenting it now will make maintenance
easier in the future.
22.- Why is it important to have standard naming conventions for a TAS?
a) A TAS that uses standard names will enable faster execution of the test automation
b) A TAS that uses standard names will be easier for a new person to learn
c) A TAS that uses standard names will support global substitutions when test automation standards change
d) A TAS that uses standard names will allow separation of the test scripts from the TAF
b) A TAS that uses standard names will be easier for a new person to learn
Standard names will be easier for a new person to learn and will make the code easier to understand