comment on

I understand where you're coming from now. I *think* the Test::* should work okay as long as I code a pass/fail. What I do like is the fact that the Test::* are already built and are relatively simple to use. I agree that depending on what I'm testing, I might have to shoehorn it.

I guess I'm looking for reasons NOT to use it.. At this point, I see only that some extra coding of the test may only need to be done.. But since I've fallen for too good to be true with some perl modules on cpan before (fits my need but no maintainer, doesn't fit my need exactly but maintainer goes ballistic when I submit a patch extending it without getting permission first from the maintainer to modify the module in the first place for my own use, etc.), I'm skeptical

Jason L. Froebe

p.s. Hava a good flight! No delays!

No one has seen what you have seen, and until that happens, we're all going to think that you're nuts. - Jack O'Neil, Stargate SG-1

In reply to Re^4: using Test::* modules for generic testing of non perl stuff? by jfroebe
in thread using Test::* modules for generic testing of non perl stuff? by jfroebe

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.


Perl Monk, Perl Meditation
	PerlMonks