Some historical background, in case it is of some use.
The Oslo Consensus (May 2008)
- $ENV{AUTOMATED_TESTING} - not $ENV{PERL_AUTOMATED_TESTING}
- $ENV{RELEASE_TESTING} - not $ENV{AUTHOR_TESTING} or $ENV{PERL_AUTHOR_TESTING}
- xt/ directory for release and other non-install-time tests (subdirectories optional)
- Support 'requires => { perl => 5.xxx }' and extend to to all 'requires' types
- *.PL should generate META_LOCAL.yml with requirements after dynamic configuration
The Lancaster Consensus (April 2013)
See The Lancaster Consensus and The Annotated Lancaster Consensus for full details.
Historically, AUTOMATED_TESTING has been confusing, used for a number of different purposes:
- I don't want the user to interact with this test.
- This is a long-running test.
- This test depends on an external website (say) and I don't want to stop the user installing if it fails, but I want to see what CPAN smokers experienced.
The Lancaster Consensus clarifies the semantics of AUTOMATED_TESTING and RELEASE_TESTING and adds three new environment variables, making a total of five:
- AUTOMATED_TESTING
- NONINTERACTIVE_TESTING
- EXTENDED_TESTING
- RELEASE_TESTING
- AUTHOR_TESTING
To run module tests after installation, use new target "make test-installed", equivalent to "make test" but without adding blib to @INC.
Some Related CPAN Modules
See also: Perl CPAN test metadata in addition to The Oslo Consensus and The Lancaster Consensus covers The Berlin Consensus (2015) and PTS Oslo (2018)
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
