Home > Archive > Extreme Programming > November 2005 > Unit testing J2EE
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| slippymississippi@yahoo.com 2005-11-16, 6:59 pm |
|
My J2EE book suggests using JUnitEE over Cactus, claiming that setting
up Cactus test cases is so complex that it eliminates the scheduling
benefits gained from strict testing. I was planning to use Maven to
automate my build, but it appears that there is no JUnitEE plug-in for
Maven. Moreover, I am using MyEclipse, and it appears that the Cactus
plug-in for MyEclipse has been broken for over a year.
Any suggestions as to the path I should take?
| |
|
| slippymississippi wrote:
> My J2EE book suggests using JUnitEE over Cactus, claiming that setting
> up Cactus test cases is so complex that it eliminates the scheduling
> benefits gained from strict testing. I was planning to use Maven to
> automate my build, but it appears that there is no JUnitEE plug-in for
> Maven. Moreover, I am using MyEclipse, and it appears that the Cactus
> plug-in for MyEclipse has been broken for over a year.
>
>
> Any suggestions as to the path I should take?
Wham each web page flat with the 16 ton weight of HttpUnit.
Use this slow, draconian approach while you outsource research into how to
configure Cactus. I tried once, and got mired in an endless vicious cycle of
mis-configurations.
Then switch to Ruby on Rails. By any means necessary.
--
Phlip
[url]http://www.greencheese.org/Z Land[/url] <-- NOT a blog!!!
| |
| slippymississippi@yahoo.com 2005-11-17, 6:58 pm |
| > Then switch to Ruby on Rails. By any means necessary.
What is the Ruby equivalent of an EJB, and how does Ruby facilitate
performing unit tests for it?
| |
|
| slippymississippi wrote:
>
> What is the Ruby equivalent of an EJB, and how does Ruby facilitate
> performing unit tests for it?
I dunno. I'm just indirectly reporting rumors that folks experienced a 10x
productivity boost switching directly from EJB to RoR. That's not an
exaggeration; it's an indictment of Java's incredibly poor flexibility.
--
Phlip
[url]http://www.greencheese.org/Z Land[/url] <-- NOT a blog!!!
|
|
|
|
|