Provide author/release testing targets.

[FGasper]

It’d be nice to have make authortest set AUTHOR_TESTING=1 then run the tests.

And would it be sensible to change make disttest to set RELEASE_TESTING=1?

[mohawk2]

I've wanted to make an xtest for a while, which I think would be the same thing as your proposed authortest - that might also be a better name!

[Leont]

I have been thinking the same actually (but in the context of Module::Build / Module::Build::Tiny). I wouldn't recommend separate targets, as one may want combinations of the several categories (author, release, automated)

[mohawk2]

In make land, separate targets are how you would combine things - just run each of them.

[Leont]

In make land, separate targets are how you would combine things - just run each of them.

But they're not different things: they're overlapping things. a make authortest releasetest would run most tests twice.

[haarg]

For some prior art, Distar implements some simple EUMM extensions along these lines. "Author mode" is determined by checking if META.yml exists, since it is normally only generated inside the dist dir or tarball. In author mode, it automatically adds xt/*.t and xt/*/*.t to the test file list. It also adds a releasetest target, which is roughly equivalent to RELEASE_TESTING=1 make disttest.

I'm not suggesting those as something EUMM should implement, just for ideas.

Also, target names would have to be carefully chosen. Using releasetest would cause problems with what I'm doing in Distar, and there are many dists providing their own authortest target.

[FGasper]

What about alltests, as an expedient to run all tests?

[mohawk2]

Perhaps xtest gains new life as it doesn't clash with prior art, as far as I know.

make authortest releasetest would run most tests twice.

Not if each of those depended on targets that were the subcomponents. Then those subcomponents would only be run once.

[Leont]

Not if each of those depended on targets that were the subcomponents. Then those subcomponents would only be run once.

That would involve running the harness separately for each of those subcomponents, IMO that is unnecessarily confusing to the user.

It also assumes that the different categories can be found in different places, which is not necessarily true (author and release tests can also live under t/, protected by an environmental variable check like with Test::Is or Test::DescribeMe)

[haarg]

Perhaps xtest gains new life as it doesn't clash with prior art, as far as I know.

Prior art