Testing, Debugging and Documentation

Debugging-

Program debugging is the process of finding and correcting errors ("bugs") in a computer program. Testing and debugging are vital steps in developing computer programs. They are also time consuming steps. In fact, the time spent in testing and debugging often equals or exceeds the time spent in program writing.

There are three types of errors that occur in a computer program. These are-

1. Syntax Errors
2. Run-time Errors
3. Logical Errors

Syntax Errors- A syntax error in the program when the rules or syntax of the programming language is not followed. Such programming errors typically involve incorrect punctuation, incorrect word sequence, undefined terms, or misuse of terms. The Python interpreter immediately reports it, usually along with the reason. All syntax errors must be found and corrected before a program is made to run. 

Runtime Errors-  A runtime error is an error that causes abnormal termination of program during execution of a code. Runtime error, is also called an exception. A number of built-in exceptions are defined in the Python library. 

Logical Errors- A logical error is a mistake in a program source code that results in incorrect or unexpected behavior. When the logical error occurs, the computer does not print the correct output. The computer does not tell you what is wrong.

Testing-

Testing is the process in which a program is validated and it is completed when all desired verifications in terms of the specifications have been performed. It is a definable task in which how and what to take place at a specific time in the development cycle.

What is Documentation?

Documentation of a program involve collecting, organizing, storing and maintaining a complete historical record of programs and other documents used or prepared during different phases of the system development. The main aim of documentation are as follows:

1. To make available a clear description of the work done so far and help in the design of the system by working to a set of standards. The documentation needs to be kept up to date throughout the project.
2. Good documentation ensures that everyone involved in the system design (namely system designers, programmers and users) fully understands how their part of the system will work. For example, what data will be inputted and how, and what information will be available from the system.