Feature: Maybe a new Test2::Tools::Lib can be provided

[XSven]

Similar to the Test2::Tools::Target, I think it could be convenient to have a Test2::Tools::Lib tool. When used like use Test2::V? -lib; it unshifts t/lib (as a default) to @INC. Maybe the tool/option can have an optional ARRAYREF argument to unshift more libs to @INC. What do you think?

[exodist]

I will think on it. At a glance it feels like it does not save much. Most of the other shortcuts save multiple lines of boilerplate, though -target does not, so that is similar.

However -target does not provide typical functionality. Someone seeing -lib might have to look up what it does. By contrast someone seeing use lib "t/lib"; should know what it does and it is less likely to require knowledge. Someone seeing use Test2::Tools::Target would need the same research as use Test2::Vx -target. So tests that just use lib are more readable/maintainable.

This is not a "no". but I need to consider it for a while. Might also help if anyone else monitoring wanted to weigh in.

[XSven]

I would like to mention 2 more things.
First my use lib boilerplate is

use File::Spec::Functions qw( catdir );
use lib catdir( qw( t lib ) );

I try to avoid stringified paths if possible. This could be done behind the scenes by the -lib option.
Second I am asking myself if it is really the test script that is responsible for adding new paths to @INC or is it the harness (prove or yath) that should be configured differently. prove for example could use -It/lib.