This guide in BETA1 form is a document that will help with both the understanding and execution of acceptance testing. It provides useful role definitions, process models and decision making guidance in a form that is relatively easy to digest compared to other works I’ve seen on the same subject. At 4MB it is a straightforward PDF download (after you agree to some license terms) that encourages feedback on the work as a community project.
The community site including download is here.
I get a lot of feedback on acceptance testing during our Team System User group sessions. Essentially this role in Visual Studio Team system is the realm of both the Test edition and Team explorer – I’ve shown this a number of times using the v-model diagram *1 which I often trot out when presenting on Team system.
The key thing about acceptance testing is that it really is the final step in determining if requirements have been met and so is critical for detecting faults in both the requirements and system development processes – in other words;
Acceptance testing = Verification of results + Continuous Improvement into both requirements and software build processes;
The guide helps identify who would be interested in this project;
You are involved in deciding whether to accept the software as it is being built. This is the
· You are involved in collecting data that the person making the acceptance decision requires to
make that decision. This is acceptance testing.
· You are involved in deciding whether the product is ready to be seen by the people involved in
the acceptance decision or acceptance testing. This is the readiness decision.
· You are involved in collecting data that the person making the readiness decision requires to
make that decision. This is readiness assessment.
· You are involved in defining the expectations against which the readiness assessment or
acceptance testing activities will be conducted. This is a combination of requirements gathering
and test design.
· You are involved in managing any of the preceding activities.
Well worth a download and a read – comparable publications I’ve seen are up around the $50 NZ Mark and lets face it being electronic its friendlier on the environment J
*1 the V-Model with Team system roles identified