‘conventional’ project management processes. There needs to be: ► An overall guiding plan; ► Well defined responsibilities and lines of communication; ► A detailed schedule of tasks with dates and assignments; ► Well defined processes and tasks; ► A controlled environment, documentation, and product; ► Processes to capture and record details of progress and to monitor them against the plan; and ► Regular review meetings. What Test Documentation Should We Make? Depending on the scale of the Acceptance Test, for maximum benefit and minimum effort, establishing and maintaining the following records and documentation can be very helpful. The Acceptance Test Strategy is generally only necessary for a large project, whilst all other documentation is needed for both large and small projects, with documentation “scaled down” for the smaller projects. ► An Acceptance Test Strategy - outlining the approach and understandings for Testing activities during the Project. This is best formulated soon after Project inception and can be included in the Project Execution Plan (should one exist). A template can be found on the DPAC Project Management web site; ► The Acceptance Test Plan - outlining the Test approach, objectives, activities, responsibilities, and schedule. This includes: • Test Procedures - documenting the processes to be followed during Acceptance Testing. Procedures; • Authorisation requirements for commencement, suspension, and cancellation; • The conduct of Tests and recording of results; • The recording and resolution of Test problems; • Signing-off and formal acceptance;
The Acceptance Testing Kit – Part 2 16 Even though Acceptance Criteria are often specified in the relevant contract or agreement with the system supplier, they should still be included in the Acceptance Test Plan. • Authorisation requirements for changes to the Test system and/or environment; and • The release of a new version of the system; ► Test Cases - showing Tests to be performed, usually measured against business requirements (with any specific data or conditions), and the expected outcomes. There may be many Test Cases for a single business requirement. These include recording the outcome of each Test Case and/or Script as Test Results; ► Test Scripts - documenting individual testing processes as a series of steps, many of which will be series’ of interrelated Test Cases and encompass an individual business requirement/process; and ► Problem Review Sheets and Problem Review Register - documenting problems encountered and indexing the status of each problem. In addition, maintain an: ► Acceptance Test Log - recording significant events and changes to the test environment and test data. Templates for these documents form part of this Kit. Samples and templates of these documents form part of this Kit.
You've reached the end of your free preview.
Want to read all 96 pages?
- Fall '18
- acceptance testing, Acceptance Test Manager