I think that once you have a test framework in place, which is used for core regression tests, you can easily expand it to include modules. I really think testing is mandatory, especially for a project that is powering a lot of high-traffic and high-visibility websites. It may not be easy, it may not be exciting, but it keeps the platform stable and helps uncover bugs early. I really do not grok why you would think this requirement to be a bad idea. Furthermore, breaking backwards compatibility is not a bad thing if it improves stability, performance, ease of use, etc. Would you rather like to see Drupal go the x86 way?
I think that once you have a test framework in place, which is used for core regression tests, you can easily expand it to include modules. I really think testing is mandatory, especially for a project that is powering a lot of high-traffic and high-visibility websites. It may not be easy, it may not be exciting, but it keeps the platform stable and helps uncover bugs early. I really do not grok why you would think this requirement to be a bad idea. Furthermore, breaking backwards compatibility is not a bad thing if it improves stability, performance, ease of use, etc. Would you rather like to see Drupal go the x86 way?
March 15, 2008 - 21:36