Software testers can have one of three roles in acceptance testing.
Role - 1) No involvement at all:
In that instance the user accepts full responsibility for developing and executing the acceptance test plan.
Role - 2) Act as an advisor:
The user will develop and execute the test plan, but rely on software testers to compensate for a lack of competency on the part of the users, or to provide a quality control role.
Role - 3) Be an active participant in software testing:
This role can include any or the entire acceptance testing activities. The role of the software tester cannot include defining the acceptance criteria, or making the decision as to whether or not the software can be placed into operation. If software testers are active participants in acceptance testing, then they may conduct any part of acceptance testing up to the point where the results of acceptance testing are documented.
A role that software testers should accept is developing the acceptance test process. This means that they will develop a process for defining acceptance criteria, develop a process for building an acceptance test plan, develop a process to execute the acceptance test plan, and develop a process for recording and presenting the results of acceptance testing.
Tags: User Acceptance Testing, Software Testing, Quality Assurance
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment