note
ignatz
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&trade;.
<p>
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&trade;.
<pre style="font-family: terminal, courier, courier new, monospaced;">
()-()
\"/
`
</pre>
206802
206862