This queue is for tickets about the Module-Build CPAN distribution.

Report information
The Basics
Id:
48766
Status:
open
Priority:
Low/Low
Queue:

People
Owner:
Nobody in particular
Requestors:
dolmen [...] cpan.org
Cc:
AdminCc:

BugTracker
Severity:
Wishlist
Broken in:
0.34_02
Fixed in:
(no value)



Subject: 'Build disttest' should set $ENV{RELEASE_TESTING}=1
In target disttest, M::B should set $ENV{RELEASE_TESTING}=1 before running "Build test". This would make Test::XT generated tests do something. Currently, the RELEASE_TESTING must be set by the author at his shell level which is not convenient if [s]he uses the same shell to install modules (using CPAN.pm) as a user (instead of as an author). See Test::XT for more information about best practices for author tests. http://search.cpan.org/dist/Test-XT/lib/Test/XT.pm
On Mon Aug 17 05:48:42 2009, DOLMEN wrote:
Show quoted text
> In target disttest, M::B should set $ENV{RELEASE_TESTING}=1 before > running "Build test". This would make Test::XT generated tests do
something. No, it should not. "disttest" is a simulation of user testing -- i.e. in the same directory as packed up in the tarball. Running 'disttest' should be *part* of one's release testing, but it is not the right place to run author-centric release test scripts. I'll change the subject to reflect the need for a release testing action. -- David
Le Lun. Aoû. 17 21:19:13 2009, DAGOLDEN a écrit :
Show quoted text
> No, it should not. "disttest" is a simulation of user testing -- i.e. > in the same directory as packed up in the tarball. Running 'disttest' > should be *part* of one's release testing, but it is not the right place > to run author-centric release test scripts.
Suggestions: - "Build disttest --release" for $ENV{RELEASE_TESTING} - "Build disttest --automated" for $ENV{AUTOMATED_TESTING}
Le Mer. Aoû. 19 08:00:37 2009, DOLMEN a écrit :
Show quoted text
> Le Lun. Aoû. 17 21:19:13 2009, DAGOLDEN a écrit :
> > No, it should not. "disttest" is a simulation of user testing -- i.e. > > in the same directory as packed up in the tarball. Running 'disttest' > > should be *part* of one's release testing, but it is not the right place > > to run author-centric release test scripts.
Well after re-reading your opinion, I agree: release testing could invoke files which are not bundled in the distribution. So a flag for disttest is not the right solution (but it is for AUTOMATED_TESTING).


This service runs on Request Tracker, is sponsored by The Perl Foundation, and maintained by Best Practical Solutions.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.