Developers will have to test the software themselves extensively. Even though they are also the one who have developed the software, they still have to run it extensively. These are the usual steps developers follow in testing their software:
- Checking of Syntax – The software is checked as it is. Developers just run software and look for possible errors. A very basic checking to know if there are major functions and errors that will occur.
- Code inspection – After the execution, developers review their codes to look for possible bugs or errors in coding technique. Even though it has worked in initial checking, the language has to be checked extensively to predict possible problems in some executions.
- Desk Checking – In this part of the testing, developers check the code and the software at the same time. Each line of command is tested if the desired output is met. This is done manually as each line is expected to work and one way of making sure it will work is to manually check each line so that developers will know what output the line has created.
- Walkthrough – After checking the software themselves, its time to present the software to the experts. Not the upper management but possibly experts on the coding language or other developers of this type of software. The developer will present their work to the pool of professionals who will scrutinize their work. It is also important for the developer to present not only the coding technique but also program itself. Using simple case studies the software will somehow provide answers faster or with a better result.
- Module Testing – After the walk through, developers will again check the software in terms of individual modules. Each module will be tested extensively for possible errors.This is also known as Unit Testing.
- Integration Testing – Once the module has been tested, it is time to test them as being integrated to other modules. In this type of testing, developer checks that interface between the two module is working properly.
- System Testing – After the integration, the whole program will again be tested. Case studies will again be applied with integrated software.
