I have small conceptual problem learning the path of TDD. I have an application that is nicely modularised. Two of the logical groups of the modules in it are business entity modules and data access modules. The business entity modules implement the business concepts and accesses the database through the data access modules. The data access modules are homegrown modules that behave like DBIx::Simple.
I am trying to test one of the business entity modules. I am using Test::MockObject to mock the call to the data access modules. While doing that, I find myself tempted to use DBD::Mock to mock the sql results that the data access modules will accept and then return it in the appropriate data structure, instead of just mocking the return value. However, I feel like it is an integration testing and not unit testing.
Is it a good practice to test multiple modules at once in unit testing? What is the line that differentiate between unit testing and integration testing?
Thanks
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |