Re: [platform-releng-dev] plugin tests for released product?

["Dean Roberts" <Dean_Roberts@xxxxxxxxxx>]

You should probably ad a line to the 2.0.2 download page.

...Dean...

Sonia Dimitrov/Ottawa/IBM@IBMCA Sent by: platform-releng-dev-admin@xxxxxxxxxxx 03/25/2003 02:48 PM Please respond to platform-releng-dev

To:        platform-releng-dev@xxxxxxxxxxx         cc:                 Subject:        Re: [platform-releng-dev] plugin tests for released product?

I have placed a 2.0.2 friendly test framework in the 2.0.2 drops directory: 

http://download.eclipse.org/downloads/drops/R-2.0.2-200211071448/eclipse-Automated-Tests-2.0.2.zip 

Instructions: 



In a nutshell, to run the tests (given java and unzip are on your path) 

1.  Extract the zip above to a directory.  This should extract to an "eclipse-testing" directory 
2.  Download the eclipse-SDK-*-2.0.2.zip into the eclipse-testing directory 
3.  Run runtests 

Please let me know if you have any problems or have any questions. 

Sonia

Erik Hennum/Oakland/IBM@IBMUS Sent by: platform-releng-dev-admin@xxxxxxxxxxx 03/20/2003 04:41 PM Please respond to platform-releng-dev

To:        platform-releng-dev@xxxxxxxxxxx        cc:                Subject:        [platform-releng-dev] plugin tests for released product?

Hi, Eclipse Release Engineers:

How can we get the download for the "JUnit Plugin Tests and Automated
Testing Framework" for a released product (2.0.2)?

It seems to be provided only for builds prior to a release.

We'd like to use the plugin tests to validate Eclipse on a variant
platform.

If another mailing list would be more appropriate, please redirect me (but
I've already tried one mailing list and the newsgroup).


Thanks,


Erik Hennum
ehennum AT us DOT ibm DOT com

_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-releng-dev

Title: Untitled Document

Automated Testing of Eclipse Builds

last updated: October 23, 2002

Description

This document describes how to run JUnit test plugins in Eclipse from the command line using Eclipse JUnit test plugins (see Appendix A for listing) and a testing framework. This method of running tests is intended for anyone who wishes to automate their testing process or reproduce the testing mechanism used in Eclipse builds by the Eclipse Release Engineering team.

Click here for a description of the testing framework, and how it can be used outside of the setup described here.

If you simply wish to write and run JUnit tests interactively from an Eclipse workbench, try one of the links below:

JUnit Support in Eclipse
Using JUnit

Requirements

1. All test machines will require a java runtime environment (version 1.3 or higher) installed and added to the path environment variable.
2. Info-ZIP UnZip version 5.41 or later installed and added to the path.
3. The Automated Test feature from an Eclipse build (http://www.eclipse.org/downloads/index.php). This contains the test framework plugin and the test plugins to run.
4. An Eclipse SDK zip file (http://www.eclipse.org/downloads/index.php) to test. Usually you will want to test a particular Eclipse build using a matching Automated Tests feature.

To run the Team CVS tests you will need extssh access to a CVS repository. The tests create a lot of junk modules and tags so you will want to keep the test repository seperate from your development repository. While it is not necessary to clean up the repository between each Team test run you will probably want to clean it up periodically.

Setup

1. Extract the eclipse-Automated-Tests-<buildid>.zip. This will create a top-level directory "eclipse-testing".
2. Place the Eclipse SDK zip file to test in the eclipse-testing directory. Do not unzip this file. (The test scripts will take care of this)
3. To run the Team CVS tests edit the test.xml script to provide connection information.

Replace the following strings in the "teamcvs" target of the test.xml file with the information described below:

• @cvs_user@ - the account used to connect to the cvs repository
• @cvs_password@- the account password
• @cvs_host@- the name of the cvs server
• @cvs_root@- the repository path

  These values are used at test time to automatically replace strings in org.eclipse.team.tests.cvs.core/repository.properties. For more information on how this file is used in the team CVS tests, click here.

Running Tests

1. cd to the eclipse-testing directory
2. Run the following script:

runtests [-os <operating system>] [-ws <windowing system>] [-arch <architecture>] [-noclean] [<testTarget>]

All parameters and targets are optional on windows systems. Just running "runtests" will run ALL tests on Windows, installing a clean Eclipse between each test target. On *nix systems, the os, ws and arch parameters must be specified.

Parameters

Parameter	Description
-os <operating system>	The OS the tests are being run on. One of: aix, hpux, linux, qnx, solaris, win32. Default win32
-ws <windowing system>	The windowing system the tests are being run on. One of: motif, gtk, photon, win32. Default win32
-arch <architecture>	The architecture the tests are being run on. One of: ppc, PA_RISC, x86, sparc. Default x86
-noclean	Run tests without installing a clean Eclipse between test targets. Default is to install a clean Eclipse between test targets.

Test Targets

Specifies which ant target to run in the main test.xml. Typically this corresponds to a test project's tests. If you do not specify a test target then the all test target is run.

all	Runs all the targets below excluding the JDT-Core components tests.
core	Runs the JUnit plugin tests for the Platform-Core component.
help	Runs the JUnit plugin tests for the Platform-Help component.
jdtdebug	Runs the JUnit plugin tests for the JDT-Debug component.
jdtui	Runs the JUnit plugin tests for the JDT-UI component.
jdtuirefactoring	Rruns additional JUnit plugin tests for the JDT-UI component.
swt	Runs the JUnit plugin tests for the Platform-SWT component. This target is executed on Windows operating systems only.
teamcore	Runs the JUnit plugin tests for the Platform-VCM component.
teamcvs	Runs additional JUnit plugin tests for the Platform-VCM component.
ui	Runs the JUnit plugin tests for the Platform-UI component.
update	Runs the JUnit plugin tests for the Platform-Update component.
genHtml	Converts xml test results in the "eclipse-testing\results" directory to html.

Appendix A - JUnit test plugins

The test plugins listed below are available from the dev.eclipse.org cvs repository and are available in binary distributable format from the Eclipse downloads page.

* indicates the plugin that contains the test.xml if component has more than one JUnit test plugin

Component	JUnit plugin tests
Jdt-Debug	org.eclipse.jdt.debug.tests
Jdt-UI	org.eclipse.jdt.ui.tests * org.eclipse.jdt.ui.tests.refactoring *
Platform-Core	org.eclipse.core.tests.harness * org.eclipse.core.tests.runtime org.eclipse.core.tests.resources
Platform-Help	org.eclipse.help.tests
Platform-SWT	org.eclipse.swt.tests
Platform-UI	org.eclipse.ui.tests
Platform-Update	org.eclipse.update.tests.core
Platform-VCM(Team)	org.eclipse.team.tests.cvs.core org.eclipse.team.tests.core

 

Appendix B- Supported os, ws, and arch value combinations

The following table contains the values that can be used with the -os, -ws, and -arch switches.

Operating System (os)	Windowing System (ws)	Architecture (arch)
aix	motif	ppc
hpux	motif	PA_RISC
linux	gtk	x86
linux	motif	x86
qnx	photon	x86
solaris	motif	sparc
win32	win32	x86