Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
I have created a new compatibility module that allows Test::LectroTest and the Test::* family of modules to be mixed together. The implementation relies upon a tiny element of hackishness right now but seems to work well.

The idea is that you build up test plans as usual with Test::More and friends. Just use Test::LectroTest::Compat if you want to use specification-based property checks as part of your plans. Define your properties in the usual LectroTest way and then use holds(property) assertions to insert property checks into your test plan. Properties that are checked within a holds assertion are free to call ok()-style assertions provided by Test::* modules (such as Test::Deep).

When invoked this way, LectroTest runs batteries of trials to check your properties, as usual, but instead of reporting the results of each battery using LectroTest's own reporting engine, it passes the result out to Test::Builder, which records and reports the result along with the rest of your plan's tests.

Give it a try and let me know what you think.

See the LectroTest FAQ list for more on the subject and info on where to download the (presently in-development) module.


In reply to Try Test::LectroTest::Compat by tmoertel
in thread Can I use Test::Differences with Test::LectroTest? by pernod

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 musing on the Monastery: (4)
As of 2024-04-19 16:49 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found