What is the intended development process in the :: Starter manifest.t module?

Question

When Module :: Starter initializes the project, it creates a test called manifest.t.

#!perl -T

use strict;
use warnings;
use Test::More;

unless ( $ENV{RELEASE_TESTING} ) {
    plan( skip_all => "Author tests not required for installation" );
}

eval "use Test::CheckManifest 0.9";
plan skip_all => "Test::CheckManifest 0.9 required" if $@;
ok_manifest();

When you run tests with Build test, here is part of the result:

t\00-load.t ....... ok
t\boilerplate.t ... ok
t\manifest.t ...... skipped: Author tests not required for installation

I understand the result in a narrow sense ( $ENV{RELEASE_TESTING}not set, so the tests are skipped), but I do not fully understand the big picture. What is the intended development process? I assume that it’s nice to run tests to confirm that my modular manifest is accurate. Should I set this environment variable? If so, at what point in the development process?

Answer 1

, , , . , MANIFEST, , , POD ..

, , RELEASE_TESTING. . , , , , .

RELEASE_TESTING=1 make test ( Build), dist. Dist:: Zilla ( ), dzil test --release. TestRelease, , dzil.

, , AUTOMATED_TESTING AUTHOR_TESTING. AUTOMATED_TESTING CPAN, .