Detailed · Deep study
1Why test?
The system is tested before it is used so that errors are found and corrected, and so that it is shown to meet the user requirements. Faults found after implementation are more costly and could cause data loss.
2Test designs and strategies
- Test designs cover the data structures, file structures, input formats, output formats and validation routines.
- Test strategies: test each module (part), each function (e.g. each button, each calculation), then the whole system working together.
3Test plans and test data
| Test | Test data | Type | Expected outcome | Actual outcome | Remedial action |
|---|---|---|---|---|---|
| enter age | 15 | normal | accepted | accepted | none |
| enter age | 25 | abnormal | error message | accepted | correct the range check |
| enter age | 11 | extreme | accepted | accepted | none |
| enter age | abc | abnormal | error message | error message | none |
| Type of test data | Meaning |
|---|---|
| normal | data that is within the acceptable range and should be accepted |
| abnormal | data that is outside the acceptable range or of the wrong type and should be rejected |
| extreme | data at the limits of the acceptable range (the largest and smallest acceptable values) – should be accepted |
| live data | real data used by the organisation, used once the system has been tested with test data, to check it works in practice |
4Exam focus
Key words: test plan; test data; normal; abnormal; extreme; live data; module; expected outcome; actual outcome; remedial action.
Quick self-check
Answer in your head first, then reveal.
Normal e.g. 56 (1); abnormal e.g. 150 or −3 or "ten" (1); extreme 0 or 100 (1).
Real data used by the organisation (1).
Test data; expected outcome; actual outcome; remedial action (4).
