Hi TomEE has much more solution but EJBContainer is a nice compromise to start. Arquillian is the more powerful but also the most hard to setup and understand. For simple apps ApplicationComposerRule is awesome cause allows app description reusability and split config and app in several classes (makes mocking easier). It also has some mockito integration. Le 21 oct. 2014 21:59, "Lars-Fredrik Smedberg" <itsme...@gmail.com> a écrit :
> Hi! > > Previously I've used CDI-Unit to unit test CDI-based applications. With > CDI-Unit I have been able to create tests for e.g. CDI managed beans, CDI > interceptors and CDI extensions. > > I see that the TomEE examples uses javax.ejb.embeddable.EJBContainer to > test EJBs. Is that my best choice or should I move on to Arquillian or > something else? Can anyone maybe explain the benefits/drawbacks of the two? > > The application/code I need to test combines CDI managed beans and EJBs as > well as JAX-WS (CXF) WebServices. Some features I would like to test / mock > in the tests are: > > Witch one would be possible/rather easy to create tests for > > - @Resource to inject DataSource > - @Inject of CDI managed beans / EJBs > - CDI- and EJB-interceptors > - CDI-extensions (This I can still do with CDI-Unit if needed) > - TimerEJBs > - MDBs > - Transactions > - Concurreny management > - Async methods > > > > > -- > Med vänlig hälsning / Best regards > > Lars-Fredrik Smedberg > > STATEMENT OF CONFIDENTIALITY: > The information contained in this electronic message and any > attachments to this message are intended for the exclusive use of the > address(es) and may contain confidential or privileged information. If > you are not the intended recipient, please notify Lars-Fredrik Smedberg > immediately at itsme...@gmail.com, and destroy all copies of this > message and any attachments. >
