db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "DerbyJUnitTesting" by BryanPendleton
Date Sat, 23 May 2015 04:46:09 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The "DerbyJUnitTesting" page has been changed by BryanPendleton:
https://wiki.apache.org/db-derby/DerbyJUnitTesting?action=diff&rev1=56&rev2=57

Comment:
Add info about junit-single target

  The top-level build.xml file in the trunk codeline contains targets for running JUnit tests.
  
  || '''Target''' || '''Action''' ||
+ || `junit-single` || Run a single test suite, specified by -Dderby.junit.testclass ||
  || `junit-clean` || Remove all the `junitYYYYMMDD_hhss` output folders from previous test
runs ||
  || `junit-all` || Run all the JUnit tests. Runs the same set of tests as `suites.All` though
it is broken down into per-package `_Suite` runs (thus the results may be different in some
environments, especially when it comes to memory usage). May also run additional tests that
require special setup or need to run in their own JVM such as the tests for checking the auto-loading
of JDBC drivers. The report output is the XML format for ant's junit task. ||
  || `junitreport` || Run `junit-all` and produce an HTML report in the output folder ||
@@ -168, +169 @@

  
  The output folder is created in the current directory with the name `junitYYYYMMDD_hhss`,
e.g. `junit_20070112_0813`.
  The generated report can be viewed by opening the `index.html` file (located in the output
folder) in a web browser.
+ 
+ ==== Running a single JUnit test suite using ant in a code line ====
+ 
+ Here's an example to run a single test suite:
+ {{{
+ ant -Dderby.junit.testclass=org.apache.derbyTesting.functionTests.tests.lang.TriggerWhenClauseTest
junit-single
+ }}}
  
  === Running tests using Eclipse ===
  

Mime
View raw message