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.
Difference between revisions of "EclipseLink/Development/Testing/StrawManProposal"
< EclipseLink | Development | Testing
(→New Testing Framework) |
(→New Testing Framework) |
||
| Line 1: | Line 1: | ||
''From the EclipseLink DevMeeting 071017, create a straw-man proposal for a new consolidated testing framework'' | ''From the EclipseLink DevMeeting 071017, create a straw-man proposal for a new consolidated testing framework'' | ||
| − | + | = New Testing Framework = | |
* based on JUnit4 - Why? | * based on JUnit4 - Why? | ||
** JUnit3 is at end-of-life | ** JUnit3 is at end-of-life | ||
| Line 8: | Line 8: | ||
Looked at requirements from MOXy/SDO, JPA, this is what we've got so far ... | 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'' | ||
Revision as of 12:10, 22 November 2007
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