Bryce Harrington wrote:
> Beta testing - CPAN tracks intra-module dependencies, and does automated > testing, but only on released modules. It would seem useful to allow > an author to upload a "beta" version of their module, and then run the > tests of a dozen or so modules that depend on it. This way, you would > gain confidence that your next release won't break everyone else's > code (or be able to explain why, if it must.) > > Obviously, this testing would mostly just benefit core modules, but > you could argue that those are probably the ones most in need of solid > QA. This could save worry time for the core module authors, allowing > them to focus more of their energy into improvements. I like this idea, especially running tests on an uploaded distribution before it becomes a "real" release. I know I've caught myself several times when my tests run just fine, I upload to CPAN and then differences in the way the CPAN shell runs my tests cause it to fail. It would have been nice to catche these failures before others start upgrading. -- Michael Peters Developer Plus Three, LP
