Skip to main content

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.

Jump to: navigation, search

EclipseLink/DesignDocs/290528

290528: Design Specification: JPA Test Suite Submission

ER 290528

EclipseLink IPLog 20091022 entry

Document History

Date Author Version Description & Notes
20091021 mobrien 1.0 - Document started during checkin of unmodified submission of the test suite attachment in ER 290528 as SVN Rev# 5626

Project overview

  • This document details the issues and changes that occured during the submission of the new JPA test suite as part of enhancement # ER 290528 in patch 150290
  • Work done so far has been to checkin the unmodified attached expanded contribution zip 'as-is' and update the IP Log
  • >See EclipseLink 2.0 IP zila entry in the section below pertaining to the future testing runtime jars automatically built by ant but not checked into SVN

http://wiki.eclipse.org/EclipseLink/IPLog#EclipseLink_2.0

  • Additional work will be required to implement the changes required for the 3 phases below.

Concepts

Requirements

  • Refer to the following report as a start to this phased integration of this JPA test suite.

Phase 1: Integrate project into Eclipse IDE

  • This phase involves the following details
    • .project and .classpath references
    • JPA.launch target adjustment to include everything currently in the custom SAPJPATest.launch

Phase 2: Integrate project into trunk Ant build (developers only)

  • This phase involves the following details
    • build.properties build targets configuration
    • test.properties test targets configuration
    • build.xml adjustment if required

Phase 3: Integrate project into nightly Ant build

  • This phase involves the following details
    • build.properties build targets configuration
    • test.properties test targets configuration
    • build.xml adjustment if required
    • build server changes (made by 1 of 3 build engineers)

Design Constraints

Design / Functionality

Testing

API

GUI

Config files

Documentation

Open Issues

Issue # Owner Description / Notes

Decisions

Issue # Description / Notes Decision

References

JUnit 4.5 requirement for BlockJUnit4ClassRunner

Future Considerations

Back to the top