• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

EJB 2.x Unit Testing/sort of JUnit line question? -compare JTest,JUnitEE,ApacheCactus

 
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi testers,
we have an application implemented via EJB 2 Session Beans (no Entity Beans) but only Hibernate for Persistence.

I have to create a framework for unit testing later on maybe functional testing.

As I google, people are using JTest, JUnitEE, J2EEUnit aka (Apache Cactus new name)
what are the differences- similarities that make sense?

How about using such a class as base class?
I mean, of yourse I will customize it, extend say TestCase of JUnit etc...
But is it just fine?
What features do all the jars of Cactus, JUnitEE deliver to me? Why should I make the application more complicated? say, create a new WAR containing test classes, definitions, deploy in EAR etc...

What is missing in the following test class, that makes a huge difference to justify usage of Cactus, JUnitEE?





[ December 04, 2008: Message edited by: rusdem e zal� ]

[ December 04, 2008: Message edited by: rusdem e zal� ]
[ December 04, 2008: Message edited by: rusdem e zal� ]
reply
    Bookmark Topic Watch Topic
  • New Topic