I would write that as separate pass calls, which allows you to see which one matched.

if ($var eq 'a') {
    pass( 'var is an a' );
}
elsif ($var eq 'b') {
    pass( 'var is a b' );
}
else {
    fail( "var was $var" );
}

[download]

Be careful here and don't go too tricky in the code flow, otherwise you may end up with a pass() in one branch, and nothing in the other, which will lead to strange off-by-one errors in the test plan. KISS.

• another intruder with the mooring in the heart of the Perl

In reply to Re: 'either or' value unit test case in Test::Simple or Test::More by grinder
in thread 'either or' value unit test case in Test::Simple or Test::More by palette

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


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.