Download
Getting Started
Members
Projects
Community
Marketplace
Events
Planet Eclipse
Newsletter
Videos
Participate
Report a Bug
Forums
Mailing Lists
Wiki
IRC
How to Contribute
Working Groups
Automotive
Internet of Things
LocationTech
Long-Term Support
PolarSys
Science
OpenMDM
More
Community
Marketplace
Events
Planet Eclipse
Newsletter
Videos
Participate
Report a Bug
Forums
Mailing Lists
Wiki
IRC
How to Contribute
Working Groups
Automotive
Internet of Things
LocationTech
Long-Term Support
PolarSys
Science
OpenMDM
Toggle navigation
Bugzilla – Attachment 172965 Details for
Bug 211752
Provide documentation of BVT PoC.
Home
|
New
|
Browse
|
Search
|
[?]
|
Reports
|
Requests
|
Help
|
Log In
[x]
|
Terms of Use
|
Copyright Agent
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:
Documentation of BVT
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:<br/> > test-automation<br/> > |-scripts<br/> >- | |-bin<br/> > |-dependencies<br/> > |-ant<br/> > |-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 @@ > <b>Reporting automation setup</b><br/> > <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_<build-id>\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_<build-id>\ant-tptp.jar to > the ant\lib directory</li> > </ol> > <b>Test automation setup</b><br/> >@@ -110,23 +107,24 @@ > <p> > After completing <a href="#Setup">setup</a>, you can run reports on test suites to automatically generate reports.<br/> > Syntax for nightly.sh for reporting:<br/> >- nightly.sh report <release> <property file> "<report start time>"<br/> >+ nightly.sh --runType=report --tptpRelease=<release> --propertyFile=<property file> --reportStartTime="<reportStartTime>"<br/> > Note: no end time is passed since it is automatically determined, i.e. reports will be from start time until the script begins<br/> >- Syntax for setup.sh for reporting:<br/> >- With only a report start time: setup.sh report <release> <property file> "<report start time>"<br/> >- With both a report start and end time: setup.sh report <release> <property file> "<report start time>" "<report end time>"<br/> >- 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 "02/04/2008 12:00 AM">test-automation/scripts/report.log 2>&1 >+ Syntax for setup.sh for reporting with only a report start time:<br/> >+ setup.sh --runType=report --tptpRelease=<release> --propertyFile=<property file> --reportStartTime="<reportStartTime>"<br/> >+ Syntax for setup.sh for reporting with both a report start and end time:<br/> >+ setup.sh --runType=report --tptpRelease=<release> --propertyFile=<property file> --reportStartTime="<reportStartTime>" --reportEndTime="<reportEndTime>"<br/> >+ Setup a cronjob for nightly reporting:<br/> 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="05/24/2010 12:00 PM" > test-automation/scripts/report.log 2>&1 > </p> > > <h2><a name="Testing"></a>Running Testing Automation</h2> > <p> >- After completing <a href="#Setup">setup</a>, you can run test automation on test suites.<br/> >+ 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.<br/> > Syntax for nightly.sh for testing:<br/> >- nightly.sh bvt <release> <property file><br/> >+ nightly.sh --runType=bvt --tptpRelease=<release> --propertyFile=<property file> --jreList=<jre list><br/> > Note: no start time is passed since it is automatically determined, i.e. bvt will be for that day's build<br/> > Syntax for setup.sh for testing:<br/> >- setup.sh bvt <release> <property file> <driver><br/> >- 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>test-automation/scripts/bvt.log 2>&1 >+ setup.sh --runType=bvt --tptpRelease=<release> --propertyFile=<property file> --tptpDriver=<driver> --jreList=<jre list><br/> >+ Setup a cronjob for nightly testing:<br/> 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= <jre list> > test-automation/scripts/bvt.log 2>&1 > </p> > > <h2><a name="Properties"></a>Property File Configuration</h2> >@@ -137,19 +135,13 @@ > <b>user</b><sup>1</sup> - The user to login with on the remote machine.<br/> > <b>keyfile</b><sup>1</sup> - The path (including file name) for the keyfile to login to the remote machine.<br/> > <b>dir</b><sup>1</sup> - The root directory for test automation on the remote machine.<br/> >+ <b>cygwinPath</b><sup>1</sup> - The path to the AC home directory on the remote machine.<br/> > <br/> > >- <b>acUser</b><sup>1</sup> - The user for configuring the Agent Controller on the remote machine.<br/> >- <b>acPassword</b><sup>1</sup> - The password for the user used to configure the Agent Controller on the remote machine.<br/> >- <b>cygwinACPath</b><sup>1</sup> - The path to the AC home directory on the remote machine.<br/> >- <b>javaLocation</b><sup>1</sup> - The path to the JRE on the remote machine.<br/> >- <br/> >- > <b>reportLocation</b><sup>1,2</sup> - The location to store the reports when running the automation on the local machine.<br/> > <b>reportDirectory=TP1</b><sup>2</sup> - The containing directory within the project where the test suites are located.<br/> > <b>reportCheckinDirectory</b><sup>2</sup> - The containing directory to store the reports for check-in.<br/> >- <b>reportHostname</b><sup>1</sup> - The hostname of the machine to copy the test automation reports to.<br/> >- <b>reportUser</b><sup>1</sup> - The user to use when logging into the host for test automation report copying.<br/> >+ <b>reportHost</b><sup>1</sup> - The hostname of the machine to copy the test automation reports to.<br/> > <br/> > > <b>tptp.test.workspace</b><sup>1,2</sup> - The location to create the workspace on the local machine.<br/> >@@ -160,7 +152,7 @@ > <b>cvsBranch</b><sup>1,2</sup> - The branch to check the projects out from CVS.<br/> > <br/> > >- <b>tptpDriver</b><sup>1</sup> - The type of remote machine for test automation (tptpWinDriver or tptpLinuxDriver).<br/> >+ <b>acDriver</b><sup>1</sup> - The Agent Controller driver for test automation (tptpWinDriver or tptpLinuxDriver).<br/> > <b>testSuite</b><sup>1,2</sup> - 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.<br/> > <b>excludeTestSuite</b><sup>1,2</sup> - 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.<br/> > <b>testProject</b><sup>1,2</sup> - The project to obtain the test suites from.<br/>
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Actions:
View
|
Diff
Attachments on
bug 211752
: 172965