> I had a look at this before but didn't want to get into it yet until I have > do my first release. Then I might use it for migrations. I never thought of > it for testing though.
thinking of automatic deployment it is much worth to even create your very first database tables with migrations. > I've been having some discussions about this topic on some other forums and > I think it'd be more suitable to mock the Model from the controller, but > when testing the Models themselves I should test against a real > database...... I think. i would say that a unit test doesn't test any database presence or functionality, but with cake models i've also done some testing against a database. i keep this test database up to date with migrations and usually do some cleanup (truncate) in the setup/teardown methods. greez, timo -- Timo Derstappen http://teemow.com mailto:[EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php -~----------~----~----~----~------~----~------~--~---
