Testing and Debugging

Testing and Debugging

Testing involves finding problems in the code. What does one Test for?

Compilation Errors.

Syntax errors: The compiler cannot understand user’s program because it does not follow the syntax.

Common syntax errors are:

• Missing or misplaced; or}
• Missing return type for a procedure.
• Missing or duplicate variable declarations.

Type errors

• These errors include type mismatch when the user assign a value to a variable and type mismatch between actual and formal parameters.

Runtime Errors

• Output errors: These errors result when the program runs but produces an incorrect result.
• An output error indicates an error in the meaning or logic of the program.
• Exceptions: These errors occur when the program terminates abnormally.
• Examples include division by zero and out of memory. Exceptions indicate an error in the semantics or the logic of a program.

Nontermination errors

• These errors occur when the program does not terminate as expected, but continues running endlessly.
• Debugging consists of isolating and fixing the problems.
• Testing and debugging are necessary stages in the development cycle, and they are best incorporated early in the cycle.
• Thoroughly testing and debugging individual components makes testing and debugging integrated applications much easier.

What is Documentation?

Documentation of a program consists of written description of program′s specification, its design, coding, operating procedures etc.

Documentation is either incomplete or inaccurate, making the users and maintenance programmers irritated and annoyed over it.

Documentation can be broadly classified into two types:

• Documentation for users.
• Documentation for maintenance programs.

The written text and comments that make a program easier for others to understand use and modify.

The compiler in the compilation process ignores comments.

It provides information about the steps and procedures.