Tyler MacDonald writes:
Chris Dolan [EMAIL PROTECTED] wrote:
[lots of author test examples, including:]
* versionsync.t - Checks that the $VERSION is the same in all bin/*
and *.pm files. This test is pointless after release, since it's
already been tested before release
*
Adam Kennedy [EMAIL PROTECTED] wrote:
Write this up. Then exhaustively test it on every single Perl platform
(50ish?) and every Perl version back to 5.004, including a random
collection similarly weird combinations (5.004 VMS, that 5.6.0 from
RedHat 7, 5.6.1 on Windows 95).
I let
On Thu, Feb 02, 2006 at 02:56:09AM -0800, Tyler MacDonald wrote:
A new module doesn't need to be added to the core, so long as there
is a way that we can reliably detect when a person wishes to build and test
any given perl package for an objectively unselfish purpose such as
Hi,
Tyler MacDonald wrote:
And now that I think about it, I'm not so convinced about that whole
concenience for the end user nonsense. If they're mucking about installing
perl modules from the CPAN packages by themself, they're probably developers
that need some extra time to sit there
On Feb 1, 2006, at 10:35 PM, Tyler MacDonald wrote:
Chris Dolan [EMAIL PROTECTED] wrote:
There is a class of tests that module authors perform that end users
are not expected to run. For example code coverage tests, spelling
tests, coding style tests, etc. These tests are either
Steffen Mueller [EMAIL PROTECTED] wrote:
And now that I think about it, I'm not so convinced about that whole
concenience for the end user nonsense. If they're mucking about
installing perl modules from the CPAN packages by themself, they're
probably developers that need some extra time
* Chris Dolan [EMAIL PROTECTED] [2006-02-02 16:55]:
On Feb 1, 2006, at 10:35 PM, Tyler MacDonald wrote:
I really like this idea. But as you pointed out, it's not just
authors that need to worry about running these tests, it's
packagers (ppm/deb/etc), automated testers
A. Pagaltzis wrote:
* Chris Dolan [EMAIL PROTECTED] [2006-02-02 16:55]:
On Feb 1, 2006, at 10:35 PM, Tyler MacDonald wrote:
I really like this idea. But as you pointed out, it's not just
authors that need to worry about running these tests, it's
packagers (ppm/deb/etc), automated testers
Chris Dolan [EMAIL PROTECTED] wrote:
* copyright.t - Ensures that there is a Copyright .([localtime]-
[5]+1900) somewhere in every .pm file. Will break 11 months from now.
* distribution.t - Relies on Test::Distribution, which is not in my
prereq list
* perlcritic.t - Runs
A. Pagaltzis [EMAIL PROTECTED] wrote:
I was just gonna say. It???s pointless for anyone but the author to
check POD or test coverage.
I agree about the POD coverage. But if I got a different level of
code coverage on somebody else's system than my own? I'd be very interested
in finding
On Thursday 02 February 2006 10:04, Tyler MacDonald wrote:
A. Pagaltzis [EMAIL PROTECTED] wrote:
I was just gonna say. It???s pointless for anyone but the author to
check POD or test coverage.
I agree about the POD coverage. But if I got a different level of
code coverage on
On Thursday 02 February 2006 02:56, Tyler MacDonald wrote:
And now that I think about it, I'm not so convinced about that whole
concenience for the end user nonsense. If they're mucking about
installing perl modules from the CPAN packages by themself, they're
probably developers that
* Christopher H. Laco [EMAIL PROTECTED] [2006-02-02 18:50]:
On more than one occasion, I've had pod2html/man (troff) errors
under FreeBSD that were only found by running the author tests
there, even though the pod syntax/coverage was perfectly fine on
two other platforms.
Are you sure that’s not
* copyright.t - Ensures that there is a Copyright
.([localtime]-[5]+1900) somewhere in every .pm file. Will break 11
months from now.
* distribution.t - Relies on Test::Distribution, which is not in my
prereq list
snipped ones that need your personal files, you are certainly right
there.
chromatic wrote:
On Thursday 02 February 2006 10:04, Tyler MacDonald wrote:
A. Pagaltzis [EMAIL PROTECTED] wrote:
I was just gonna say. It???s pointless for anyone but the author to
check POD or test coverage.
I agree about the POD coverage. But if I got a different level of
code
On Thursday 02 February 2006 17:45, Adam Kennedy wrote:
Just as a datapoint on this topic, the PITA request objects (as of 5
minutes ago) now support the ability to explicitly set environment
variables you want set when running the tests, on top of the
default-but-overridable ones like
* Adam Kennedy [EMAIL PROTECTED] [2006-02-03 02:45]:
But I don't know that I like disttest autodetection. I quite
like being able to run the additional tests manually if needed,
and not be limited to only during the disttest process.
Maybe do it the other way around? Define INSTALL_AUTOMATED and
On Thu, Feb 02, 2006 at 10:01:48AM -0800, Tyler MacDonald wrote:
I strongly feel that authors should keep everything necessary
for their distribution public; either in the CPAN distribution
itself, or via a permanent publicly available version control
system.
Who's to say you won't lose interest
On Feb 2, 2006, at 9:19 PM, Yitzchak Scott-Thoennes wrote:
Chris, how are you currently set up to run these tests only when
preparing a release?
I make no such distinction. Instead, I see these tests as part of my
day-to-day development and run all of them with every ./Build
test.
That doesn't allow for what happens if both are missing.
I find the following a good general rule.
There are tests that test how the code actually works, that could
convievably be different on different platforms.
These are always on.
There are tests for issues that are almost certainly
Chris Dolan [EMAIL PROTECTED] wrote:
There is a class of tests that module authors perform that end users
are not expected to run. For example code coverage tests, spelling
tests, coding style tests, etc. These tests are either prohibitively
expensive or complicated or unpredictable
The trouble is, EVERYONE wants to add just one more little dependency
(me included *cough*Params::Util*cough*).
I'll make you a deal.
Write this up. Then exhaustively test it on every single Perl platform
(50ish?) and every Perl version back to 5.004, including a random
collection similarly
22 matches
Mail list logo
