More Testing EJBs with NetBeans

Following up on my Testing EJBs blog, Geertjan posted a blog about how to integrate Cactus as your testing environment. It's only for Web apps but the procedure is pretty much the same for EJB projects.

There's no automatic generation of test classes, but I assume that since Cactus is based on JUnit, it wouldn't be too hard to adapt the test classes generated by the IDE for JUnit into Cactus tests. Anyone who uses Cactus have any comments on how different the two are?

Also, it looks a bit clunky to do this (have to hack the IDE's build script and add all the libraries to the test classpath yourself). It would be nice to let the user specify which testing frameword she wants to use and then have everything work out of the box. The question is whether enough people use Cactus, MockEJB, etc. to make this a worthwhile use of resources.

Comments:

Hi John

my vote would be for more testing support. The benefits of well-tested software are clear enough. The easier it is to use in NetBeans, the more developers will use it. In an ideal world, as a developer included a class into a project, a corresponding test unit would automatically be introduced -- specfic to that particular type of class (POJO, EJB, Servlet, etc.). The choice of any particular framework is, I think, less important than making the use of each type of test as similar as possible. I've probably glossed over some difficult problems, but thought I'd throw in my tuppence-worth.

Regards
Rik

Posted by Rik on March 06, 2009 at 11:10 AM CET #

Post a Comment:
  • HTML Syntax: NOT allowed
About

johnc

Search

Archives
« May 2015
SunMonTueWedThuFriSat
     
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
      
Today