The test database is simply a temporary database used in unit tests that require a database to run. Say you want to write a test that involves some custom SQL or simply some condition of ordering logic in your model. To be able to run such a test you need an actual database (that you fill with some data to test for).
The point is that you would not want a failed test (or a successful one) to delete lots of data in your normal development database (or god forbid production database). When testing for stored passwords in a user table you don't want your "normal" user-accounts affected by the tests. As for best practices (how to setup, fill and empty the database and such things) I am no authority. I still still mess about with these things quite manually. On Jan 21, 6:38 am, 703designs <[EMAIL PROTECTED]> wrote: > What are good practices for configuring a test database, as defined in > database.php.default's second array? I know that it is unnecessary, > but is it advised to have a test db? --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
