Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

"That means you wouldn't use Test::More to check every possible outcome of a subroutine but only a a few specific tests to make sure the program is running correctly. Is this the correct approach or am I completely wrong?"

It is the start to some kind of a correct approach. The point of math proofs is that you don't have to show every value of X or Y, etc. You can treat unit testing the same way with a few caveats, the main one being bug fixes. When someone reports a bug, write (add) a unit test to recreate the bug. The test should fail. Fix the bug. Include the bug report number in the name of the test.

The flip side is writing too many tests, especially if they take too long to run. Developers will stop running them and they will go to the weeds, becoming a hindrance. You have to keep your unit tests current and they need to finish in a timely manner.

"Also, what would be the best method for automatic testing of scripts we use? "

I have my own personal Jenkins server that i use to test and build my distributions. I also use github and travis-ci which are free services. The gist is you use github as a repository for you code and travis-ci to build and test. Hope this helps. :)


(the triplet paradiddle with high-hat)

In reply to Re: Testing in Perl by jeffa
in thread Testing in Perl by mrguy123

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others studying the Monastery: (3)
As of 2022-09-25 02:28 GMT
Find Nodes?
    Voting Booth?
    I prefer my indexes to start at:

    Results (116 votes). Check out past polls.