This activity can vary depending on the computer operating
environment. If computer time is at a premium, a 'remote'
testing procedure conserves both computer and programming time.
The drawback of this approach may be the elapsed time between
program tests. For sheer speed in testing programs, 'hands on'
testing by Software Engineering will produce tested programs in
the shortest elapsed time but at considerable expenditure of
manpower and computer time.
Regardless of the testing environment, the 'debugging'
of programs is an iterative process. During Activity B, the
program was compiled and all grammatical/syntactical errors
encountered were corrected (until a "clean" compile is
obtained). During Activity D, Software Engineering tests for
procedure logic. This process is repeated until all errors
are eliminated.
The program code, documentation and test results are then
submitted to Quality Assurance to be reviewed for compliance
with installation standards for program documentation, coding
and testing.
The result of this activity is a tested and operational
program.