Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

There are several alternate ways to structure that code fragment. If you already have %HASH primed to contain keys for the values you're trying to match,

if (exists $HASH{$s}) { my $foo = $HASH{$s}; ...

which lets you write a unit test against the initialization of %HASH, in addition to a smaller number of tests of foo(). The risk of that approach is that the link between %HASH and its use in foo() is tenuous from the perspective of the tests. (I.e., how can you prove, via tests, that there's any association between %HASH and the behavior of foo()?)

Another approach is to move the matching into a separate sub, which lets you write more focused unit tests against the matching subroutine, but which still leaves you with the tenuous link problem.

One approach to establishing linkage is to use Test::Resub to temporarily replace the search subroutine with a test-only version that records that it has been invoked, and then write a test against foo() to verify the invocation. (We used to call these "plumbing" tests, since their goal is to verify that A calls B without asserting anything about the behavior of B, leaving assertions about B's behavior for other tests.)


In reply to Re: coverage influencing form by dws
in thread coverage influencing form by davidrw

Title:
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 How to display code and escape characters are good places to start.
Log In?
Username:
Password:

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

How do I use this?Last hourOther CB clients
Other Users?
Others drinking their drinks and smoking their pipes about the Monastery: (4)
As of 2024-03-29 15:35 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found