Attachment 172965 Details for Bug 211752 – Documentation of BVT

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

[patch] Documentation of BVT

Documentation of BVT 20100628 patch.txt (text/plain), 9.30 KB, created by Samuel Wu

on 2010-06-28 17:05:14 EDT

(hide)

Description:

Filename:

MIME Type:

Creator: Samuel Wu

Created: 2010-06-28 17:05:14 EDT

Size: 9.30 KB

patch

obsolete

>### Eclipse Workspace Patch 1.0
>#P org.eclipse.tptp.platform.releng.tools
>Index: org/eclipse/tptp/platform/releng/tools/testautomation/readme.html
>===================================================================
>RCS file: /cvsroot/tptp/platform/org.eclipse.tptp.platform.releng.tools/org/eclipse/tptp/platform/releng/tools/testautomation/readme.html,v
>retrieving revision 1.1
>diff -u -r1.1 readme.html
>--- org/eclipse/tptp/platform/releng/tools/testautomation/readme.html	25 Feb 2008 16:43:11 -0000	1.1
>+++ org/eclipse/tptp/platform/releng/tools/testautomation/readme.html	28 Jun 2010 20:53:29 -0000
>@@ -1,7 +1,7 @@
> <html>
> <!--
> 
>- Copyright (c) 2008 IBM Corporation and others. 
>+ Copyright (c) 2008, 2010 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 
>@@ -57,12 +57,10 @@
> 		<li>Create a directory to store the test automation in, such as test-automation in the following sample structure: 
> 		test-automation 
> 		|-scripts 
>-		| |-bin 
> 		|-dependencies 
> 		|-ant 
> 		|-workbench</li>
> 		<li>Extract the automation scripts to the scripts directory from CVS and set the sh scripts to execute</li>
>-		<li>Ensure the jar files for configuring the remote machine are in a bin/ directory where the ant scripts are located (test-automation/scripts/bin/)</li>
> 		<li>Navigate to <a href="http://ant.apache.org">http://ant.apache.org</a></li>
> 		<li>Click on Binary Distributions under the Download section in the left navigation bar</li>
> 		<li>Download Ant, for example to dependencies</li>
>@@ -77,12 +75,11 @@
> 	Reporting automation setup 
> 	<ol>
> 		<li>Download <a href="http://download.eclipse.org/eclipse/downloads/">Eclipse</a>, <a href="http://www.eclipse.org/tptp/home/downloads/">TPTP</a>,
>-		<a href="http://download.eclipse.org/birt/downloads/">BIRT</a>, <a href="http://www.eclipse.org/datatools/downloads.php">DTP</a>, and 
>-		<a href="http://www.eclipse.org/gef/downloads/">GEF</a>. For TPTP 4.5.x you will also need the As-Is components Manual Test Tools, 
>-		Business Intelligence and Reporting Tools (BIRT) Test Reports, Business Intelligence and Reporting Tools (BIRT) Log Reports, 
>-		Business Intelligence and Reporting Tools (BIRT) Trace Reports, and Business Intelligence and Reporting Tools (BIRT) Statistical Reports.</li>
>+		<a href="http://download.eclipse.org/birt/downloads/">BIRT</a>, <a href="http://www.eclipse.org/datatools/downloads.php">DTP</a>, 
>+		<a href="http://www.eclipse.org/gef/downloads/">GEF</a>, <a href="http://eclipse.org/modeling/emf/downloads/">EMF</a>, <a href="http://eclipse.org/modeling/emf/downloads/">XSD</a>, As-Is components Manual Test Tools, Automated GUI Recorder, 
>+		Business Intelligence and Reporting Tools (BIRT) Test Reports, Business Intelligence and Reporting Tools (BIRT) Trace Reports.</li>
> 		<li>Extract the downloads to a workbench folder</li>
>-		<li>Copy workbench\eclipse\plugins\com.jcraft.jsch_0.1.31.jar and eclipse\plugins\org.eclipse.hyades.execution_&lt;build-id&gt;\ant-tptp.jar to
>+		<li>Copy workbench\eclipse\plugins\com.jcraft.jsch_0.1.41.v200903070017.jar and workbench\eclipse\dropins\eclipse\plugins\org.eclipse.hyades.execution_&lt;build-id&gt;\ant-tptp.jar to
> 		the ant\lib directory</li>
> 	</ol>
> 	Test automation setup 
>@@ -110,23 +107,24 @@
> 
> 	After completing <a href="#Setup">setup</a>, you can run reports on test suites to automatically generate reports. 
> 	Syntax for nightly.sh for reporting: 
>-	nightly.sh report &lt;release&gt; &lt;property file&gt; "&lt;report start time&gt;" 
>+	nightly.sh --runType=report --tptpRelease=&lt;release&gt; --propertyFile=&lt;property file&gt; --reportStartTime=&quot;&lt;reportStartTime&gt&quot; 
> 	Note: no end time is passed since it is automatically determined, i.e. reports will be from start time until the script begins 
>-	Syntax for setup.sh for reporting: 
>-	With only a report start time: setup.sh report &lt;release&gt; &lt;property file&gt; &quot;&lt;report start time&gt;&quot; 
>-	With both a report start and end time: setup.sh report &lt;release&gt; &lt;property file&gt; &quot;&lt;report start time&gt;&quot; &quot;&lt;report end time&gt;&quot; 
>-	Setup a cronjob for nightly reporting, e.g. export CVS_RSH=ssh; cd test-automation/scripts; ./nightly.sh report 4.5.0 test-automation/scripts/test450.properties &quot;02/04/2008 12:00 AM&quot;&gt;test-automation/scripts/report.log 2&gt;&amp;1
>+	Syntax for setup.sh for reporting with only a report start time: 
>+	setup.sh --runType=report --tptpRelease=&lt;release&gt; --propertyFile=&lt;property file&gt; --reportStartTime=&quot;&lt;reportStartTime&gt&quot; 
>+	Syntax for setup.sh for reporting with both a report start and end time: 
>+	setup.sh --runType=report --tptpRelease=&lt;release&gt; --propertyFile=&lt;property file&gt; --reportStartTime=&quot;&lt;reportStartTime&gt&quot; --reportEndTime=&quot;&lt;reportEndTime&gt&quot; 
>+	Setup a cronjob for nightly reporting: e.g. export CVS_RSH=ssh; cd test-automation/scripts; ./nightly.sh --runType=report --tptpRelease=4.7.0 --propertyFile=test-automation/scripts/test.properties --reportStartTime=&quot;05/24/2010 12:00 PM&quot; &gt test-automation/scripts/report.log 2&gt;&amp;1
> 
> 
> <h2><a name="Testing"></a>Running Testing Automation</h2>
> 
>-	After completing <a href="#Setup">setup</a>, you can run test automation on test suites. 
>+	After completing <a href="#Setup">setup</a>, you can run test automation on test suites. Make sure no other bvt is currently running on the machine. 
> 	Syntax for nightly.sh for testing: 
>-	nightly.sh bvt &lt;release&gt; &lt;property file&gt; 
>+	nightly.sh --runType=bvt --tptpRelease=&lt;release&gt; --propertyFile=&lt;property file&gt; --jreList=&lt;jre list&gt; 
> 	Note: no start time is passed since it is automatically determined, i.e. bvt will be for that day's build 
> 	Syntax for setup.sh for testing: 
>-	setup.sh bvt &lt;release&gt; &lt;property file&gt; &lt;driver&gt; 
>-	Setup a cronjob for nightly testing, e.g. export CVS_RSH=ssh; cd test-automation/scripts; ./nightly.sh bvt 4.5.0 test-automation/scripts/test.properties&gt;test-automation/scripts/bvt.log 2&gt;&amp;1
>+	setup.sh --runType=bvt --tptpRelease=&lt;release&gt; --propertyFile=&lt;property file&gt; --tptpDriver=&lt;driver&gt; --jreList=&lt;jre list&gt; 
>+	Setup a cronjob for nightly testing: e.g. export CVS_RSH=ssh; cd test-automation/scripts; ./nightly.sh --runType=bvt --tptpRelease=4.7.0 --propertyFile=test-automation/scripts/test.properties --jreList= &lt;jre list&gt &gt test-automation/scripts/bvt.log 2&gt;&amp;1
> 
> 
> <h2><a name="Properties"></a>Property File Configuration</h2>
>@@ -137,19 +135,13 @@
> 	user1 - The user to login with on the remote machine. 
> 	keyfile1 - The path (including file name) for the keyfile to login to the remote machine. 
> 	dir1 - The root directory for test automation on the remote machine. 
>+	cygwinPath1 - The path to the AC home directory on the remote machine. 
> 	 
> 
>-	acUser1 - The user for configuring the Agent Controller on the remote machine. 
>-	acPassword1 - The password for the user used to configure the Agent Controller on the remote machine. 
>-	cygwinACPath1 - The path to the AC home directory on the remote machine. 
>-	javaLocation1 - The path to the JRE on the remote machine. 
>-	 
>-	
> 	reportLocation1,2 - The location to store the reports when running the automation on the local machine. 
> 	reportDirectory=TP12 - The containing directory within the project where the test suites are located. 
> 	reportCheckinDirectory2 - The containing directory to store the reports for check-in. 
>-	reportHostname1 - The hostname of the machine to copy the test automation reports to. 
>-	reportUser1 - The user to use when logging into the host for test automation report copying. 
>+	reportHost1 - The hostname of the machine to copy the test automation reports to. 
> 	 
> 	
> 	tptp.test.workspace1,2 - The location to create the workspace on the local machine. 
>@@ -160,7 +152,7 @@
> 	cvsBranch1,2 - The branch to check the projects out from CVS. 
> 	 
> 	
>-	tptpDriver1 - The type of remote machine for test automation (tptpWinDriver or tptpLinuxDriver). 
>+	acDriver1 - The Agent Controller driver for test automation (tptpWinDriver or tptpLinuxDriver). 
> 	testSuite1,2 - The test suite to include in test automation or reporting. Note: This must be set to a non-existent test suite name if only test suite exclusion is required. 
> 	excludeTestSuite1,2 - The test suite to exclude in test automation or reporting. Note: This must be set to a non-existent test suite name if all test suites are required. 
> 	testProject1,2 - The project to obtain the test suites from.

Actions: View | Diff

Attachments on bug 211752: 172965