The relevant Information Management Branch will also have input into Acceptance Testing based upon technical Acceptance Criteria and report to the Project Manager. Unfortunately, the computer professionals will not understand your business as well as you do. Computer personnel will view the system from a technical rather than business-user perspective. Given they had a hand in constructing the system, they may have developed misconceptions of how it should operate. For these reasons it is best for end-users to Acceptance Test their own system.
The Acceptance Testing Kit – Part 1 23 The Key Steps There are key steps in Acceptance Testing that must be considered no matter the size or complexity of the Project. The extent of an Acceptance Test may range from testing a small change to an existing system, to implementing a large new package or custom-built system. Whatever the extent, there are fundamental steps to be followed. It is important the person responsible for Acceptance Testing formalises the testing process and arranges for the necessary personnel and resources to be available. This requires preparation and planning, and quite often training as well. 1. Prepare a Test Plan 2. Review the Test Plan with participants and stakeholders 3. Arrange sign off of the Plan 1. Prepare the tests (Test Cases) 2. Prepare the Test Scripts (or Test Scenarios) 3. Prepare the Test Data 4. Conduct training for the participants 5. Establish the Test Environment 6. Confirm the availability of personnel and resources 1. Run the tests (Test Scripts and Test Cases) 2. Record the results 3. Log problems and monitor their resolution 4. Fix problems and re-test 1. Arrange for formal acceptance of the system 2. Hand over the system, the documentation and test records
The Acceptance Testing Kit – Part 1 24 The Seven Golden Rules If you observe the Seven Golden Rules, you’ll avoid the most common pitfalls of Acceptance Testing. 7 T imeframes for Acceptance Testing must be realistic, planned, and signed- off by management and endorsed by stakeholders. E veryone involved in Acceptance Testing should be relieved of their normal duties to a level that allows them to meet their testing commitments. S uppliers of the system must thoroughly test the system and guarantee it’s stability and quality before handing it over for Acceptance Testing. T rain all Acceptance Testing participants in the use of the system and the testing procedures. I nform management and stakeholders of progress regularly, and keep the Acceptance Test Plan up-to-date. N ever overlook the end-user who has the best knowledge of the business area under test and how to most successfully improve the business processes. G ive the testing staff ready access to technical support personnel who maintain the test environment, including network administrators, database administrators, and software specialists.
The Acceptance Testing Kit – Part 1 25 A Map of Acceptance Testing Documentation Test Data Requirements or acceptance criteria that must be met.
You've reached the end of your free preview.
Want to read all 96 pages?
- Fall '18
- acceptance testing, Acceptance Test Manager