You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would do that subtly different, but that's mostly bike-shedding:
run xt/*.t && xt/author/ if $ENV{AUTHOR_TESTING}
run xt/release/ if $ENV{RELEASE_TESTING}
run xt/smoke/ if $ENV{AUTOMATED_TESTING}
A far more interesting question: should make xtest also run t/. To me, it'd be fairly useless without that.
Actually, given the semantics I just proposed, a separate xtest target wouldn't be necessary. A make test that takes those variables into account would be enough.
Not that either behavior is particularly trivial to implement in a portable makefile :-/
I think 'make xtest' should always run xt/* (minus the special sub-directories) regardless of the environment, just as Dist::Zilla::Plugin::RunExtraTests does... just as mauve is a good colour for that bikeshed. :)
'make xtest' should be available through standard use of Makefile.PL.
IMO it's sufficient to just have it target "xt/*", but if we wanted to get fancy we could glob-expand that and then:
The text was updated successfully, but these errors were encountered: