User acceptance testing
The system will be user friendly.
The safety-critical parts of the system will contain zero faults.
The response time will be less than one second for the specified usage load.
The system will be built to be portable.
Find as many faults as possible.
Test high risk areas.
Obtain good test coverage.
Test whatever is easiest to test.
Features to be tested
To find faults in the software.
To assess whether the software is ready for release.
To demonstrate that the software doesn't work.
To prove that the software is correct.
Enable the code to be tested before the execution environment is ready.
Can be performed by the person who wrote the code.
Can be performed by inexperienced staff.
Are cheap to perform.