directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From seelm...@apache.org
Subject svn commit: r663773 [6/6] - in /directory/sandbox/seelmann/testingframework/test-integration-ui: ./ META-INF/ resources/test-plugins/ resources/test-plugins/org.apache.ant_1.7.0.v200706080842/ resources/test-plugins/org.apache.ant_1.7.0.v200706080842/M...
Date Thu, 05 Jun 2008 23:05:32 GMT
Added: directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.eclipse.test_3.2.0/library.xml
URL: http://svn.apache.org/viewvc/directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.eclipse.test_3.2.0/library.xml?rev=663773&view=auto
==============================================================================
--- directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.eclipse.test_3.2.0/library.xml (added)
+++ directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.eclipse.test_3.2.0/library.xml Thu Jun  5 16:05:29 2008
@@ -0,0 +1,169 @@
+<?xml version="1.0"?>
+<project name="Library" default="usage" basedir=".">
+
+	<target name="usage">
+		<echo message="Please refer to the testframework.html in org.eclipse.test for instructions on usage." />
+	</target>
+
+	<target name="init">
+		<!-- 
+			Parameters:
+				(Mandatory)
+				data-dir		- the directory for Eclipse to write its data
+				plugin-name		- the name of the plugin to test
+				classname		- the name of the test class
+				
+				(Optional - overrides defaults set in script)
+				vmargs			- a string containing arguments to pass to the VM.
+				extraVMargs		- allows separate setting of VM args from separate caller.
+				timeout			- overrides default test timeout value (in milliseconds).
+				test-output		- overrides default output file produced from test run.
+				plugin-path		- path to root of plug-in
+				useEclipseExe	- property setting forces test to launch via eclipse executable.
+				junit-report-output - output directory for junit reports produced for specified classname.
+		-->
+		
+	  	<tstamp>
+	        <format property="TIMENOW" pattern="HHmmssSSSS"/>
+	    </tstamp>
+		<!--property setting useEclipseExe launches tests using the eclipse executable-->
+		<condition property="launchTarget" value="eclipse-test">
+			<isset property="useEclipseExe" />
+		</condition>
+		<!--default launch target for launching tests-->
+		<property name="launchTarget" value="java-test" />
+		<property name="formatter" value="org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter"/>
+	    
+		<!--default heap sizes when running performance tests-->
+	    <condition property="vmargs" value=" -Xms256M -Xmx256M">
+			<equals arg1="${test.target}" arg2="performance" />
+	    </condition>
+		<property name="extraVMargs" value=""/>
+		<property name="plugin-path" value="" />
+		<property name="timeout" value="7200000" />
+		<property name="test-output" value="${eclipse-home}/${classname}.xml" />
+		<property name="junit-report-output" value="${eclipse-home}/results" />
+		<mkdir dir="${junit-report-output}"/>
+	</target>
+	
+	<target name="core-test" description="Eclipse application used to launch HEADLESS plugin tests." depends="init">
+		<antcall target="${launchTarget}">
+			<param name="application" value="org.eclipse.test.coretestapplication"/>
+		</antcall>
+	</target>
+	
+	<target name="ui-test" description="Eclipse application used to launch UI plugin tests." depends="init">
+		<antcall target="${launchTarget}">
+			<param name="application" value="org.eclipse.test.uitestapplication"/>
+		</antcall>
+	</target>
+
+	<target name="java-test">
+		<!--default vm args-->
+		<property name="vmargs" value=" -Xms40m -Xmx256m"/>
+	  	
+	  	<!--set default jvm to use for testing-->
+	   	<property name="jvm" value="${java.home}/bin/java" />
+  	
+		<echo message="Running ${classname}. Result file: ${junit-report-output}/${classname}.xml."/>
+
+		<java fork="true" dir="." timeout="${timeout}" jvm="${jvm}" logError="true"
+			classname="org.eclipse.core.launcher.Main" output="${junit-report-output}/${classname}.txt">
+	        <classpath>
+	    		<fileset dir="${eclipse-home}/plugins">
+	            	<include name="org.eclipse.equinox.launcher_*.jar"/>
+	          	</fileset>
+	        </classpath>
+		    <arg line="-application ${application}"/>
+		    <arg line="-data ${data-dir}"/>
+		    <arg line="formatter=${formatter},${test-output}"/>
+		    <arg line="-testPluginName ${plugin-name}"/>
+		    <arg line="-className ${classname}"/>
+		    <arg line="-os ${os}"/>
+		    <arg line="-ws ${ws}"/>
+		    <arg line="-arch ${arch}"/>
+		    <arg line="-consolelog"/>
+		    <jvmarg line="${vmargs} ${extraVMargs}"/>
+		    <sysproperty key="PLUGIN_PATH" value="${plugin-path}"/> 
+		</java>
+		<antcall target="collect-results" />
+	</target>
+	
+	<target name="eclipse-test" description="Runs the specified classname as a plug-in test.">		
+		<property name="vmargs" value="-Xms256m -Xmx512m"/>
+		
+		<!--use -consolelog if launching a headless test-->
+		<condition property="consolelog" value="-consolelog">
+			<equals arg1="${application}" arg2="org.eclipse.test.coretestapplication"/>
+		</condition>
+		<property name="consolelog" value="" />
+
+		<!--
+			vm selection priority:
+			1.  user-specified java executable via outer Ant property setting of "jvm".
+			2.  java executable on path.
+		-->
+		<condition property="test-vm" value="-vm ${jvm}">
+			<isset property="jvm" />
+		</condition>
+		<property name="test-vm" value="" />
+		
+		<!--ensure executable has execute permission-->
+		<chmod file="${eclipse-home}/eclipse" perm="ugo+rx"/>
+		
+		
+		<echo message="Running ${classname}. Result file: ${junit-report-output}/${classname}.xml."/>
+
+		<exec executable="${eclipse-home}/eclipse" dir="${eclipse-home}" timeout="${timeout}" logError="true" failonerror="false" output="${junit-report-output}/${classname}.txt">
+			<arg line="-data ${data-dir}"/>
+			<arg line="${test-vm}"/>
+			<arg line="-application ${application}"/>
+			<arg line="formatter=${formatter},${test-output}"/>
+			<arg line="-testPluginName ${plugin-name}"/>
+			<arg line="-className ${classname}"/>
+			<arg line="-nosplash"/>
+			<arg line="-suppressErrors"/>
+			<arg line="${consolelog}"/>
+			<arg line="-vmargs ${vmargs} ${extraVMargs} -DPLUGIN_PATH=${plugin-path}"/>
+		</exec>
+		<antcall target="collect-results" />
+	</target>
+	
+	<target name="collect-results">
+		<dirname property="output-dir" file="${test-output}"/>
+		<basename property="output-file-name" file="${test-output}"/>
+		<junitreport todir="${junit-report-output}" tofile="${classname}.xml">
+			<fileset dir="${output-dir}">
+				<include name="${output-file-name}"/>
+			</fileset>
+		</junitreport>
+
+		<style style="${eclipse-home}/plugins/org.eclipse.test/JUNIT.XSL"
+			basedir="${junit-report-output}"
+			includes="${classname}.result.xml"
+			destdir="${junit-report-output}" />
+
+		<!--save .log content and *.log content from configuration directory-->
+		<concat destfile="${junit-report-output}/${classname}.log">
+			<fileset dir="${eclipse-home}" includes="${data-dir}/.metadata/*.log"/>
+			<fileset dir="${eclipse-home}" includes="configuration/*.log"/>
+		</concat>
+	</target>
+
+	<target name="collect">
+		<!--
+			This target can be used to aggragate test runs from multiple test suites into a single report.
+		
+			Parameters to this target:
+			includes		- the names of the files to include
+			output-file		- the name of the output file to produce
+		-->
+		<junitreport todir="." tofile="${output-file}">
+			<fileset dir=".">
+				<include name="${includes}"/>
+			</fileset>
+		</junitreport>
+	</target>
+
+</project>
+

Added: directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.eclipse.test_3.2.0/plugin.properties
URL: http://svn.apache.org/viewvc/directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.eclipse.test_3.2.0/plugin.properties?rev=663773&view=auto
==============================================================================
--- directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.eclipse.test_3.2.0/plugin.properties (added)
+++ directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.eclipse.test_3.2.0/plugin.properties Thu Jun  5 16:05:29 2008
@@ -0,0 +1,12 @@
+###############################################################################
+# Copyright (c) 2000, 2005 IBM Corporation and others.
+# All rights reserved. This program and the accompanying materials
+# are made available under the terms of the Eclipse Public License v1.0
+# which accompanies this distribution, and is available at
+# http://www.eclipse.org/legal/epl-v10.html
+#
+# Contributors:
+#     IBM Corporation - initial API and implementation
+###############################################################################
+pluginName = Eclipse Automated Testing
+providerName = Eclipse.org

Added: directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.eclipse.test_3.2.0/plugin.xml
URL: http://svn.apache.org/viewvc/directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.eclipse.test_3.2.0/plugin.xml?rev=663773&view=auto
==============================================================================
--- directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.eclipse.test_3.2.0/plugin.xml (added)
+++ directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.eclipse.test_3.2.0/plugin.xml Thu Jun  5 16:05:29 2008
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?eclipse version="3.0"?>
+<plugin>
+     <extension
+         id="coretestapplication"
+         point="org.eclipse.core.runtime.applications">
+      <application>
+         <run
+               class="org.eclipse.test.CoreTestApplication">
+         </run>
+      </application>
+   </extension>
+   <extension
+         id="uitestapplication"
+         point="org.eclipse.core.runtime.applications">
+      <application>
+         <run
+               class="org.eclipse.test.UITestApplication">
+            <parameter
+                  name="productInfo"
+                  value="product.ini">
+            </parameter>
+         </run>
+      </application>
+   </extension>
+
+</plugin>

Added: directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.eclipse.test_3.2.0/testframework.html
URL: http://svn.apache.org/viewvc/directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.eclipse.test_3.2.0/testframework.html?rev=663773&view=auto
==============================================================================
--- directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.eclipse.test_3.2.0/testframework.html (added)
+++ directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.eclipse.test_3.2.0/testframework.html Thu Jun  5 16:05:29 2008
@@ -0,0 +1,277 @@
+<html>
+<head>
+<title>Eclipse Testing Instructions</title>
+</head>
+
+<body>
+<h1>The Eclipse Test Framework</h1><p>Last Modified: June 13, 2007</p><p><font size="+1"><br>
+  Introduction</font></p><p>The testing framework is comprised of the org.eclipse.test plugin and the org.eclipse.ant.optional.junit 
+  fragment. </p><p>These two projects are available from the dev.eclipse.org repository and are 
+  included in the 	eclipse-test-framework-&lt;buildId&gt;.zip from the eclipse.org 
+  downloads page.</p><p><font size="+1">Building and Installation</font></p><p>Since the org.eclipse.test plugin is stored in the repository in source-code 
+  form, it needs to be compiled before it can be used. The org.eclipse.ant.optional.junit 
+  fragment does not contain any source and can be used as is from the repository.</p><ol>
+  <li>Turn of automatic builds. Window->Preferences->Workbench and uncheck "Perform 
+    build automatically on resource modification"</li><li>Load org.eclipse.test into your workspace.</li><li>Right-click on the org.eclipse.test project in either the Navigator or Packages 
+    view. Select 'Rebuild Project' from the context menu. This will compile the 
+    entire org.eclipse.test plugin.</li><li>Finally, copy the org.eclipse.test plugin into your target Eclipse.</li>
+    <li>The org.eclipse.ant.optional.junit fragment only needs to be present in 
+    the environment of the Eclipse that is overseeing the test process. If you 
+    are running the test script from within the Workbench, this means that the 
+    fragments need to be present withinn your development Eclipse. If you are 
+    running the tests from the command line, then the fragments will need to be 
+    present in your target Eclipse.</li></ol>
+ <p><font size="+1">Setup</font></p>
+ <p>Follow the steps given above to build and install all of the neccessary plugins 
+  and fragments. Please note that the current version of the test framework is 
+  not compatible with the PDE notion of self-hosting. If you want to run the tests, 
+  you will need to setup a full target Eclipse so that the testing framework can 
+  detect everything that is needed.</p>
+<p>If you are writing tests for one or more Eclipse plugins, then you should
+create a separate plugin for tests. The test plugin will contain all of the
+tests that will be run on your development plugins, as well as defining how
+those tests get run.</p>
+
+<p>If you are not writing tests for an Eclipse plugin, then you should look into 
+  using JUnit on its own to test your work. JUnit is designed for testing Java 
+  code, and by default has no knowledge of Eclipse. There are separate mechanisms 
+  for using JUnit on Java code in Eclipse. See the documentation provided here:</p>
+<p> <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/plugins/org.eclipse.jdt.junit/index.html">
+JUnit Support in Eclipse</a><br>
+  	<a href="http://dev.eclipse.org:8080/help/content/help:/org.eclipse.jdt.doc.user/tasks/tasks-207.htm?resultof=%6a%75%6e%69%74%20&toc=%2Forg.eclipse.jdt.doc.user%2Ftoc.xml">
+  	Using JUnit</a></p>
+  	
+  	<p>Once a test plugin has been created, you must then create an Ant script that 
+  will run all of the tests. Create a file called 'test.xml' in the root of your plug-in or bundle.
+  This is an Ant file that defines how each test is going to be run. The 'test.xml' 
+  file is like a DOS batch file that scripts the entire testing process. Typically, 
+  the 'test.xml' file will contain targets for setting up the test run, executing 
+  the tests, cleaning up afterwards, and running the entire process.</p>
+  
+  <p><font size="+1">Converting existing Test Suites</font></p>
+  
+  <p>If you are converting an existing set of tests to use the new framework, the
+actual tests that have been written should not need much change.</p>
+  <p>If you have tests in multiple plugins, move these to a single test plug-in for your component.</p>
+  
+  <p>Make sure that the tests are defined in a plug-in. This is probably the most 
+  common cause of confusion in the entire test process. Your tests need to be 
+  in a plug-in so that Eclipse can find them when it tries to load them.</p>
+  
+  <p><font size="+1">Creating new Test Suites</font></p>
+  
+  <p>Creating new JUnit tests for an Eclipse plugin should be no more difficult 
+  than writing standard JUnit tests. Since the framework allows tests to be run 
+  inside of a working Eclipse, any tests that you write have available to them 
+  any of the methods supplied by the Eclipse platform, provided that you add the 
+  appropriate dependencies to your tests' manifest.</p>
+  
+  <p><font size="+1">Performance Issues</font></p>
+  <p>You should keep in mind the number of times that Eclipse needs to be
+started. Launching Eclipse has a substantial cost in terms of runtime. To
+minimize the number of times the platform is started, you should consider
+writing a TestSuite called AllTests for each of your test plugins. AllTests
+should invoke each of the tests that you want to run for a particular plugin.
+The 'test.xml' file can then run the AllTests class, which will run all of your
+tests, but the platform will only ever be started once for each of your test
+plugins.</p><p>Note: Sometimes tests involve shutting down, restarting, and testing the state 
+  of metadata that was written to disk. These session tests will require Eclipse 
+  to be launched several times in sequence, which will increase the runtime of 
+  your tests. This cannot be avoided.</p><p>&nbsp;</p>
+  
+  <p><font size="+1">Running the Test Suite from the UI</font></p><p>Right click on the test.xml file and select 'Run Ant...' from the pull-down 
+  menu. The Running Ant dialog box pops up. From the list of targets, select the 
+  one that runs all of your tests. If you are using the example file provided 
+  below, this target is called 'Run', and will be selected by default. Hit the 
+  'Finish' button to start the test process.</p>
+  
+  <p><font size="+1">Running the Test Suite from the command line</font></p>
+  <p>When the test suites are invoked automatically, they are run from command
+line. From the ${eclipse-home} directory, the command to use is:</p>
+<code>java -jar plugins\org.eclipse.equinox.launcher_&lt;version&gt;.jar -application org.eclipse.ant.core.antRunner -buildfile ${test-plugin-path}\test.xml
+-Declipse-home=${eclipse-home} -Dos=&lt;operating system&gt; -Dws=&lt;windowing system&gt; -Darch=&lt;architecture&gt;</code>
+
+<p>Individual tests can also be invoked directly. From the ${eclipse-home}
+directory, use the command:</p><code>java -jar plugins\org.eclipse.equinox.launcher_&lt;version&gt;.jar
+ -application ${launcher} -os &lt;operating system&gt; -ws &lt;windowing system&gt; -arch &lt;architecture&gt; -dev bin -testpluginname ${plugin-name} 
+-classname ${test-classname} formattter=org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter,&lt;path to output file with .xml extension&gt;</code> 
+<p>where ${launcher} is one of: <i>org.eclipse.test.uitestapplication</i> or <i>org.eclipse.test.coretestapplication</i> 
+  depending on whether or not you want to run your tests within an active Workbench.</p><p><font size="+1">Output</font></p><p>By default, output from each test run is logged as XML. For each test that 
+  is run, the output is logged into the file called ${classname}.xml. The individual 
+  XML files are located in the ${eclipse-home} directory. When the test run is 
+  finished, you can call the <b>&quot;collect&quot;</b> target in the library 
+  file, which will collect the XML into a single file. See below for an example 
+  of how to use this target correctly.</p>
+  
+<h3>Other issues</h3><h4>Headless Testing vs. UI testing</h4><p>Many plugin tests will not need the Workbench active in order to run. Indeed, 
+  only the minimum number of plugins needed to run the plugin being tested need 
+  to be present when testing in a target Eclipse. There are two different Ant 
+  targets provided for running Eclipse plugin tests. One target starts the entire 
+  Workbench. The other starts Eclipse with the minimum number of plugins needed. 
+  It is up to you to decide which target is most appropriate. For examples, look 
+  at the <b>&quot;ui-test&quot;</b> and <b>&quot;core-test&quot;</b> targets below.</p>
+  
+<h4>Disposing the Display</h4><p>Some low-level tests for the Eclipse platform take actions that are not
+normally possible inside of Eclipse. An example of this behaviour would be
+disposing the display. While this action can be performed while running the UI,
+it will also kill the UI for the copy of Eclipse that is running, and cause
+errors when the Workbench tries to shutdown. If you need to test disposing the
+display, or other similar actions, your tests should be running without a UI. </p>
+
+<h4>Tests that are not plugins</h4><p>It is very easy to forget to define your tests inside of a plugin. If your 
+  tests will not load properly, make sure that a plug-in manifest exists in your 
+  test project, and also that the plugin is being loaded by the platform. Make 
+  sure that all of the dependencies are satisfied for your test plugin.</p>
+  
+<p><font size="+1">Interface</font></p><p>The org.eclipse.test plugin defines many useful Ant tasks/targets to aid developers 
+  in writing their test.xml scripts. Currently, there is only Ant targets defined, 
+  which can be called using Ant's built-in &lt;ant&gt; task. To use these targets, 
+  add the following line to the top of your script, and reference the ${library-file} 
+  property when calling &lt;ant&gt;:</p><code>&lt;property name=&quot;library-file&quot;
+value=&quot;${eclipse-home}/fragments/org.eclipse.test/library.xml&quot;/&gt; </code>
+
+<p>The targets that are defined are: </p><ul>
+  <li><b>ui-test</b> - This target runs a JUnit test suite inside of an Eclipse 
+    Workbench. This target is mainly for testing plugins that use the Eclipse 
+    UI and JFace. The output of the test pass is automatically logged in an XML 
+    file called ${classname}.xml. It takes four arguments: </li><ul>
+  <li><i>data-dir</i> - The
+      data directory of the Eclipse that gets run</li><li><i>plugin-name</i> -
+      The name of the plugin that the test suite is defined in</li><li><i>classname</i> -
+      The name of the class that the test suite is defined in</li><li><i>vmargs</i> - An
+      optional argument string to pass to the VM running the tests</li></ul><p>For example, the following code will run the test
+org.eclipse.foo.bar.MyTest in the plugin org.eclipse.foo in a new Eclipse
+workbench. It passes the string &quot;-Dbaz=true&quot; to the VM. The Eclipse
+stores its metadata in the directory &quot;data-folder&quot;. 
+
+<code><pre>
+&lt;ant target=&quot;ui-test&quot; antfile=&quot;${library-file}&quot; dir=&quot;${eclipse-home}&quot;&gt;
+  &lt;property name=&quot;data-dir&quot; value=&quot;data-folder&quot;/&gt;
+  &lt;property name=&quot;plugin-name&quot; value=&quot;org.eclipse.foo&quot;/&gt;
+  &lt;property name=&quot;classname&quot; value=&quot;org.eclipse.foo.bar.MyTest&quot;/&gt;
+  &lt;property name=&quot;vmargs&quot; value=&quot;-Dbaz=true&quot;/&gt;
+&lt;/ant&gt;
+</pre></code>
+
+  <li><b>core-test</b> - This target runs a JUnit test suite inside of an IPlatformRunnable. 
+    This target is for testing plugins that use the Eclipse platform, but do not 
+    require a UI to be running. The output of the test pass is automatically logged 
+    in an XML file called ${classname}.xml. It takes four arguments: </li><ul>
+  <li><i>data-dir</i> - The
+      data directory of the Eclipse that gets run</li><li><i>plugin-name</i> -
+      The name of the plugin that the test suite is defined in</li><li><i>classname</i> -
+      The name of the class that the test suite is defined in</li><li><i>vmargs</i> - An
+      optional argument string to pass to the VM running the tests</li></ul><p>For example, the following code will run the test
+org.eclipse.foo.bar.MyTest in the plugin org.eclipse.foo in a headless Eclipse.
+It passes the string &quot;-Dbaz=true&quot; to the VM. The Eclipse stores its
+metadata in the directory &quot;data-folder&quot;.
+
+<code><pre>
+&lt;ant target=&quot;core-test&quot; antfile=&quot;${library-file}&quot; dir=&quot;${eclipse-home}&quot;&gt;
+  &lt;property name=&quot;data-dir&quot; value=&quot;data-folder&quot;/&gt;
+  &lt;property name=&quot;plugin-name&quot; value=&quot;org.eclipse.foo&quot;/&gt;
+  &lt;property name=&quot;classname&quot; value=&quot;org.eclipse.foo.bar.MyTest&quot;/&gt;
+  &lt;property name=&quot;vmargs&quot; value=&quot;-Dbaz=true&quot;/&gt;
+&lt;/ant&gt;
+</pre></code>
+
+ <li><b>collect</b> - This
+     target collects the XML files that are produced over the course of the
+     test script. It takes two arguments: </li><ul>
+  <li><i>includes</i> - A
+      pattern matching all XML files to be included in the test report. This
+      argument is typically &quot;org*.xml&quot;</li><li><i>output-file</i> -
+      The filename where the output of the test gets stored. For the automated
+      build process, this file should be ${pluginname}.xml, and be located in
+      the ECLIPSE_HOME directory.</li></ul><p>For example, the following code collects all of the files
+matching the pattern &quot;org*.xml&quot; in the directory ${eclipse-home},
+into the file named &quot;logfile.xml&quot;.
+
+<code><pre>
+&lt;ant target=&quot;collect&quot; antfile=&quot;${library-file}&quot; dir=&quot;${eclipse-home}&quot;&gt;
+  &lt;property name=&quot;includes&quot; value=&quot;org*.xml&quot;/&gt;
+  &lt;property name=&quot;output-file&quot; value=&quot;logfile.xml&quot;/&gt;
+&lt;/ant&gt;
+</pre></code>
+
+ 
+</ul><h2>Examples:</h2><p>Included is the 'test.xml' file from the org.eclipse.jdt.ui.tests.refactoring plugin. This
+file controls all of the automated testing that is done for the  org.eclipse.jdt.ui.tests.refactoring
+plugin. It can be run from inside of Eclipse or from the command line. It is
+intended to serve as a template file for testing any other plugin.</p><p>Notice that the structure of the file roughly mirrors that of a JUnit test.
+Targets are defined for setting up the tests, defining what needs to be done,
+cleaning up after the tests, and running everything in the right order.</p>
+<code><pre>
+&lt;?xml version="1.0" encoding="UTF-8"?&gt;
+
+&lt;project name="testsuite" default="run" basedir="."&gt;
+	&lt;!-- The property ${eclipse-home} should be passed into this script --&gt;
+	&lt;!-- Set a meaningful default value for when it is not. --&gt;
+	&lt;property name="eclipse-home" value="${basedir}\..\.."/&gt;
+
+	&lt;!-- sets the properties eclipse-home, and library-file --&gt;
+	&lt;property name="plugin-name" value="org.eclipse.jdt.ui.tests.refactoring"/&gt;
+	&lt;property name="library-file"
+            value="${eclipse-home}/plugins/org.eclipse.test/library.xml"/&gt;
+
+	&lt;!-- This target holds all initialization code that needs to be done for --&gt;
+	&lt;!-- all tests that are to be run. Initialization for individual tests --&gt;
+	&lt;!-- should be done within the body of the suite target. --&gt;
+	&lt;target name="init"&gt;
+		&lt;tstamp/&gt;
+		&lt;delete&gt;
+			&lt;fileset dir="${eclipse-home}" includes="org*.xml"/&gt;
+		&lt;/delete&gt;
+	&lt;/target&gt;
+
+	&lt;!-- This target defines the tests that need to be run. --&gt;
+	&lt;target name="suite"&gt;
+		&lt;property name="refactoring-folder" 
+              value="${eclipse-home}/refactoring_folder"/&gt;
+		&lt;delete dir="${refactoring-folder}" quiet="true"/&gt;
+		&lt;ant target="ui-test" antfile="${library-file}" dir="${eclipse-home}"&gt;
+			&lt;property name="data-dir" value="${refactoring-folder}"/&gt;
+			&lt;property name="plugin-name" value="${plugin-name}"/&gt;
+			&lt;property name="classname" 
+                value="org.eclipse.jdt.ui.tests.refactoring.all.AllAllRefactoringTests"/&gt;
+		&lt;/ant&gt;
+	&lt;/target&gt;
+	
+	&lt;!-- This target holds code to cleanup the testing environment after --&gt;
+	&lt;!-- after all of the tests have been run. You can use this target to --&gt;
+	&lt;!-- delete temporary files that have been created. --&gt;
+	&lt;target name="cleanup"&gt;
+	&lt;/target&gt;
+
+	&lt;!-- This target runs the test suite. Any actions that need to happen --&gt;
+	&lt;!-- after all the tests have been run should go here. --&gt;
+	&lt;target name="run" depends="init,suite,cleanup"&gt;
+		&lt;ant target="collect" antfile="${library-file}" dir="${eclipse-home}"&gt;
+			&lt;property name="includes" value="org*.xml"/&gt;
+			&lt;property name="output-file" value="${plugin-name}.xml"/&gt;
+		&lt;/ant&gt;
+	&lt;/target&gt;
+	&lt;/project&gt;
+</pre></code>
+
+<h2>Known Issues:</h2><h4>Problem 1: Issues with Ant 1.3</h4><p>Ant 1.3 has some issues when used with the &lt;style&gt; tag and absolute
+paths. Also, any tests that use the <code>System.exit()</code> call will not
+log their output properly when using Ant 1.3.</p><h4>Problem 2: ECLIPSE_HOME</h4><p>The test suites need to know where the root of the eclipse install is on the
+file system (the ECLIPSE_HOME variable). However, this variable is only defined
+in JDT. The ${eclipse-home} property can be set to a reasonable default inside
+of the test.xml script. Then tests can be run from the standard Ant window,
+without having to specify -Declipse-home=%ECLIPSE_HOME%. If a value for
+${eclipse-home} does get passed in, the default (specified in test.xml) gets
+overridden. The parameter is passed in by the build mechanism. For most cases,
+the value &quot;${basedir}/../..&quot; is a reasonable default.</p><h4>Problem 3: Ugly reference to library.xml</h4><p>org.eclipse.test should provide Ant tasks, not template scripts.</p><h4>Problem 4: No console output</h4><p>When you run a TestSuite using the standard JUnit, it normally outputs a
+series of dots to the console so that you can track the TestSuite's progress.
+It is not possible to add this feature to the automated testing process at this
+point in time.</p><h4>Problem 5: Ant java task on Linux</h4><p>Ant expects there to be a java executable on the system path. Furthermore, the executable
+must be a real file, not a symbolic link. If the test framework is throwing an exception
+<code>java.io.IOException: java: not found</code>, ensure that the java executable is on
+your system path.</p><h4>Problem 6: PDE</h4><p>The testing framework currently has no knowledge of PDE. In order to run the automated
+you must be running a self hosting environment with a full development and target Eclipse.</p>
+
+</body>
+
+</html>

Added: directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.eclipse.ui.testing_3.2.0.jar
URL: http://svn.apache.org/viewvc/directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.eclipse.ui.testing_3.2.0.jar?rev=663773&view=auto
==============================================================================
Binary file - no diff available.

Propchange: directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.eclipse.ui.testing_3.2.0.jar
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit4_4.3.1/META-INF/MANIFEST.MF
URL: http://svn.apache.org/viewvc/directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit4_4.3.1/META-INF/MANIFEST.MF?rev=663773&view=auto
==============================================================================
--- directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit4_4.3.1/META-INF/MANIFEST.MF (added)
+++ directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit4_4.3.1/META-INF/MANIFEST.MF Thu Jun  5 16:05:29 2008
@@ -0,0 +1,21 @@
+Manifest-Version: 1.0
+Bundle-ManifestVersion: 2
+Bundle-Name: %pluginName
+Bundle-SymbolicName: org.junit4
+Bundle-Version: 4.3.1
+Bundle-Localization: plugin
+Bundle-ClassPath: junit.jar
+Bundle-RequiredExecutionEnvironment: J2SE-1.5
+Bundle-Vendor: %providerName
+Export-Package: junit.extensions;version="4.3.1",
+ junit.framework;version="4.3.1",
+ junit.runner;version="4.3.1",
+ junit.textui;version="4.3.1",
+ org.junit;version="4.3.1",
+ org.junit.internal;version="4.3.1";x-internal:=true,
+ org.junit.internal.requests;version="4.3.1";x-internal:=true,
+ org.junit.internal.runners;version="4.3.1";x-internal:=true,
+ org.junit.runner;version="4.3.1",
+ org.junit.runner.manipulation;version="4.3.1",
+ org.junit.runner.notification;version="4.3.1",
+ org.junit.runners;version="4.3.1"

Added: directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit4_4.3.1/about.html
URL: http://svn.apache.org/viewvc/directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit4_4.3.1/about.html?rev=663773&view=auto
==============================================================================
--- directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit4_4.3.1/about.html (added)
+++ directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit4_4.3.1/about.html Thu Jun  5 16:05:29 2008
@@ -0,0 +1,50 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
+<title>About</title>
+</head>
+<body lang="EN-US">
+<h2>About This Content</h2>
+ 
+<p>June 7, 2007</p>	
+<h3>License</h3>
+
+<p>The Eclipse Foundation makes available all content in this plug-in (&quot;Content&quot;).  Unless otherwise 
+indicated below, the Content is provided to you under the terms and conditions of the
+Eclipse Public License Version 1.0 (&quot;EPL&quot;).  A copy of the EPL is available 
+at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
+For purposes of the EPL, &quot;Program&quot; will mean the Content.</p>
+
+<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is 
+being redistributed by another party (&quot;Redistributor&quot;) and different terms and conditions may
+apply to your use of any object code in the Content.  Check the Redistributor's license that was 
+provided with the Content.  If no such license exists, contact the Redistributor.  Unless otherwise
+indicated below, the terms and conditions of the EPL still apply to any source code in the Content
+and such source code may be obtained at <a href="http://www.eclipse.org">http://www.eclipse.org</a>.</p>
+
+<h3>Third Party Content</h3>
+
+<p>The Content includes items that have been sourced from third parties as set out below. If you 
+did not receive this Content directly from the Eclipse Foundation, the following is provided 
+for informational purposes only, and you should look to the Redistributor&rsquo;s license for 
+terms and conditions of use.</p>
+
+<p>The Content includes items that have been sourced from third parties as follows:</p>
+
+<h4>JUnit 4.3.1</h4>
+
+<p>The plug-in is accompanied by software developed by JUnit.org.  The JUnit 4.3.1 code included with the plug-in includes no modifications.
+Your use of JUnit 4.3.1 in both source and binary code form contained in the plug-in is subject to the terms and conditions of the 
+Common Public License Version 1.0 (&quot;CPL&quot;).  A copy of the CPL is available at <a href="http://www.eclipse.org/legal/cpl-v10.html">http://www.eclipse.org/legal/cpl-v10.html</a>.
+The binary code is located in junit.jar and the source code is located in junitsrc.zip.</p>
+
+<p>i) IBM effectively disclaims on behalf of all Contributors all warranties and conditions, express and implied, including warranties or conditions of title and non-infringement, and implied warranties or conditions of merchantability and fitness for a particular purpose;</p>
+
+<p>ii) IBM effectively excludes on behalf of all Contributors all liability for damages, including direct, indirect, special, incidental and consequential damages, such as lost profits;</p>
+
+<p>iii) IBM states that any provisions which differ from the CPL are offered by that IBM alone and not by any other party.</p>
+
+</body>
+</html>
\ No newline at end of file

Added: directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit4_4.3.1/junit.jar
URL: http://svn.apache.org/viewvc/directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit4_4.3.1/junit.jar?rev=663773&view=auto
==============================================================================
Binary file - no diff available.

Propchange: directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit4_4.3.1/junit.jar
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit4_4.3.1/plugin.properties
URL: http://svn.apache.org/viewvc/directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit4_4.3.1/plugin.properties?rev=663773&view=auto
==============================================================================
--- directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit4_4.3.1/plugin.properties (added)
+++ directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit4_4.3.1/plugin.properties Thu Jun  5 16:05:29 2008
@@ -0,0 +1,13 @@
+###############################################################################
+# Copyright (c) 2006 IBM Corporation and others.
+# All rights reserved. This program and the accompanying materials
+# are made available under the terms of the Eclipse Public License v1.0
+# which accompanies this distribution, and is available at
+# http://www.eclipse.org/legal/epl-v10.html
+#
+# Contributors:
+#     IBM Corporation - initial API and implementation
+###############################################################################
+
+pluginName=JUnit Testing Framework Version 4
+providerName=Eclipse.org

Added: directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit4_4.3.1/plugin.xml
URL: http://svn.apache.org/viewvc/directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit4_4.3.1/plugin.xml?rev=663773&view=auto
==============================================================================
--- directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit4_4.3.1/plugin.xml (added)
+++ directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit4_4.3.1/plugin.xml Thu Jun  5 16:05:29 2008
@@ -0,0 +1,4 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?eclipse version="3.0"?>
+<plugin>
+</plugin>

Added: directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit_3.8.2.v200706111738/META-INF/MANIFEST.MF
URL: http://svn.apache.org/viewvc/directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit_3.8.2.v200706111738/META-INF/MANIFEST.MF?rev=663773&view=auto
==============================================================================
--- directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit_3.8.2.v200706111738/META-INF/MANIFEST.MF (added)
+++ directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit_3.8.2.v200706111738/META-INF/MANIFEST.MF Thu Jun  5 16:05:29 2008
@@ -0,0 +1,16 @@
+Manifest-Version: 1.0
+Ant-Version: Apache Ant 1.7.0
+Created-By: 2.3 (IBM Corporation)
+Bundle-ManifestVersion: 2
+Export-Package: junit.awtui;version="3.8.2",junit.extensions;version="
+ 3.8.2",junit.framework;version="3.8.2",junit.runner;version="3.8.2",j
+ unit.swingui;version="3.8.2",junit.swingui.icons;version="3.8.2",juni
+ t.textui;version="3.8.2"
+Bundle-Version: 3.8.2.v200706111738
+Bundle-SymbolicName: org.junit
+Bundle-Name: %pluginName
+Bundle-RequiredExecutionEnvironment: J2SE-1.3
+Bundle-Localization: plugin
+Bundle-Vendor: %providerName
+Bundle-ClassPath: junit.jar
+

Added: directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit_3.8.2.v200706111738/META-INF/eclipse.inf
URL: http://svn.apache.org/viewvc/directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit_3.8.2.v200706111738/META-INF/eclipse.inf?rev=663773&view=auto
==============================================================================
--- directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit_3.8.2.v200706111738/META-INF/eclipse.inf (added)
+++ directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit_3.8.2.v200706111738/META-INF/eclipse.inf Thu Jun  5 16:05:29 2008
@@ -0,0 +1,3 @@
+#Processed using Jarprocessor
+pack200.args = -E4
+pack200.conditioned = true

Added: directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit_3.8.2.v200706111738/about.html
URL: http://svn.apache.org/viewvc/directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit_3.8.2.v200706111738/about.html?rev=663773&view=auto
==============================================================================
--- directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit_3.8.2.v200706111738/about.html (added)
+++ directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit_3.8.2.v200706111738/about.html Thu Jun  5 16:05:29 2008
@@ -0,0 +1,50 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
+<title>About</title>
+</head>
+<body lang="EN-US">
+<h2>About This Content</h2>
+ 
+<p>September 28, 2006</p>	
+<h3>License</h3>
+
+<p>The Eclipse Foundation makes available all content in this plug-in (&quot;Content&quot;).  Unless otherwise 
+indicated below, the Content is provided to you under the terms and conditions of the
+Eclipse Public License Version 1.0 (&quot;EPL&quot;).  A copy of the EPL is available 
+at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
+For purposes of the EPL, &quot;Program&quot; will mean the Content.</p>
+
+<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is 
+being redistributed by another party (&quot;Redistributor&quot;) and different terms and conditions may
+apply to your use of any object code in the Content.  Check the Redistributor's license that was 
+provided with the Content.  If no such license exists, contact the Redistributor.  Unless otherwise
+indicated below, the terms and conditions of the EPL still apply to any source code in the Content
+and such source code may be obtained at <a href="http://www.eclipse.org">http://www.eclipse.org</a>.</p>
+
+<h3>Third Party Content</h3>
+
+<p>The Content includes items that have been sourced from third parties as set out below. If you 
+did not receive this Content directly from the Eclipse Foundation, the following is provided 
+for informational purposes only, and you should look to the Redistributor&rsquo;s license for 
+terms and conditions of use.</p>
+
+<p>The Content includes items that have been sourced from third parties as follows:</p>
+
+<h4>JUnit 3.8.2</h4>
+
+<p>The plug-in is accompanied by software developed by JUnit.org.  The JUnit 3.8.2 code included with the plug-in includes no modifications.
+Your use of JUnit 3.8.2 in both source and binary code form contained in the plug-in is subject to the terms and conditions of the 
+Common Public License Version 1.0 (&quot;CPL&quot;).  A copy of the CPL is available at <a href="http://www.eclipse.org/legal/cpl-v10.html">http://www.eclipse.org/legal/cpl-v10.html</a>.
+The binary code is located in junit.jar and the source code is located in src.jar.</p>
+
+<p>i) IBM effectively disclaims on behalf of all Contributors all warranties and conditions, express and implied, including warranties or conditions of title and non-infringement, and implied warranties or conditions of merchantability and fitness for a particular purpose;</p>
+
+<p>ii) IBM effectively excludes on behalf of all Contributors all liability for damages, including direct, indirect, special, incidental and consequential damages, such as lost profits;</p>
+
+<p>iii) IBM states that any provisions which differ from the CPL are offered by that IBM alone and not by any other party.</p>
+
+</body>
+</html>
\ No newline at end of file

Added: directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit_3.8.2.v200706111738/about_files/cpl-v10.html
URL: http://svn.apache.org/viewvc/directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit_3.8.2.v200706111738/about_files/cpl-v10.html?rev=663773&view=auto
==============================================================================
--- directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit_3.8.2.v200706111738/about_files/cpl-v10.html (added)
+++ directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit_3.8.2.v200706111738/about_files/cpl-v10.html Thu Jun  5 16:05:29 2008
@@ -0,0 +1,125 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<HTML>
+<HEAD>
+<TITLE>Common Public License - v 1.0</TITLE>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+</HEAD>
+
+<BODY BGCOLOR="#FFFFFF" VLINK="#800000">
+
+
+<P ALIGN="CENTER"><B>Common Public License - v 1.0</B>
+<P><B></B><FONT SIZE="3"></FONT>
+<P><FONT SIZE="3"></FONT><FONT SIZE="2">THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS COMMON PUBLIC LICENSE ("AGREEMENT").  ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.</FONT>
+<P><FONT SIZE="2"></FONT>
+<P><FONT SIZE="2"><B>1.  DEFINITIONS</B></FONT>
+<P><FONT SIZE="2">"Contribution" means:</FONT>
+
+<UL><FONT SIZE="2">a) in the case of the initial Contributor, the initial code and documentation distributed under this Agreement, and<BR CLEAR="LEFT">
+b) in the case of each subsequent Contributor:</FONT></UL>
+
+
+<UL><FONT SIZE="2">i)	 	changes to the Program, and</FONT></UL>
+
+
+<UL><FONT SIZE="2">ii)		additions to the Program;</FONT></UL>
+
+
+<UL><FONT SIZE="2">where such changes and/or additions to the Program originate from and are distributed by that particular Contributor.  </FONT><FONT SIZE="2">A Contribution 'originates' from a Contributor if it was added to the Program by such Contributor itself or anyone acting on such Contributor's behalf.  </FONT><FONT SIZE="2">Contributions do not include additions to the Program which:  (i) are separate modules of software distributed in conjunction with the Program under their own license agreement, and (ii) are not derivative works of the Program.  </FONT></UL>
+
+<P><FONT SIZE="2"></FONT>
+<P><FONT SIZE="2">"Contributor" means any person or entity that distributes the Program.</FONT>
+<P><FONT SIZE="2"></FONT><FONT SIZE="2"></FONT>
+<P><FONT SIZE="2">"Licensed Patents " mean patent claims licensable by a Contributor which are necessarily infringed by the use or sale of its Contribution alone or when combined with the Program.  </FONT>
+<P><FONT SIZE="2"></FONT><FONT SIZE="2"></FONT>
+<P><FONT SIZE="2"></FONT><FONT SIZE="2">"Program" means the Contributions distributed in accordance with this Agreement.</FONT>
+<P><FONT SIZE="2"></FONT>
+<P><FONT SIZE="2">"Recipient" means anyone who receives the Program under this Agreement, including all Contributors.</FONT>
+<P><FONT SIZE="2"><B></B></FONT>
+<P><FONT SIZE="2"><B>2.  GRANT OF RIGHTS</B></FONT>
+
+<UL><FONT SIZE="2"></FONT><FONT SIZE="2">a)	</FONT><FONT SIZE="2">Subject to the terms of this Agreement, each Contributor hereby grants</FONT><FONT SIZE="2"> Recipient a non-exclusive, worldwide, royalty-free copyright license to</FONT><FONT SIZE="2" COLOR="#FF0000"> </FONT><FONT SIZE="2">reproduce, prepare derivative works of, publicly display, publicly perform, distribute and sublicense the Contribution of such Contributor, if any, and such derivative works, in source code and object code form.</FONT></UL>
+
+
+<UL><FONT SIZE="2"></FONT></UL>
+
+
+<UL><FONT SIZE="2"></FONT><FONT SIZE="2">b) 	Subject to the terms of this Agreement, each Contributor hereby grants </FONT><FONT SIZE="2">Recipient a non-exclusive, worldwide,</FONT><FONT SIZE="2" COLOR="#008000"> </FONT><FONT SIZE="2">royalty-free patent license under Licensed Patents to make, use, sell, offer to sell, import and otherwise transfer the Contribution of such Contributor, if any, in source code and object code form.  This patent license shall apply to the combination of the Contribution and the Program if, at the time the Contribution is added by the Contributor, such addition of the Contribution causes such combination to be covered by the Licensed Patents.  The patent license shall not apply to any other combinations which include the Contribution.  No hardware per se is licensed hereunder.   </FONT></UL>
+
+
+<UL><FONT SIZE="2"></FONT></UL>
+
+
+<UL><FONT SIZE="2">c)	Recipient understands that although each Contributor grants the licenses to its Contributions set forth herein, no assurances are provided by any Contributor that the Program does not infringe the patent or other intellectual property rights of any other entity.  Each Contributor disclaims any liability to Recipient for claims brought by any other entity based on infringement of intellectual property rights or otherwise.  As a condition to exercising the rights and licenses granted hereunder, each Recipient hereby assumes sole responsibility to secure any other intellectual property rights needed, if any.  For example, if a third party patent license is required to allow Recipient to distribute the Program, it is Recipient's responsibility to acquire that license before distributing the Program.</FONT></UL>
+
+
+<UL><FONT SIZE="2"></FONT></UL>
+
+
+<UL><FONT SIZE="2">d)	Each Contributor represents that to its knowledge it has sufficient copyright rights in its Contribution, if any, to grant the copyright license set forth in this Agreement. </FONT></UL>
+
+
+<UL><FONT SIZE="2"></FONT></UL>
+
+<P><FONT SIZE="2"><B>3.  REQUIREMENTS</B></FONT>
+<P><FONT SIZE="2"><B></B>A Contributor may choose to distribute the Program in object code form under its own license agreement, provided that:</FONT>
+
+<UL><FONT SIZE="2">a)	it complies with the terms and conditions of this Agreement; and</FONT></UL>
+
+
+<UL><FONT SIZE="2">b)	its license agreement:</FONT></UL>
+
+
+<UL><FONT SIZE="2">i)	effectively disclaims</FONT><FONT SIZE="2"> on behalf of all Contributors all warranties and conditions, express and implied, including warranties or conditions of title and non-infringement, and implied warranties or conditions of merchantability and fitness for a particular purpose; </FONT></UL>
+
+
+<UL><FONT SIZE="2">ii) 	effectively excludes on behalf of all Contributors all liability for damages, including direct, indirect, special, incidental and consequential damages, such as lost profits; </FONT></UL>
+
+
+<UL><FONT SIZE="2">iii)</FONT><FONT SIZE="2">	states that any provisions which differ from this Agreement are offered by that Contributor alone and not by any other party; and</FONT></UL>
+
+
+<UL><FONT SIZE="2">iv)	states that source code for the Program is available from such Contributor, and informs licensees how to obtain it in a reasonable manner on or through a medium customarily used for software exchange.</FONT><FONT SIZE="2" COLOR="#0000FF"> </FONT><FONT SIZE="2" COLOR="#FF0000"></FONT></UL>
+
+
+<UL><FONT SIZE="2" COLOR="#FF0000"></FONT><FONT SIZE="2"></FONT></UL>
+
+<P><FONT SIZE="2">When the Program is made available in source code form:</FONT>
+
+<UL><FONT SIZE="2">a)	it must be made available under this Agreement; and </FONT></UL>
+
+
+<UL><FONT SIZE="2">b)	a copy of this Agreement must be included with each copy of the Program.  </FONT></UL>
+
+<P><FONT SIZE="2"></FONT><FONT SIZE="2" COLOR="#0000FF"><STRIKE></STRIKE></FONT>
+<P><FONT SIZE="2" COLOR="#0000FF"><STRIKE></STRIKE></FONT><FONT SIZE="2">Contributors may not remove or alter any copyright notices contained within the Program.  </FONT>
+<P><FONT SIZE="2"></FONT>
+<P><FONT SIZE="2">Each Contributor must identify itself as the originator of its Contribution, if any, in a manner that reasonably allows subsequent Recipients to identify the originator of the Contribution.  </FONT>
+<P><FONT SIZE="2"></FONT>
+<P><FONT SIZE="2"><B>4.  COMMERCIAL DISTRIBUTION</B></FONT>
+<P><FONT SIZE="2">Commercial distributors of software may accept certain responsibilities with respect to end users, business partners and the like.  While this license is intended to facilitate the commercial use of the Program, the Contributor who includes the Program in a commercial product offering should do so in a manner which does not create potential liability for other Contributors.   Therefore, if a Contributor includes the Program in a commercial product offering, such Contributor ("Commercial Contributor") hereby agrees to defend and indemnify every other Contributor ("Indemnified Contributor") against any losses, damages and costs (collectively "Losses") arising from claims, lawsuits and other legal actions brought by a third party against the Indemnified Contributor to the extent caused by the acts or omissions of such Commercial Contributor in connection with its distribution of the Program in a commercial product offering.  The obligations in this section do 
 not apply to any claims or Losses relating to any actual or alleged intellectual property infringement.  In order to qualify, an Indemnified Contributor must: a) promptly notify the Commercial Contributor in writing of such claim, and b) allow the Commercial Contributor to control, and cooperate with the Commercial Contributor in, the defense and any related settlement negotiations.  The Indemnified Contributor may participate in any such claim at its own expense.</FONT>
+<P><FONT SIZE="2"></FONT>
+<P><FONT SIZE="2">For example, a Contributor might include the Program in a commercial product offering, Product X.  That Contributor is then a Commercial Contributor.  If that Commercial Contributor then makes performance claims, or offers warranties related to Product X, those performance claims and warranties are such Commercial Contributor's responsibility alone.  Under this section, the Commercial Contributor would have to defend claims against the other Contributors related to those performance claims and warranties, and if a court requires any other Contributor to pay any damages as a result, the Commercial Contributor must pay those damages.</FONT>
+<P><FONT SIZE="2"></FONT><FONT SIZE="2" COLOR="#0000FF"></FONT>
+<P><FONT SIZE="2" COLOR="#0000FF"></FONT><FONT SIZE="2"><B>5.  NO WARRANTY</B></FONT>
+<P><FONT SIZE="2">EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is</FONT><FONT SIZE="2"> solely responsible for determining the appropriateness of using and distributing </FONT><FONT SIZE="2">the Program</FONT><FONT SIZE="2"> and assumes all risks associated with its exercise of rights under this Agreement</FONT><FONT SIZE="2">, including but not limited to the risks and costs of program errors, compliance with applicable laws, damage to or loss of data, </FONT><FONT SIZE="2">programs or equipment, and unavailability or interruption of operations</FONT><FONT SIZE="2">.  </FONT><FONT SIZE="2"></FONT>
+<P><FONT SIZE="2"></FONT>
+<P><FONT SIZE="2"></FONT><FONT SIZE="2"><B>6.  DISCLAIMER OF LIABILITY</B></FONT>
+<P><FONT SIZE="2"></FONT><FONT SIZE="2">EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES </FONT><FONT SIZE="2">(INCLUDING WITHOUT LIMITATION LOST PROFITS),</FONT><FONT SIZE="2"> HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.</FONT>
+<P><FONT SIZE="2"></FONT><FONT SIZE="2"></FONT>
+<P><FONT SIZE="2"><B>7.  GENERAL</B></FONT>
+<P><FONT SIZE="2"></FONT><FONT SIZE="2">If any provision of this Agreement is invalid or unenforceable under applicable law, it shall not affect the validity or enforceability of the remainder of the terms of this Agreement, and without further action by the parties hereto, such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable.</FONT>
+<P><FONT SIZE="2"></FONT>
+<P><FONT SIZE="2">If Recipient institutes patent litigation against a Contributor with respect to a patent applicable to software (including a cross-claim or counterclaim in a lawsuit), then any patent licenses granted by that Contributor to such Recipient under this Agreement shall terminate as of the date such litigation is filed.  In addition, if Recipient institutes patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Program itself (excluding combinations of the Program with other software or hardware) infringes such Recipient's patent(s), then such Recipient's rights granted under Section 2(b) shall terminate as of the date such litigation is filed. </FONT><FONT SIZE="2"></FONT>
+<P><FONT SIZE="2"></FONT>
+<P><FONT SIZE="2">All Recipient's rights under this Agreement shall terminate if it fails to comply with any of the material terms or conditions of this Agreement and does not cure such failure in a reasonable period of time after becoming aware of such noncompliance.  If all Recipient's rights under this Agreement terminate, Recipient agrees to cease use and distribution of the Program as soon as reasonably practicable.  However, Recipient's obligations under this Agreement and any licenses granted by Recipient relating to the Program shall continue and survive.  </FONT><FONT SIZE="2"></FONT>
+<P><FONT SIZE="2"></FONT>
+<P><FONT SIZE="2"></FONT><FONT SIZE="2">Everyone is permitted to copy and distribute copies of this Agreement, but in order to avoid inconsistency the Agreement is copyrighted  and may only be modified in the following manner. The Agreement Steward reserves the right to </FONT><FONT SIZE="2">publish new versions (including revisions) of this Agreement from time to </FONT><FONT SIZE="2">time. No one other than the Agreement Steward has the right to modify this Agreement. IBM is the initial Agreement Steward.   IBM may assign the responsibility to serve as the Agreement Steward to a suitable separate entity.  </FONT><FONT SIZE="2">Each new version of the Agreement will be given a distinguishing version number.  The Program (including Contributions) may always be distributed subject to the version of the Agreement under which it was received. In addition, after a new version of the Agreement is published, Contributor may elect to distribute the Program (including its Contributi
 ons) under the new </FONT><FONT SIZE="2">version.  </FONT><FONT SIZE="2">Except as expressly stated in Sections 2(a) and 2(b) above, Recipient receives no rights or licenses to the intellectual property of any Contributor under this Agreement, whether expressly, </FONT><FONT SIZE="2">by implication, estoppel or otherwise</FONT><FONT SIZE="2">.</FONT><FONT SIZE="2">  All rights in the Program not expressly granted under this Agreement are reserved.</FONT>
+<P><FONT SIZE="2"></FONT>
+<P><FONT SIZE="2">This Agreement is governed by the laws of the State of New York and the intellectual property laws of the United States of America. No party to this Agreement will bring a legal action under this Agreement more than one year after the cause of action arose.  Each party waives its rights to a jury trial in any resulting litigation.</FONT>
+<P><FONT SIZE="2"></FONT><FONT SIZE="2"></FONT>
+<P><FONT SIZE="2"></FONT>
+
+</BODY>
+
+</HTML>
\ No newline at end of file

Added: directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit_3.8.2.v200706111738/junit.jar
URL: http://svn.apache.org/viewvc/directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit_3.8.2.v200706111738/junit.jar?rev=663773&view=auto
==============================================================================
Binary file - no diff available.

Propchange: directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit_3.8.2.v200706111738/junit.jar
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit_3.8.2.v200706111738/plugin.properties
URL: http://svn.apache.org/viewvc/directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit_3.8.2.v200706111738/plugin.properties?rev=663773&view=auto
==============================================================================
--- directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit_3.8.2.v200706111738/plugin.properties (added)
+++ directory/sandbox/seelmann/testingframework/test-integration-ui/resources/test-plugins/org.junit_3.8.2.v200706111738/plugin.properties Thu Jun  5 16:05:29 2008
@@ -0,0 +1,13 @@
+###############################################################################
+# Copyright (c) 2000, 2004 IBM Corporation and others.
+# All rights reserved. This program and the accompanying materials
+# are made available under the terms of the Eclipse Public License v1.0
+# which accompanies this distribution, and is available at
+# http://www.eclipse.org/legal/epl-v10.html
+#
+# Contributors:
+#     IBM Corporation - initial API and implementation
+###############################################################################
+
+pluginName=JUnit Testing Framework
+providerName=Eclipse.org

Modified: directory/sandbox/seelmann/testingframework/test-integration-ui/src/main/java/org/apache/directory/studio/test/integration/ui/ConnectionUiTest.java
URL: http://svn.apache.org/viewvc/directory/sandbox/seelmann/testingframework/test-integration-ui/src/main/java/org/apache/directory/studio/test/integration/ui/ConnectionUiTest.java?rev=663773&r1=663772&r2=663773&view=diff
==============================================================================
--- directory/sandbox/seelmann/testingframework/test-integration-ui/src/main/java/org/apache/directory/studio/test/integration/ui/ConnectionUiTest.java (original)
+++ directory/sandbox/seelmann/testingframework/test-integration-ui/src/main/java/org/apache/directory/studio/test/integration/ui/ConnectionUiTest.java Thu Jun  5 16:05:29 2008
@@ -29,7 +29,6 @@
 import net.sf.swtbot.widgets.SWTBotTable;
 import net.sf.swtbot.widgets.SWTBotText;
 import net.sf.swtbot.widgets.SWTBotTree;
-import net.sf.swtbot.widgets.SWTBotTreeItem;
 
 import org.apache.directory.server.unit.AbstractServerTest;
 import org.apache.directory.studio.connection.core.Connection;



Mime
View raw message