There are several objectives of testing that need to be answered:
- Does the system work properly?
- Does the system do everything specified?
- Does the system crash?
- 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 be entered in fields to see if the right outcome is shown (e.g. date).
Below are several kinds of tests that also need to be carried out:
Logical Testing: This will be used to test every aspect of each form, report and query as soon as it is implemented, using valid, invalid and extreme data. Test data will be added to test each code module and results compared with expected results. Sufficient data will be added to ensure that there are at least a few patients with different types of treatments. Subsequent test will often involve adding new data which will then be deleted when the test works satisfactorily.
Functional Testing: Each menu item will be tested in turn to ensure that no function has been missed out.
System Testing: When the system is complete, the whole range of tests will be carried out again to ensure that no errors have been introduced.
Recovery Testing: The computer will be rebooted while the database is open, to ensure that the data is not lost or corrupted in the event of a power failure.
.
Acceptance Testing: The user will then be involved and asked to test all the capabilities of the program to ensure that all the required functions are present and working in the manner expected. This testing may result in further requirements.
The test plan for this system is shown below:
