Why is Module Testing Important for a Project?

December 05 10:00 2014 by Nataliia Vasylyna Print This Article

Modern software products are complex systems; their functionality is rich, they consist of many different modules. That is why every software testing process includes verifying quality of the system modules.

Module testing is one of the most significant activities of a project, as problems with an application module always have a great impact on the whole program. Fixing of such defects at late stages of software construction is expensive and time-consuming.

The goal of module testing is to make sure that the code of the application modules is correctly written, the modules have all the intended elements, procedures and so on. It is executed at the beginning of web site testing, desktop testing or mobile application testing.

Module tests are usually automated. The development team frequently carries out some module tests before passing the modules to the test engineers.

A software testing company executes smoke testing of the software modules at first. If they pass, testers check the module more detailed. If the smoke testing detects problems, the defects are logged, and the module is improved by the programmers, who are responsible for it.

All the errors are logged into the error tracking tool. When they are fixed, test engineers carry out regression testing to make sure that the defects do not exist any more, and no new ones appeared.

When the modules are verified, they are joined together by the programmers and the next testing type – integration testing is executed.