Ejb3Unit 2.0 is out now

See our Roadmap for a full feature list.

Announcement: Ejb3Unit is powering jp-mobile !!!

Java Platform Mobile jp-mobile is a unified, HTML5-based user interface system for all popular mobile device platforms, built on the rock-solid GWT foundation. Its lightweight code is built with progressive enhancement, and has a flexible, easily themeable design. Jp-mobile provides the right toolset developing mobile applications with GWT and works on all kind of mobile devices that support webkit (like iPhone, iPad, iPod, Android, Blackberry, ...). Try out our Java Platform Mobile jp-mobile showcase.

Overview of Test Cases in Ejb3Unit

Ejb3Unit uses 4 different base test classes. Base entity fixture for example allows to automate tests for persistence classes. The following matrix shows all available test classes together with their use case description:

Feature matrix of Test Cases in Ejb3Unit

• Database: Ejb3Unit provides Database access for entity beans (real database or in-memory database). Note the in-memory database is automatically created
• Data Generators: Ejb3Unit uses data generators for fully automated entity bean test.
• JNDI: Ejb3Unit binds all used enitity bean to an InitialContext

  Ejb3Unit provides three different test categories for ejb3: Entity bean test, Session bean test and Mocked session bean test.

1. Entity bean test

You can create and test entity beans outside a JEE 5, EJB3 container.

• Fully automated test
  • Entity beans are randomly (or customized) written against and read from an in memory database (or against a database you may specify). This can easily be parametrizied to your own needs.
  • equals() and hashCode() methods implementations of your Entity beans are checked automatically.
  • Nullable fields are tested.
  • Possible data truncations or possible schema errors will be checked.
• Manual test
  • Of course you can add manual tests if you like
• Relations: OneToMany and ManyToOne supported
  • With Ejb3Unit it’s possible to Test this beans AND the relations (in a non transitive way!).
• Limitations:
  • ManyToMany relations, OneToOne relations and unidirectional relationships are currently not supported. For this or complex scenarios you can use the "PoJoFixture" which setups the infrastructure and gives you access to an entity manager which allows to persist your own object graph.
  • Currently only the access type 'field' is supported (annotation are declared on the field). The access type 'property' (annotation are declared on the methods) is currently not supported.

2. Session bean test

This test represents an integration test, if you like to test parts of your system in collaboration.

• The session bean under test and all referenced session beans are created.
• Also a DataSource, EntityManager and a SessionContext are injected.
• The in memory database is initialized with predefined data using comma separated value files. Each .csv file represents data for one table (using the mapping definitions form the corresponding entity bean). The testdata can also be defined directly in the testclass if this is necessary.

4. POJO test

POJO test is the alrounder for testing any POJO (Plain Old Java Object) which would be normally executed inside the container. Test complex object graphs or complex queries.

The POJO fixture provides access to the entity manager, it creates the schema for you if you are using Ejb3Unit with the in memory database and provides helper methods to persist and generate random instances of your persistent objects.

3. Mocked session bean test

A session bean class is created and for all dependencies mock objects are injected. This test allows testing of an Session bean in isolation.

• A mock object is a substitute for a concrete implementation (please see JMock for details).
• All EJB 3.0 dependency injection attributes are supported.