comment on

I'd split up the different phases ( like

) into different subs and unit test them against typical cases.

And after testing all small building steps you test some big one combining easier ones and so on.

Of course you have to mock data, but with this approach you only need to simulate the simpler building cases that convince you.

The trick is to add new tests as soon that you discover a bug caused by an edge case you forgot to cover.

With this incremental approach the probability of bugs shrinks very fast in linear time.

I think a good test suite combines the qualities of a spider web and a pyramid.

Cheers Rolf
_{(addicted to the Perl Programming Language and ☆☆☆☆ :)

Je suis Charlie!}

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 How to display code and escape characters are good places to start.