Are you signing a contract to outsource a software development project to a vendor? Ask these questions to make sure you know what you're getting and are getting what you are paying for.
Are you doing usability testing on your application's user interface? Use this checklist to perform a thorough review on how easily users interpret, navigate and respond to the GUI.
Integration testing ensures that each component of the application you develop works correctly within the system as a whole. Record any errors discovered through integration testing and request system changes using this form.
You've tested the new system or application and found some bugs that require the attention of the development team. This form will help you characterize the type, description and disposition of post-testing system change requests.
This form provides a quick and dirty assessment rating for product and development quality.
Here is a solid outline of a plan for testing individual development components in context with the overall system.
The system is ready for testing, and you'd better check to see if everything is there. Formalize the hand-off process between the development team and the testing team with this checklist and signoff form.
Oops! isn't what your client wants to hear at the eleventh hour in the delivery cycle. Use this sample QA plan to verify that the data warehouse (or data mart) has been designed and built correctly before it undergoes user acceptance testing.
Improved deliverable! The new CIS system isn't ready for prime time until business users have tested it. This plan provides guidance on the how, who, when, where, why and what of acceptance testing.
A handy spreadsheet for recording Data Warehouse QA issues, from data transformation to report generation problems.
|
"The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man." - George Bernard Shaw |
