In the scenario you describe, there is no reason that your test script would inherit from Class::DBI or that your CDBI class would use T::MO. Using T::MO and calling CDBI objects in the same test script is not a problem, and my company does this in our tests without issues. That is not what is being shown in this example.
Mutant is using T::MO from a Class::DBI class, not from a test script.
I am honestly not trying to be difficult and I have no stake involved in the success of T::MO or CDBI, but I really don't see any reason to use these modules in the way that is shown here. The whole point of T::MO is that the modules being tested don't even know it's being used.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.