Re^4: How do track down underlying reason for smoke test failure

OK, so I guess a simple fix would be to just throw a use lib '.'; into Test::Classifier.

$PM = "Perl Monk's";
$MCF = "Most Clueless ~~Friar~~ ~~Abbot~~ ~~Bishop~~ ~~Pontiff~~ ~~Deacon~~ ~~Curate~~ ~~Priest~~ Vicar";
$nysus = $PM . ' ' . $MCF;
Click here if you love Perl Monks

Comment on Re^4: How do track down underlying reason for smoke test failure Select or Download Code

Replies are listed 'Best First'.
Re^5: How do track down underlying reason for smoke test failure by syphilis (Archbishop) on Sep 12, 2019 at 12:36 UTC
OK, so I guess a simple fix would be to just throw a `use lib '.';` into Test::Classifier. Or, I think: `use lib './t/TestMods';` [download] Cheers, Rob	[reply] [d/l] [select]
Re^5: How do track down underlying reason for smoke test failure by bliako (Abbot) on Sep 12, 2019 at 12:24 UTC
Yes I guess. Although `use lib 't/TestMods';` (and changing all `use t::TestMods::XXX;` to `use XXX;` maybe more in the spirit of removing `.` from INC for security purposes ... (* I am hardly an expert, please get 2nd opinion)	[reply] [d/l] [select]
Re^6: How do track down underlying reason for smoke test failure by NERDVANA (Priest) on Sep 14, 2019 at 02:28 UTC
"In the spirit of removing ." is to remove all path references that depend on the current directory, which is dynamic and depends what other code has executed inbetween. `use FindBin; use lib "$FindBin::Bin/TestMods"` [download]	[reply] [d/l]