Difference between revisions of "EclipseLink/Development/DatabasePlatform/SymfowarePlatform/TestResults2.3.2"

Latest revision as of 01:12, 3 February 2012

The following are the test results for SymfowarePlatform.

Test Results(February 2/2012)

EclipseLink 2.3.2 and Symfoware Server v 10.0.0

EclipseLink 2.3.2
DB: Symfoware Server V10.0.0
JDBC driver: Symfoware JDBC 4.0 driver (RDB2_TCP)
JDK: Sun JDK6(jdk1.6.0_26)
OS: Windows 7(64bit)

Test Name	Tests	Failures	Errors
Core SRG	690	0	0
JPA SRG	228	0	0
Core LRG	7849	0	0
JPA LRG	2714	0	0
Server LRG (GlassFish v3)	-	-	-

Testing durations (SRG tests are included in LRG tests)

Core LRG: 33min.
JPA LRG: 13min.

EclipseLink 2.3.2 and Symfoware Server v 10.1.0

EclipseLink 2.3.2(r10461)
DB: Symfoware Server V10.1.0
JDBC driver: Symfoware JDBC 4.0 driver (RDB2_TCP)
JDK: Sun JDK6(jdk1.6.0_26)
OS: Windows 7(64bit)

Test Name	Tests	Failures	Errors
Core SRG	690	0	0
JPA SRG	228	0	0
Core LRG	7849	0	0
JPA LRG	2714	0	0
Server LRG (GlassFish v3)	-	-	-

Testing durations (SRG tests are included in LRG tests)

Core LRG: 26min.
JPA LRG: 11min.

Additional Configuration

Core LRG tests are run with ANT_OPTS=-Xmx3000m and max.heap.memory=3500m to prevent OOM errors while generating JUnit report (not carefully tuned so might work with less).
JPA LRG tests are run with max.heap.memory=1300m to prevent OOM errors while generating JUnit report (not carefully tuned so might work with less).

The Details of Test Suites

Test Suite	Ant Target	Test Location	Test Class	Wiki
Core SRG	test-srg	foundation/eclipselink.core.test	org.eclipse.persistence.testing.tests.SRGTestModel	EclipseLink/Development/Testing/foundation
Core LRG	test-lrg	foundation/eclipselink.core.test	org.eclipse.persistence.testing.tests.TestRunModel	EclipseLink/Development/Testing/foundation
JPA SRG	test-srg	jpa/eclipselink.jpa.test	org.eclipse.persistence.testing.tests.jpa.advanced.EntityManagerJUnitTestSuite	EclipseLink/Development/Testing/JPA
JPA LRG	test-lrg	jpa/eclipselink.jpa.test	org.eclipse.persistence.testing.tests.jpa.AllCMP3TestRunModel org.eclipse.persistence.testing.tests.jpa.xml.EntityMappingsJUnitTestSuite	EclipseLink/Development/Testing/JPA

For JPA LRG, build.xml of jpa/eclipselink.jpa.test was edited to avoid table locking issues on Symfoware.
Sleep 1 minute was inserted between AllCMP3TestRunModel and EntityMappingsJUnitTestSuite.

Test Configuration Notes

Install Symfoware Server Client on the machine that EclipseLink is installed on.
For the JPA and Foundation Test Suites, update the respective test.properties files with your JDBC connection settings.

For example:

jdbc.driver.jar=c:/SFWCLNT/JDBC/fjjdbc/lib/fjsymjdbc4.jar
db.driver=com.fujitsu.symfoware.jdbc.SYMDriver
db.url=jdbc:symford://symfodb:56005/TESTDB;codeselect=OS
db.user=symfouser
db.pwd=symfopwd
db.platform=org.eclipse.persistence.platform.database.SymfowarePlatform
db.platform.jvmargs=-Declipselink.test.toggle-fast-table-creator=true

Note the following:

jdbc.driver.jar: Should include the path to the JDBC driver libraries. Refer to the Symfoware Server Client manual for details, and use the correct driver for your JDK version.; Should include the path to the Symfoware Platform class.
db.platform: The platform name is org.eclipse.persistence.platform.database.SymfowarePlatform.
db.url: 'codeselect=OS' is added to prevent Japanese messages from the database from being completely garbled when received on the client (required because I use a Japanese DB on Linux and the client is on English Windows).
db.platform.jvmargs: This JVM argument is read by EclipseLink's test suite. It will prevent tests that reuse tables to try to drop and recreate tables (as this can lead to table lock errors if the original connection is still open). Instead, it will force them to just delete the rows in the tables.

Also, include the JDBC driver native libraries in your PATH (Windows) or LD_LIBRARY_PATH (Unix).
If you face the lack of database space while executing tests, configure DEFAULT_TABLE_SIZE and DEFAULT_INDEX_SIZE.