I was thinking about this in a drive to and from an interview. If something works for you, that's kewl. It's not the way I would do it, and I would worry if my system relied on it, but to each his/her own. Hey, no matter what, writing tests is a good thing™.
My main objection to the original post is with using Perl to test Enterprise Java Beans. A part of the EJB 2 standard includes interfaces that are only visible from within the bean itself. That means that no Perl, Resin, XML, HTTP or carrier pidgeon thingamabob is going to be able to test what is going on within those parts of that bean. Bottom line, to me not being able to test your internals is bad, thus relying on Perl to test your EJBs is a bad thing™.
()-()
\"/
`
-
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.
|