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/Frameworks
< EclipseLink | Development | Testing
Revision as of 16:27, 3 October 2007 by Unnamed Poltroon (Talk)
Introduction
Historically, TopLink has used internal 'home-grown' testing software for both developer's unit-tests and for batch-run regression testing. More recently, 'modern' testing frameworks such as JUnit (versions 3 and 4) have been used.
Going forward for EclipseLink, there is a desired to come up with a comprehensive testing strategy that integrates into Eclipse's nightly build/test systems, allows external committers to easily add new tests and (somehow!) re-use the thousands of existing tests.
Requirements
- simple unit-testing inside Eclipse IDE environment
- support nightly test runs
- report pass/fail/ignore
- post results to EclipseLink dashboard
- compare results to 'known' good results