Versions Compared

Old Version 12

changes.mady.by.user Craig Russell

Saved on

compared with

New Version 13

changes.mady.by.user Michael Dick

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Add -DfailIfNoTests=false and note how you can set it in settings.xml

...

Once you have downloaded and built OpenJPA (see Building), you can run individual tests using the "test" goal to maven. For example:

Code Block
mvn test -DfailIfNoTests=false -Dtest=TestPersistence
Note

By default Maven will fail if there are no testcases found in any module you build. The examples solve this by specifying -DfailIfNoTests=false but you can also change your personal default by adding the following to ${user.home}/.m2/settings.xml :

Code Block
xml
xml

        <profile>
            <id>enable-no-tests</id>
            <activation>
                <activeByDefault>true</activeByDefault>
            </activation>
            <properties>
                <failIfNoTests>false</failIfNoTests>
            </properties>
        </profile>

To get more debugging information (e.g., to see the SQL that is being executed against the database), you can enable trace-level logging from the command line using the "openjpa.Log" system property. For example:

Code Block
$ mvn test -DfailIfNoTests=false -Dtest=TestPersistence -Dopenjpa.Log=DefaultLevel=TRACE

[INFO] Scanning for projects...
[INFO] Reactor build order: 
...
690  test  TRACE  [main] openjpa.jdbc.SQL - <t 4261185, conn 3061987> executing prepstmnt 12659709 
   INSERT INTO AllFieldTypes (id, arrayOfStrings, booleanField, byteField, charField, dateField, 
   doubleField, floatField, intField, longField, shortField, stringField) 
   VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [params=(long) 601, (null) null, (int) 0, (byte) 0, 
   (int) 0, (null) null, (double) 0.0, (float) 0.0, (int) 0, (long) 0, (short) 0, (null) null]
701  test  TRACE  [main] openjpa.jdbc.SQL - <t 4261185, conn 3061987> [11 ms] spent
701  test  TRACE  [main] openjpa.jdbc.JDBC - <t 4261185, conn 3061987> [0 ms] commit
702  test  TRACE  [main] openjpa.jdbc.JDBC - <t 4261185, conn 0> [0 ms] close
...
$

...

By default, OpenJPA uses the Derby database for testing. The openjpa-persistence-jdbc/pom.xml POM declares various pre-defined databases against which tests can be executed. For example, to test against the stand-alone HSQLDB database, you can run with the "test-hsqldb" profile:

Code Block
mvn test -DfailIfNoTests=false -Dtest=TestPersistence -Ptest-hsqldb

For databases that are not in the pre-defined list, you can manually specify connection parameters to use for testing under the "test-custom" profile. You will need to manually provide the driver class and specify all of the connection parameters. For example, to test against Oracle, you might run:

Code Block
mvn test -DfailIfNoTests=false -Dtest=TestPersistence -Ptest-custom \
  -Dopenjpa.custom.driverjar=$(pwd)/drivers/jdbc-oracle-10_2_0_1_0.jar \
  -Dopenjpa.custom.driverclass=oracle.jdbc.driver.OracleDriver \
  -Dopenjpa.custom.url=jdbc:oracle:thin:@HOST:PORT:DBNAME \
  -Dopenjpa.custom.username=USERNAME \
  -Dopenjpa.custom.password=PASSWORD

...

This profile can then be executed by running:

Code Block
mvn test -DfailIfNoTests=false -Dtest=TestPersistence -Ptest-custom,test-oracle