On Feb 6, 2006, at 1:37 AM, Adam Kennedy wrote:
In fact, what you just asked is already listed in the PITA
documentation as within it's scope.
For lack of a better name, I've called it Fallout Testing.
As opposed to Rot Testing, which is when your module doesn't
change, but makes sure it s
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
* Bryce Harrington <[EMAIL PROTECTED]> [2006-02-05 21:40]:
> http://search.cpan.org/src/BRYCE/Test-Parser-1.00/t/01_script_compile.t
I know this is beside the point, but I have to point out that
this script will break on at least Windows – and probably every
other non-Unix OS as well.
* Sébastien
Bryce Harrington wrote:
Default tests - Like probably a lot of perl module writers, I don't
write tests nearly as often as I should, but I have collected a few
simple default tests that I can toss into a new module and reuse
without modification. For example:
http://search.cpan.org/src
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 o
On Feb 5, 2006, at 2:36 PM, Bryce Harrington wrote:
[snip]
It would seem to be useful if CPAN were to have a couple really
basic
tests like this to run for perl modules that haven't created any
tests
themselves.
Obviously, this only benefits immature modules, but this might be a
