Hi
> Question: How do you do your testing? > > I should be doing unit testing but I haven't had time to read more > about how to do it in CakePHP. So I have been testing by simply trying > (clicking) different features on the website. I know ideally unit > testing should be part of the development cycle but at this point my > app has grown so much that I am not sure what the best approach is. > The problem is that when testing manually I often miss something and a > bug gets released. Any suggestions? > You could use simpletest web testing capabilities. And create an integration test. I've written my approach in my blog http://www.gignus.com/blog/posts/view/13. > 5. Both my production and dev environment point to the same database. > The advantage is when a new field or table is added due to a new > feature, the changes done automatically but I often fear I shouldn't > be touching the production environment until the changes are done. > I wouldn't recommend that, because you must be careful to introduce database changes that might break production application. Also, for testing purposes, it's better to start with a clean database on each test. > Question: how do you manage and deploy DB changes? > I hadn't solved this on linux yet, but if you work with some mysql program like mysqlfront on win, you can check the logs and save every alteration to you database, save them to a text file, and run them on production. Good luck! -- Matias Lespiau http://www.gignus.com/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
