The product has to be finally used by the user. So he is the most important person as he has highest interest than any one else in the project. From the user we need the following data as shown in the below figure:-
- The first important thing is the Acceptance test plan from the end user. Acceptance test defines the entire test which the product has to pass so that it can go in production.
- Requirement document from the customer. In normal scenarios customer never writes a formal document until really he is so matured. But we need to document and the customer should sign saying yes this is what he wants.
- Customer should also define the risky sections of the project. For instance in a normal accounting project if a voucher entry screen does not work that will stop the accounting functionality completely. But yes if reports are not derived the accounting department can stay with it for some time. Customer is the right person to say which section will hit him the most. With this feedback the testers can prepare a proper test plan for those areas and test it thoroughly.
- Customer should also provide proper data for testing. Feeding proper data during testing is the most important thing. In many scenarios testers key in wrong data and expect results which are of no interest to the customer.
Expectation from the end user for testing