0 What is cdi tester, why isn't there ejb cdi unit anymore

This project is currently in the process of a complete restructuring.

Why:

The goal is to solve the initial problems that occur when you try to create a new test-class based on EJB-CDI-Unit or CDI-Unit. The main causes for these problems have been identified and should be solved with the new module

How:

• The analyze step of cdi-unit has been refined, so that it should be
  • clearer and easier to define a test-configuration
  • more deterministic in how classes are added into the configuration
• The modules are reorganized, so that
  • there are different starters for different weld main-versions
  • there are different modules if you need different extensions
    • cdi-tester is the base module
    • cdi-test-mocks supports the inclusion of @Mock annotated fields as producers
    • cdi-tester-contexts supports the extensions necessary to support Session-based CDI
    • cdi-ejb-tester contains the extensions necessary to support the extensions added by ejb-cdi-unit to cdi-unit.

Current state of development

There is a released alpha version on maven central which supports JUnit4, Weld1,Weld2,Weld3. If you want to try it, look into the junit4-examples.

Next steps

• Support of JUnit5 The alpha version meanwhile is in a state so that reworking of existing EjbCdiUnit-Tests can start. Experiences made during that will be included next.