Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change
 
PerlMonks  

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

by bliako (Monsignor)
on Sep 12, 2019 at 12:24 UTC ( [id://11106064]=note: print w/replies, xml ) Need Help??


in reply to Re^4: How do track down underlying reason for smoke test failure
in thread How do track down underlying reason for smoke test failure

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)

Replies are listed 'Best First'.
Re^6: How do track down underlying reason for smoke test failure
by NERDVANA (Deacon) 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"

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://11106064]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others perusing the Monastery: (5)
As of 2024-04-19 06:28 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found