Before my system is handed over to the end user, tests will have to be carried to make sure that everything is in working order and the system doesn’t do anything wrong
Member rating: No Rating | Words: | Submitted: Sat Mar 10 2007
On the left is an image preview of every page of this document, and below are the first 150 words with formatting removed:
Test Strategy Before my system is handed over to the end user, tests will have to be carried to make sure that everything is in working order and the system doesn't do anything wrong. Everything in the database will be tested (e.g. command buttons, reports, queries, tables). If some of the tests fail then they will have to be reviewed and changed so that it works. Until the system isn't working to a set standard it cannot be passed onto the end user. There are several objectives of testing that need to be answered: 1. Does the system work properly? 2. Does the system do everything specified? 3. Does the system crash? 4. Are any functions missing? There will be a test strategy used when performing the tests. Each individual object will be tested (e.g. table, query, command button, report). Every command button will be tested and made sure that it works. Valid and invalid information will...

