Otherwise, you'll probably end up doing more work to manage all the code coverage cases. That is, you'll need to do the same code coverage, but you'll have to reason out how to get to each submethod, and ensure you pass it the right parameters to ensure all of it's children get called.
I find that this is rarely a problem in real world usage. This is probably a side effect of doing TDD. If I factor out a private method from a public method then the coverage of my test suite isn't going to change, and if I change my private method I'll always write a test first.
To put it another way, if you aren't exercising all of the code in your private methods why did you need to write them in the first place?
-
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.
|