This section describes what happens before code is ready to be committed in to the group CVS repository.
Entry criteria: Since this kind of testing is informal, it is to be carried out while the classes are being coded.
Exit criteria: The coder is confident that his or her code works as required and contains no obvious bugs.
Informal Testing is the testing carried out by a coder while working on a class. The main point of Informal Testing is to increase a coder's confidence in his or her code, and to identify any small bugs early on. As the cost of fixing bugs is smaller the earlier they are found, this step is invaluable for streamlining the testing procedure.
There is no set procedure for Informal Testing, and this is entirely up to the coder to implement. However the coder is encouraged to use the automated testing script provided which allows the coder to efficiently run both unit and integration tests, without the need to submit the test reports.