Similarly, the complexity of providing Test Data will increase and its preparation and maintenance will need to be managed. There is likely to a larger group of testers and the range of skills, knowledge, and capability will vary. Preparation of a Skills Transfer and Training Plan is needed to detail delivery and management of training needs. For the Acceptance Testing to be (contractually) valid, the Test environment needs to mirror the final operating environment, as defined in the contract. The Acceptance Test Manager will need to oversee this step and the system suppliers may request an audit of the Test environment. The degree of coordination and planning will be higher. There may be a wide range of resources and personnel to be confirmed. Execution and Control Its important to use the Register of Problem Reviews and plan several runs of Testing, in particular, regression testing. Closure An allowance to accept the system subject to subsequent resolution of documented outstanding (minor) problems should be made. If this is the case, the Problem Review Register should be part of the Acceptance Document. The records for Acceptance Testing of a large system can be quite extensive. It’s important that these are retained safely.
The Acceptance Testing Kit – Part 2 36 Acceptance Testing a Small System A small project is defined as one where the external cost does not exceed $50,000. With a smaller project or system, the overall complexity of Acceptance Testing is reduced. There are fewer people involved, there are fewer types of data and the number of tests and problems is lower. Nevertheless, the basic steps listed still need to be executed. Planning ► Prepare a Test Plan ► Review the Test Plan ► Arrange sign off Preparing Tests, Test Data, and Training ► Prepare the Test Cases ► Prepare the Test Scripts ► Prepare the Test Data • Conduct training • Set up test environment • Confirm people and resources Execution and Control ► Run Test Scripts and Test Cases ► Record the results ► Log and manage problems ► Fix problems and re-test The relatively small number of problems from testing a small system should mean a Problem Review Register is not required. Closure ► Formal acceptance ► Hand over the system
The Acceptance Testing Kit – Part 2 37 System Enhancements and Maintenance Usually changes to an existing production system are grouped together into a ‘Release’. The source of these changes may be requested functionality enhancements and/or resolution of reported problems. Planning Existing DIER applications should already have processes established for system upgrades, maintenance, and enhancements. It may not be necessary to establish a formal Acceptance Test Plan, strategy, and procedures. However there is a minimum set of details that should be defined in order for the Acceptance Testing process to work successfully with established systems.
You've reached the end of your free preview.
Want to read all 96 pages?
- Fall '18
- acceptance testing, Acceptance Test Manager