Comments on: Unit Testing EJBs

By: Gonzalo

Gonzalo — Thu, 28 Jun 2007 18:42:48 +0000

Hello everyone, I am trying to find any examples of EJB3Unit usage, but i can’t. Does anyone knows any place where i can get some? Because the documentation about using rc2 is not in the project site

Thanks

Gonzalo

By: loester

loester — Mon, 07 May 2007 12:01:30 +0000

Jason, thanks for sharing your gem.

To the JBoss/Hibernate folks: you can easily make your own DBUnitHelper using the following information:
http://www.censnet.it/articles/cap03.htm

By: JohnBat26

JohnBat26 — Sat, 05 May 2007 13:27:59 +0000

Hello all !
This method for testing seem good, but this while we has small model.
How I must test Session Beans, if it dependence from 5-level graph Entities ?
I must very long tediously work istead container, executing DI myself.
Or one session bean depend from 5 session beans ?

By: jason

jason — Fri, 27 Apr 2007 14:42:33 +0000

Szymono,

I’m not sure it’s “better,” really, I just like the way it works better, if that makes sense. We tried ejb3unit and had some issues with it. To be honest, that was so long ago, I can’t remember off the top of my head. I seem to remember thinking that it was awfully heavy. Having said all of that, if ejb3unit works for you and you like it, there’s no reason to switch that I can see.

By: Szymono

Szymono — Fri, 27 Apr 2007 08:48:34 +0000

Hi,

Could you tell me is above method better than ejb3unit method (http://ejb3unit.sourceforge.net)?

Best Regards,
Szymono

By: jason

jason — Mon, 02 Apr 2007 14:00:42 +0000

vicnov, thanks for the feedback. A base class for txn handling, or even use of @Before methods would likely simplify txn handling a bit, but also make things a little less flexible — just depends on your intended usage, I guess, but a good point either way. As far as Spring goes, we’ve already settled that discussion. All we were using Spring for was DI, which we get for free with EJB3 with less configuration and one less library (and its 573 dependecies). While I think Spring is great, and we still use things like the JdbcTemplate, EJB3 made more sense for us given our environment (GlassFish, JSF 1.2, etc).

By: vicnov

vicnov — Fri, 30 Mar 2007 15:59:02 +0000

Jason, thanks for this idea of testing EJBs!
Some time ago we worked at a project with EJB 3.0 beans, and our unit-tests worked with EJBs deployed to app server. This worked well but required much time for deployment…
After that I worked (and working now) with Spring – I was surprised how it is simple and fast to run unit-tests in Spring. No deployment, but your test class should be inherited from some Spring’s class which prepares environment, manage transactions etc.
Now, after your article I see that I can do almost the same with session beans in EJB 3.0.

I have just 2 ideas to propose:
1. You could create a base (parent) class which manages transactions, creates EntityManager, etc. All your test classes could inherit it.
2. If necessary, you can deal even with field-level injection using Java Reflection
3. You could use Spring itself for unit-testing. But this way you may end up by asking “Do I really need Java EE container or I could use Spring with any Servlet container?”