| || |
EJB component testing
I am fairly new to the Java testing world and I am currently searching for tools for server-side testing using the Java platform. So far, I have found Bean-Test (http://www.empirix.com/Empirix/Web+T...t+testing.html) and Cactus (http://jakarta.apache.org/cactus/index.html).
Have any of you used any of these tools? If so, what are the pros and cons? Are there alternate tools that I should evaluate?
Thanks in advance.
Re: EJB component testing
I just saw your post from a month back on Bean-test. What did you end up going with for an EJB tool? My current client currently has an order in to buy some Bean-test, and I wanted to see what you thought.
I posted what I thought of Bean-test a few days to usenet, so I thought I would paste it here for you guys.
I have finally got around to putting the Bean-test report together that I said I would do a few week ago. (Thanks for the reminder emails!)
The (free) bean-test consulting session with the Empirix engineer went well. Their "quickstart" lasted a bit over an hour, and we successfully tested a few business methods under different load conditions. What is nice is how elaborate the code generation was. bean-test code generated for my java object types which I didn't think the product would do. They even went over the idea of why testing the EJBs individually very early was important, which I supposed they should since they have this tool for it. I wish they spent more time to help to test more of my beans, but the engineer gave me his number so I could call him back later which I did once. However, I got the idea of how to use the tool.
Overall, I can see why bean-test got all those nice reviews by the folks at Bea, the JDJ, and so forth. Also, check out that chapter someone recommended in the Professional EJB book that explains EJB testing using Bean-test. Good tutorial. I recommend Bean-test and have made that recommendation to the "powers that be" here at work.