Software-Development---Testing7
Software-Development---Testing7
Sign in "
File Home Insert Draw Design Transitions Animations Slide Show Review View Help G L Comments Present Editing
12
5
•Before a system is used, each sub-system must be tested to ensure it works correctly and interacts correctly with other
sub-systems
•Programs are tested by running them on a computing device while pseudocode and flowcharts must be dry run
manually. Both require suitably chosen and different sets of test data. The outputs are then compared to the expected
output to check if the algorithm works as intended
•Test data comes in several generic types:
.
6
• Normal
• Normal test data is data that a system would be expected to handle on a day-to-day basis, be accepted by
the algorithm and produce expected results
• Examples could include entering people's names and addresses, phone numbers, student grades as a
.
percentage, etc
7 • Student percentage grades could involve test data such as: 34, 41, 56, 78, 12, 92
• Invalid
• Also known as erroneous data, abnormal data is data that is expected to fail and should be rejected by the
system. This is used to prove that the system works correctly by rejecting incorrect data
• Examples of abnormal data would be entering numbers instead of someone's name, or entering text
.
instead of numbers
8
• Student percentage grades abnormal data could involve test data such as: abc, 7&n, Harry, £300, <!%, etc
• Unusual Test Data
• Extreme test data is the maximum and minimum values of normal data that are accepted by the system
• Examples could include percentages (0 and 100), days in April (1 and 30) or the number of characters in a
passwords range
.