SYSTEM TESTING After the code being generated by the programmer, the testing begins.

Different testing methodologies are obtainable to clean up the bugs that were committed during the system designation. We managed to archive the following testing; testing scenarios, unit testing, overall system testing but failed for side of User acceptance test We begin testing determine more severe bugs that cause our system to hang (stop responding to commands) and this bug might leave the user with no alternative but to restart the system, and as result losing whatever previous work had not been saved. In this case, our programmer tries to his level best find and correct the errors by the process known as debugging .Because of the potential risk to important data, commercial application. Our systems tested and debugged as completely as possible before presented. If minor bugs found after the system put into use are corrected in the next renew; more severe bugs can sometimes be fixed with special software, called patches, that circumvents the problem or otherwise alleviates its effects. Patching is a common means of adding a feature or a function to an existing version of system until the next version of the system, which we assume will have that feature or function included in its design. But we get stabling block to accomplish beta testing (the formal process of asking for feedback on system that is still under development) due limited time because no even single user tested our system even just for trial before final version is put on use. Users are the one who test its functionality and determine whether any operational or utilization errors (bugs) still exist in the system. This due to the fact that a beta test usually one of the last steps a system takes before being used and also includes a draft version of a product's documentation, which is reviewed along with the system by the user.