Yes.
On Thu, Oct 24, 2013 at 11:16 AM, Ralf Eggert <[email protected]> wrote: > Hi Franz, > > thanks for your reply. > > > I don't think its misleading. For unit test purposes and i emphasize the > > "unit" it serves the purpose of the mocked object, the TableGateway in > this > > case. > > It really all depends on what you are trying to accomplish. If you just > > want to unit test your single method then you should be fine with your > > solution above. > > Integration and functional test is another layer on top of unit test to > > make sure everything work as intended. > > So, a Unit Test for a TableGateway class would only test, that my > fetchList() method is returning a ResultSet class, while an integration > test will check, that the ResultSet really returns the expected data > within the ResultSet? > > But from the TDD point of view, I will need a Unit Test to check the API > and the expected objects and an Integration Test (based on > PHPUnit_Extensions_Database_TestCase for example) to check stuff like > sorting and getting the correct results. > > Is that correct? > > Thanks and best regards, > > Ralf > > -- > List: [email protected] > Info: http://framework.zend.com/archives > Unsubscribe: [email protected] > > >
