Versions Compared

Old Version 10

changes.mady.by.user Barrett Reed

Saved on

compared with

New Version 11

changes.mady.by.user Tim McConnell

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

If building the entire GEP, the testsuite will be the last plugin module built. As part of the normal build process, Maven will perform several step.steps as documented and shown below:

  1. Ant is is invoked from Maven to download Eclipse, the Eclipse test framework, and the Abbot SWT jars. Those artifacts are unzipped to create an Eclipse installation for the equinox launcher. The regular GEP Abbot plug-ins are downloaded into the M2 repo, which are built prior to the invocation of the testsuite, are copied into that installation. This new eclipse installation will reside in the launcher subdirectory of the testsuite.

  2. Maven is used to download the Geronimo server(s) to be tested during testsuite. Multiple servers are supported since the GEP typically supports multiple version of the Geronimo server. The servers are also installed in the launcher subdirectory.

  3. All the testsuite Eclipse plugins are built using maven and then copied into the appropriate location in the testsuite Eclipse installation. Each plugin must contain an ant script (i.e., test.xml) and be included in the testsuite.xml file Uses Ant to install a Geronimo server into a launcher directory so that it can be used during testinginvoked properly.
  4. Compile the testsuite.

  6. Use Ant to start the testsuite.Finally, maven uses ant to invoke Eclipse using the Equinox launcher. For each testsuite plugin, ant is invoked with the plugin's test.xml file.

    Image Added

This testsuite must run after the regular plug-in builds since it will test the plug-in code. The testsuite by default is not invoked. To skip the tests, use invoke it use "mvn install -Pno-itPtestsuite".

Note

The GEP testsuite simulates end-user interactions with the Eclipse GUI framework. Thus, while it is running any cursor or mouse movements will likely interfere with the successful execution of the incumbent testcases. It if is problematic or just inconvenient then the no-it testsuite profile should not be used to , which will skip the GEP testsuite. It appears that the best way to mitigate the interference running testsuite is by invoking the testsuite within an SVN viewer (although even this will not fully isolate the testsuite from user interference).

Importing the testsuite into Eclipse

...