Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
EclipseLink/Development/Testing/StrawManProposal
< EclipseLink | Development | Testing
From the EclipseLink DevMeeting 071017, create a straw-man proposal for a new consolidated testing framework
New Testing Framework
- based on JUnit4 - Why?
- JUnit3 is at end-of-life
- Eclipse IDE has built-in support for JUnit4 tests
- while various testing frameworks have been extended, JUnit4 is extensible by design
Looked at requirements from MOXy/SDO, JPA, this is what we've got so far ...
Hollywood Principle
Don't call us, we'll call you The Hollywood Principle
The existing tests have code that is strongly coupled between setting up resources and the tests. Instead, the NTF injects the resource into a tagged variable. Setting up the context for the resource is a done in a separate class with its own requirements for inheritance/composition/aggregation.