Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3
Warning
titleStale Content

The content of this page is growing stale and may or may not contain relevant, useful or correct information.

Table of Contents
minLevel1

...

Code Block
titlecommand
borderStylesolid
$>cd geronimo/testsuite
$>mvn [-DinstallDirectory=/path/to/geronimoHome]

Maven will run through all the testsuites. For every testsuite, it will invoke all the testsets under it. By the time it is done, it should have created surefire xmls in every target/surefire-reports directory.

Using the -DinstallDirectory parameter will install Geronimo in one location and the same server instance will be used for each foo-testsuite. The server will be started/stopped for each of them too. The default is for every foo-testsuite to have it's own installation of the server in it's target directory. All testsets under it will use this same instance of the running server.

You may go to any single testsuite and execute 'mvn' from it to run only it's tests.

Warning
titleWarning

Currently there is a problem with running the server from inside the testsuite. This is because the testsuite build requires JDK 1.5 to execute while the server binary requires JDK 1.4 to run.
The workaround is to unzip the geronimo binary into any directory of your choice and run it.
Leave it running while executing the tests.

Viewing test results

Code Block
titlecommand
borderStylesolid
$>cd geronimo/testsuite
$>mvn site-deploy -DdeployDirectory=/path/to/websiteDbuildNumber=<a timestamp>

This will generate a website for the entire testsuite . Click on the Surefire Test Reports link to see the test resultsand deploy it to a site under geronimo.apache.org. See the summary of the results here.

Framework

The integration test is part of the regular geronimo tree and it resides under geronimo/testsuite. The child modules under this pom.xml are organized into various functional categories of the server. For eg., console-testsuite will perform tests on the console while the web-testsuites will perform tests against the web container.

...

Anchor
selenium-maven-plugin
selenium-maven-plugin

selenium-maven-plugin

http://geronimo.apache.org/maven/genesisserver/maven-plugins/mavenselenium-maven-plugin/index.html

The console-testsuite under geronimo/testsuite tests the console using Selenium (http://openqa.org).  This requires a special server process started which is provided by our selenium-maven-plugin.  

...

Anchor
maven-maven-plugin
maven-maven-plugin

maven-maven-plugin

http://geronimo.apache.org/maven/servergenesis/maven-plugins/maven-maven-plugin/index.html

This plugin invokes each of the testset-n/pom.xml in the integration-test phase of the maven lifecycle. The testcases are defined in those projects. The tests can be either junit or testng testcases. maven-surefire-plugin is configured to skip the tests during the test phase and run in the integration-test phase. surefire-report xmls are generated after the tests.

Anchor
testsuite-maven-plugin
testsuite-maven-plugin

testsuite-maven-plugin

http://geronimo.apache.org/maven/genesisserver/maven-plugins/maventestsuite-maven-plugin/index.html

Maven does not generate surefire-reports for pom packagings. foo-testsuite is a pom packaging with executions in pre-integration-test and post-integration-test phases. The results of those tests will not be captured by Maven. Also, the surefire reports from the testset-n projects should be rolled up into it's parent foo-testsuite. This is done by generate-surefire-xml goal in the testsuite-maven-plugin. Another goal, generate-surefire-report will generate the surefire-report.html from those surefire xmls. Finaly fix-menu goal will fix the menu for this html file.