Hey y'all, In order to make the bug tracking and fixing process more of a community effort, we'd like to encourage people to attach unit tests to new bug tickets going forward. Unit tests help us identify the exact source of the bug (which isn't always immediately apparent: a bug may seem like it's in one area of the code, when it's actually somwhere completely different), as well as any and all other code that might be affected by any changes to the problem area.
While Cake code is fairly simple, there are many places where the bugs found are hidden in other parts not easily recognizable by someone less familiar with the code. This does not mean your patch is worthless, but rather than spend the time patching it, you could write a test that would prove the code we wrote is wrong. We dont like it when we fail tests so you can be assured that it will be fixed quickly. It's also helpful since, once the bug has been fixed, your test will be added to the core test suite as a regression test, to ensure that the bug doesn't show up again. A short tutorial on how to set up a unit test for the CakePHP core has been posted to the Trac wiki, and you can find it here: https://trac.cakephp.org/wiki/CoreTests Thanks for your help everybody. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
