The acceptance test confirms that Tradecloud works as agreed for your process before you go live. It gives the project owner and sponsor the basis to accept the implementation.
For: buyers
Template
Download the acceptance test scenario template (Excel) and extend it with scenarios specific to your process.
Goals
All test cases are executed.
All critical and major defects are verified and closed.
Open medium and low defects or suggestions are discussed: roadmap or not, and with or without cost, to be solved later.
Product suggestions and improvements are not part of the acceptance test. The scope is defined per project.
Planning
Prioritize. Identify the most critical features before testing and test them first. If time runs short, the critical items are covered and developers get early feedback on serious defects.
Schedule. Plan preparation, execution and reporting, with checkpoints to track progress.
Execute iteratively. Run the tests. Document any defects, discuss and fix them, and test again.
Report. Deliver a short test summary report with open issues, to support the accept-or-reject decision, and a detailed final report with every test, its pass/fail status and the issues found.
If time runs out, list the untested items with a risk assessment.
Common risks
Not enough test time | Work from a prioritized critical path of tests. |
Incomplete requirements | Track which tests cover which requirements. |
Test environment differs from production | Document the differences and keep them as small as possible. |