All programs have to be compiled/assembled for testing. Before this however, a complete program description should be available. Included is the purpose of the program, its use, the programmer(s) who prepared it and the amount of computer time it takes to run it. Program and system flowcharts of the project should also be available for reference.
In addition to these activities, desk checking the source code uncovers programming errors or inconsistencies. Before actual program testing, run order schedule and test schemes are finalized. A run order schedule specifies the transactions to test and the order in which they should be tested. Hi priority transactions that make special demands on the candidate system are tested first. In contrast, a test scheme specifies how program software should be debugged. A common approach, called bottom-up programming, tests small-scale program modules, which are linked to a higher-level module, and so on until the program is completed. An alternative is the top down approach, where the general program is tested first, followed by the addition of program modules, one level at a time to he lowest level.
No comments:
Post a Comment