Preloader image

OpenEJB itests

The OpenEJB itests module is a framework to create EJB test cases that are designed according to the JUnit rules, i.e. they all have setUp, tests and tearDown methods. Since it’s JUnit-based, you can do whatever you could do in JUnit.

This page describes the steps to create EJB test cases.

How itests work

The itests module lives in OpenEJB’s repository in the modules\itests directory. Setting up the test environment to execute the itests is based on (maven-itest-plugin-1.0 plugin ).

Take a look at maven.xml in modules\itests directory. There you’ll see that the default goal is ejb:install, which in turn executes itest. When the EJBs (todo: describe it a bit more) are done, the itest:setup goal is executed, which starts the real game. First, org/openejb/Security configuration is started. Once it’s done, openejb-itests-xxx.jar is deployed, which is org/openejb/Itests configuration to be started, afterwards. When the configurations are deployed and started, the maven-itest-plugin executes junit (see Ant JUnit task documentation and of the itests module). The file configures which itests are run and some other stuff.

The first itest test case is org.openejb.test.entity.cmp.CmpTestSuite. Consult this for more information. Then the others defined in maven.itest.includes property are executed.

The order in which the itests are executed is important, so the first order is set up via the maven.itest.includes property, then the test suites add their tests in some order, and finally the method names in the test classes put yet another order. So, be careful what name your test method name will become. It may influence the order.

Some EJBs access database resources. It’s even more important for CMPs. The itests module uses the database as defined in the openejb.test.database property. It’s currently defined in the file of the module. You can change its value to whatever you wish using the Maven property setting approaches (-D on the command line,, in your home directory or the project you work in).

So, the last important information is how the junit tests access the server resources - EJBs. It’s done via executing session beans that in turn get at the test EJBs, mostly CMPs. It’s also possible that the CMP itests will be accessed directly without having to pass on the call through a session bean.

If itests are part of a larger project structure you can disable executing it using the maven.itest.skip property. Set it to true and Maven won’t run the itests.

Simple CMP 2.1 itest

Database setup

The itests default database is Derby. The class - org.openejb.test.DerbyTestDatabase - is instantiated upon executing org.openejb.testTestManager.getDatabase() in each test case’s setUp() method. Remember, you can define any other database using the openejb.test.database property or do initialization of your own database choice in the setUp() method.

The current implementation of database initialization is based on two DerbyTestDatabse methods: createCMP2Model() and dropCMP2Model() that create and drop database structure, accordingly.

CMP 2.1 deployment

{info:title=Information} Unless specified, all directories are relative to modules/itests directory and commands are executed in it. {info}

A Maven project can produce one build artefact. It’s very important to keep in mind whenever your tests are to be based on a EJB that’s not built by default. The default EJBs are defined in modules/itests/src/ejb/META-INF/ejb-jar.xml. The corresponding deployment plan - the openejb-jar.xml file is in modules/itests/src/ejb/META-INF/openejb-jar.xml.

If you want to test your own EJB, you need to build it yourself, i.e. describe the build and deployment in modules/itests/maven.xml in the pregoal of itest:setup.

In the following example, Ant’s jar builds openejb-cmp2-petstore.jar file, which in turn is distributed and started in Geronimo. The id attribute of deploy:start is as specified in the module’s deployment plan. See Geronimo Deployment for more information about Geronimo deployment plans.

<ant:jar destfile="${basedir}/target/openejb-cmp2-petstore.jar">
  <fileset dir="${basedir}/target/classes">
    <include name="**/cmp2/petstore/*.class"/>
    <include name="**/TestFailureException.class"/>
  <metainf dir="${basedir}/src/cmp2/petstore" includes="*.xml"/>


When EJB classes, deployment descriptor and plan, maven.xml are all set up, it’s time to execute your tests. In order to run itests you will run Maven in modules/itests directory.

$ maven

It’s also possible to override project properties and run only some test cases.

$ maven -Dmaven.itest.includes=**/

When a failure occurs, you should take a look at the result file of the failed test suite in target/itest-reports, e.g.

$ maven -Dmaven.itest.includes=**/ -o
 [junit]  Tests run: 113, Failures: 1, Errors: 0, Time elapsed: 22,132 sec
 [junit]  [ERROR]  TEST org.openejb.test.entity.cmp2.Cmp2TestSuite FAILED
File...... C:\Documents and Settings\root\.maven\cache\maven-itest-plugin-1.0\plugin.jelly
Element... fail
Line...... 166
Column.... 64
There were test failures.
Total time: 2 minutes 3 seconds
Finished at: Sun Jul 17 17:48:36 CEST 2005

$ more target/itest-reports/TEST-org.openejb.test.entity.cmp2.Cmp2TestSuite.txt
Testsuite: org.openejb.test.entity.cmp2.Cmp2TestSuite
Tests run: 113, Failures: 1, Errors: 0, Time elapsed: 22,132 sec

Testcase: PetstoreTests.create: FAILED
Received Exception class java.lang.NullPointerException : null
junit.framework.AssertionFailedError: Received Exception class java.lang.NullPointerException : null
	at org.openejb.test.entity.cmp2.PetstoreTests.test01_create(
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
	at org.openejb.test.NumberedTestCase.runTestMethod(
	at org.openejb.test.NumberedTestCase$3.protect(

Complete execution log is in target/openejb/var/log/openejb.log of the itests module.

Running the Tests in Eclipse.

The steps for running the iTests inside of Eclipse are given below. They are

1) For Local Interface Tests, the class to be run is org.apache.openejb.iTest. 2) For Remote Interface Tests, the class to be run is org.apache.openejb.RemoteiTest.

In both the cases you need to give '-Dopenejb.home=target/test-classes/' as a vm argument for the tests to run.