Jump to: navigation, search

EclipseLink/Development/ServerPlatform/NetweaverPlatform/Testing

< EclipseLink‎ | Development‎ | ServerPlatform/NetweaverPlatform
Revision as of 05:31, 6 May 2010 by Sabine.heider.sap.com (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Testing the NetWeaver Server Platform

Testing of the NetWeaver platform is done using the JPA server test suite.

Test Results Summary

NetWeaver Version EclipseLink Version Database Weaving Tests Failures/Errors Error Details All Issues Addressed?
7.3 dev version
(LKG 2010-02-17 ID 144)
trunk (2.1 stream)
(2010-02-17)
MySQL 5.1.37 a) disabled
b) static
1492 197

AdvancedServerTestSuite (1) [1]
CriteriaServerTestSuite (195) [2]
FAServerTestSuite (1) [3]

yes
7.3 dev version
(LKG 2010-02-17 ID 144)
trunk (2.1 stream)
(2010-02-17)
Oracle 10.2.0.2.0 a) disabled
b) static
1503 208

AdvancedServerTestSuite (1) [1]
CriteriaServerTestSuite (195) [2]
FAServerTestSuite (1) [3]
StructConverterTestSuite (6) [4]
TimeStampTZJUnitTestSuite (5) [5]

yes
(without Oracle specific tests)
7.2 SP2 trunk (2.1 stream)
(2010-02-17)
Oracle 10.2.0.2.0 a) disabled
b) static
1503 208

AdvancedServerTestSuite (1) [1]
CriteriaServerTestSuite (195) [2]
FAServerTestSuite (1) [3]
StructConverterTestSuite (6) [4]
TimeStampTZJUnitTestSuite (5) [5]

yes
(without Oracle specific tests)

Details on Failing Tests

  1. 1.0 1.1 1.2 AdvancedServerTestSuite.testSetRollbackOnly: bug 297558
  2. 2.0 2.1 2.2 CriteriaServerTestSuite: should not be executed as SAP NetWeaver supports only JPA 1.0, bug 298407
  3. 3.0 3.1 3.2 FAServerTestSuite.testSetRollbackOnly: bug 297558
  4. 4.0 4.1 StructConverterTestSuite: Oracle-specific tests, no efforts have been made so far to make them pass
  5. 5.0 5.1 TimeStampTZJUnitTestSuite: Oracle-specific tests, no efforts have been made so far to make them pass

Running the JPA tests on SAP NetWeaver AS Java

  1. Follow the instructions to run the JPA tests against application servers: EclipseLink/Development/Testing/JPA#Running_JPA_tests_against_Application_Servers_Using_Ant
  2. Copy test.properties to the <user_home> directory and edit the properties as described here (step 7.): EclipseLink/Development/Testing/JPA#Configuration
    Additionally, set either one of the following properties to configure weaving:
    • server.weaving=false to disable weaving OR
    • server.weaving=static to use static weaving
  3. Copy netweaver.properties to <user_home> and edit those properties that are marked as user dependent.
  4. Depending on the Java VM used for testing, increase the memory parameters for ant's VM using the ANT_OPTS environment variable. For example, using a HotSpot VM version 1.6, successful test runs could be produced with the following setting:
    • ANT_OPTS=-Xmx512M -XX:MaxPermSize=128M
  5. Prepare the NetWeaver server for the JPA server tests
    • Use the NetWeaver Administrator to deploy the JDBC driver of the database to use for testing. Use the name configured in property netweaver.datasource.driver.deployname in file <user_home>/netweaver.property. (TODO: Link to help portal)
  6. Apply patches
    • Additional patches depending on the EclipseLink source level (see below)
  7. Make a full build of eclipselink: Go to the <trunk> directory, and execute 'ant'.
  8. Execute the tests:
    • Call 'ant server-setup' to deploy the test data source and the EclipseLink library.
    • Call 'ant server-test' to execute the server-test-lrg test suite on the application server.
    • Call 'ant server-reset' to undeploy the test data source and the EclipseLink library.

Additional Patches

The following patches have been applied depending on the EclipseLink source level:

  1. trunk (2010-02-17)
    • bug 287167 - Server Platform for SAP NetWeaver 7.1 (as the platform was still in the incubator at that point in time)
    • bug 303472 - Data source for JPA testing on NetWeaver server should use vendor_sql
    • bug 303472 - Tests testSetRollbackOnly operate on left-over data
    • Undo changes introduced by bug 295124, i.e. remove the comments in JarFileArchive.close.