Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things
 
PerlMonks  

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

by davido (Cardinal)
on Sep 12, 2019 at 17:25 UTC ( [id://11106082]=note: print w/replies, xml ) Need Help??


in reply to How do track down underlying reason for smoke test failure

You have the ability to add environment exploration to your tests, of course. Your tests run on the smoker. So add a diag to your tests that produces output about some of the hunches you want to chase down -- things that don't already show up in the smoker's output but that you think would be helpful to know.

Also when your tests encounter failures, there will be an entry in http://analysis.cpantesters.org/ for your module. Sometimes it takes 24 hours or more to show up, and it only shows up when the distribution has test failures. As a hint, you can create a development version number -- see perlmodstyle for how to do that, and that will allow you to iterate without impacting your typical users.


Dave

Log In?
Username:
Password:

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

How do I use this?Last hourOther CB clients
Other Users?
Others wandering the Monastery: (3)
As of 2024-04-25 20:05 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found