Unit Testing Vs Module Testing

In testing world, commonly used terminologies for testing a small indenpendant set in an application or system is called as Unit Testing or Module Testing. The purpose of this type of testing is to make sure a unit in an application or system is working as expected indenpendantly. Both the areas in SDLC i.e. Development team and Testing team perform this kind of testing. The end goal for both the teams is same to make sure that unit is working as expected.

If the purpose and the end goal is same then why both the teams need to do this testing. There must be some difference which raises the need for both the team to do it. Or is it a redundant testing that is being done just because of different teams from different areas are involved in SDLC.

Testing approach is a major difference why both the teams need to do it. Development team needs to verify whether the code or programme written for a specific unit functions as expected and as per the system design. Whereas testing team needs to verify whether that specific unit of an application / system works as expected and as per the business requirements.

If that is the case then why we call it as Unit Testing OR Module Testing. On the similar there should be some difference due to which there are two names to this kind of testing.

Again testing approach is the difference. The approach taken by development team is more from system perspective and is called as Unit testing. Whereas the approach taken by testing team is more from functionality/business requirements perspective. For testing team the unit of an application is nothing a but a small module in full life cycle of that functionality. Thats why the testing done by the test team is called as Module testing.

This is not the only difference, there may be more ….