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 96616 Details for
Bug 201892
doc updates for section Creating a test deployment
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]
Patch.
Defect_201892_patch.txt (text/plain), 80.70 KB, created by
Paul Slauenwhite
on 2008-04-18 12:03:45 EDT
(
hide
)
Description:
Patch.
Filename:
MIME Type:
Creator:
Paul Slauenwhite
Created:
2008-04-18 12:03:45 EDT
Size:
80.70 KB
patch
obsolete
>### Eclipse Workspace Patch 1.0 >#P org.eclipse.hyades.test.doc.user >Index: concepts/cartifacteditor.htm >=================================================================== >RCS file: /cvsroot/tptp/test/org.eclipse.hyades.test.doc.user/concepts/cartifacteditor.htm,v >retrieving revision 1.5 >diff -u -r1.5 cartifacteditor.htm >--- concepts/cartifacteditor.htm 3 May 2007 14:33:15 -0000 1.5 >+++ concepts/cartifacteditor.htm 18 Apr 2008 16:02:18 -0000 >@@ -2,7 +2,7 @@ > <html lang="en-us" xml:lang="en-us"> > <!-- > /********************************************************************** >- * Copyright (c) 2006, 2007 Scapa Technologies and others. >+ * Copyright (c) 2006, 2008 Scapa Technologies and others. > * All rights reserved. This content is made available under > * the terms of the Eclipse Public License v1.0 > * which accompanies this distribution, and is available at >@@ -15,97 +15,89 @@ > **********************************************************************/ > --> > >- > <head> > <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" /> > <link rel="StyleSheet" href="../css/book.css" type="text/css" /> > >-<title>Artifact Editor - overview</title> >+<title>Editing an artifact</title> > </head> > > <body> > >+<h1>Editing an artifact</h1> > >-<h1>Artifact Editor - overview</h1> >+<p>Test artifacts are edited using the Artifact editor. The editor contains three tabs:</p> > >-<p> >-Test artifacts associate objects such as test suites and datapools; that is, >-artifacts make an asset available to a test suite. In the Artifact Editor, >-there are initially two main tabs: <b>Overview</b> and <b>Test Assets</b>. >-A third tab, <b>General Properties</b>, appears after the artifact has been associated with a JUnit test.</p> >- >-<p><img width="469" height="347" >- src="../images/creatingATestDeployment_image025.png" alt="" /></p> >-<h2>Overview Tab</h2> >- >-<p>The <i>General Information</i> section provides the artifact's name, description, and its >-path within the workspace.</p> >- >-<p>The <i>Test Assets</i> section shows the test elements associated with the artifact.</p> >- >-<p>The <i>Property Groups</i> section includes <i>General Properties</i>, and, if either >-of these is selected, this will instantiate an additional tab >-named <i>General Properties</i> with content.</p> >- >- >-<h2>Test Assets Tab</h2> >-<p>In the Overview tab, clicking on the <b>More...</b> button, or selecting the <b>Test Assets</b> tab, results in the <i>Test Assets</i> >-view being displayed. To add a test asset, click on the <b>Add...</b> button to bring up the Select Resource dialog. Navigate to a resource, select it, and click on <b>OK</b>. >-The resource (in this example a TPTP JUnit test named <i>SimpleTest.testsuite<b></b></i>) >-will be added to the Test Assets section.<b><br /> >-<img width="262" height="217" >- src="../images/creatingATestDeployment_image016.png" alt="" /></b></p><p>You can add or remove test assets by using the <b>Add...</b> >-or <b>Remove</b> buttons respectively. As we have seen, invoking <b>Add...</b> brings up the Select Resource dialog. To >-remove an asset, select it by clicking on it, then press the <b>Remove</b> button.</p> >- >-<p>When there is more than one asset in the Test Assets section, their relative ordering can be modified by selecting an item within the list and >-then pressing the <b>Up</b> or <b>Down</b> buttons to move the selected item up or down the list, respectively.</p> >- >-<p>If we return to the Overview tab view, we see that <i>SimpleTest</i> has been added >- to the <b>Test Assets</b> section. Apart from the JUnit test suite, the test assets >-should include any other resources required (for example, datapools).<br /> >-</p><h2>General Properties tab</h2> >-<p>The CLASSPATH is added to the <i>General Properties</i> section as a >-consequence of the artifact being associated with a JUnit test.</p> >- >-<p>In the <i>Overview</i> tab, either clicking on the <b>CLASSPATH </b>or the <b>More...</b> button in the <i>General Properties</i> section >-of the Overview tab, selecting <b>General Properties</b> in the <i>Property Groups</i> section, or selecting the <b>General Properties</b> tab, all >-result in the General Properties tab view being displayed.<br /> >-<img width="366" height="283" src="../images/creatingATestDeployment_image026.png" alt="" /></p> >- >-<p><b>Note</b> that, while it is possible to add in further properties to the General Properties section, TPTP itself uses only the <b>CLASSPATH</b> >-property. It may be that other applications can make use of additional properties, so, for completeness, we describe how to add, remove and edit such >-properties.</p> >- >-<p>To add a new property, click on the <b>Add...</b> button. This launches the <b>New Property</b> dialog.<br /> >-<img width="436" height="126" src="../images/creatingATestDeployment_image027.png" alt="" /></p> >- >-<p>Enter your property name in the <b>Property Name</b> field, or select it from the drop-down list.<br /> >-<img width="436" height="140" src="../images/creatingATestDeployment_image028.png" alt="" /></p> >- >-<p>Select the <b>Operator</b> from =, !=, >, <, >=, or <= via the associated drop-down list >- and insert the required value in the <b>Property Value</b> field.</p> >- >-<p>To edit an existing property, double-click on it to launch the <b>Edit >-Property</b> dialog.<br /> >-<img width="436" height="126" src="../images/creatingATestDeployment_image029.png" alt="" /></p> >+<h2>Overview</h2> > >-<p>Then change the <b>Property Name</b>, <b>Operator</b>, or <b>Property Value</b> fields as required.</p> >+<p>This tab provides an overview of the test artifact.</p> > >-<p>To remove an existing property, select it then click on the <b>Remove</b> button.</p> >+<p>This tab contains three sections:</p> > >-<p> >-<b>Related concepts</b><br/> >-<a href="cdeployeditor.htm">Deployment Editor - overview</a><br/> >-<a href="clocationeditor.htm">Location Editor - overview</a><br/> >-</p> >+<ul> >+ <li> >+ <p><b>General Information</b></p> >+ <p>Contains the test artifact's name, description, and file path within the workspace. The test artifact's name<sup>1</sup> and description are editable.</p> >+ <br/> >+ </li> >+ <li> >+ <p><b>Property Groups</b></p> >+ <p>Contains a link to the General Properties tab. Clicking the link will open the associated tab.</p> >+ <br/> >+ </li> >+ <li> >+ <p><b>Test Assets</b></p> >+ <p>Contains links to the test assets, such as test suites and datapools, in the Test Assets tab. Clicking a link or the More... button will >+ open the Test Assets tab.</p> >+ <br/> >+ </li> >+ <li> >+ <p><b>General Properties</b></p> >+ <p>Contains links to the general properties in the General Properties tab. Clicking a link or the More... button will >+ open the General Properties tab.</p> >+ <br/> >+ <p>Note, the General Properties section will only appear if one or more general properties are associated with the test artifact.</p> >+ <br/> >+ </li> >+</ul> >+ >+<p>[1] Test artifacts have a file name and logical name. The logical name is used in the Test Navigator, dialogs, editors, and wizards to represent the test artifact. >+The file name represents the test artifact file (<i>*.artifact</i>) within the workspace. When the test artifact is created, the logical name defaults to the file name >+(excluding the <i>.artifact</i> file extension) and may be modified without modifying the file name. The logical name allows customization of the test artifact name >+without affecting the file name within the workspace.</p> >+ >+<h2>Test Assets</h2> >+ >+<p>This tab contains the list of test assets, such as test suites and datapools, associated with the test artifact.</p> >+ >+<p>Test assets can be added to the list by clicking the <b>Add...</b> button and select the test assets.</p> >+ >+<p>Selected test assets can be removed (<b>Remove</b>), moved up (<b>Up</b>), or moved down (<b>Down</b>).</p> >+ >+<h2>General Properties</h2> >+ >+<p>This tab contains the table of general properties associated with the test artifact. For example, the <i>CLASSPATH</i> general property contains local dependencies of the associated test suites.</p> >+ >+<p>When a test suite is executed, the following dependencies are deployed to the target host:</p> >+ >+<ul> >+ <li>Dependencies on the class path of the project containing the test suite, excluding <i>*.java</i>, <i>*.execution</i>, <i>*.testsuite</i>, <i>*.deploy</i>, <i>*.location</i>, and <i>*.artifact</i>.</li> >+ <li>Dependencies on the <i>CLASSPATH</i> general property.</li> >+ <li>Test assets associated with the test artifact.</li> >+</ul> >+ >+<p>Note, the General Properties tab will only appear if one or more general properties are associated with the test artifact.</p> >+ >+<p>General properties can be added to the table by clicking the <b>Add...</b> button and entering the property name, operator (<i>=</i>, <i>!=</i>, <i>></i>, <i><</i>, <i>>=</i>, or <i><=</i>), and value.</p> >+ >+<p>All file paths are absolute and operating system dependent based on the local operating system.</p> >+ >+<p>Selected general properties can be removed (<b>Remove</b>), moved up (<b>Up</b>), or moved down (<b>Down</b>). Existing general properties may be edited by double-clicking >+the general property in the table and and modifying the property name, operator, and/or value.</p> > > <p> > <b>Related tasks</b><br/> > <a href="../tasks/tcreateartifact.htm">Creating an artifact</a><br/> >-<a href="../tasks/tcreatetestdeployment.htm">Creating a deployment</a><br/> >-<a href="../tasks/tcreatelocation.htm">Creating a location</a><br/> >-<a href="../tasks/tassociateartifact.htm">Forming an artifact and location pairing</a><br/> > </p> > > </body> >Index: concepts/clocationeditor.htm >=================================================================== >RCS file: /cvsroot/tptp/test/org.eclipse.hyades.test.doc.user/concepts/clocationeditor.htm,v >retrieving revision 1.5 >diff -u -r1.5 clocationeditor.htm >--- concepts/clocationeditor.htm 3 May 2007 14:33:15 -0000 1.5 >+++ concepts/clocationeditor.htm 18 Apr 2008 16:02:18 -0000 >@@ -2,7 +2,7 @@ > <html lang="en-us" xml:lang="en-us"> > <!-- > /********************************************************************** >- * Copyright (c) 2006, 2007 Scapa Technologies and others. >+ * Copyright (c) 2006, 2008 Scapa Technologies and others. > * All rights reserved. This content is made available under > * the terms of the Eclipse Public License v1.0 > * which accompanies this distribution, and is available at >@@ -15,65 +15,96 @@ > **********************************************************************/ > --> > >- > <head> > <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" /> > <link rel="StyleSheet" href="../css/book.css" type="text/css" /> > >-<title>Location Editor - overview</title> >+<title>Editing a location</title> > </head> > > <body> > >+<h1>Editing a location</h1> > >-<h1>Location Editor - overview</h1> >-<p> >-Test locations identify the computer where the test suite will run. >-</p> >- >-<p> >-<img width="473" height="392" src="../images/creatingATestDeployment_image018.png" alt="" /></p><p>There are 3 tabs: <b>Overview</b>, <b>General >-Properties</b>, and <b>Eclipse Workbench Properties</b>. The above screen capture shows the <i>Overview</i> tab information.</p> >- >-<h3><a name="_Toc115944873"></a><a name="_Toc116098740"><b> Overview Tab</b></a></h3> >- >-<p>The <i>General Information</i> section provides the location's name (<b>testLocation</b> here), Description ('A sample >-location'), its path within the workspace (/java_01/testLocation.location), and the Host name (<b>localhost</b>).</p> >+<p>Test locations are edited using the Location editor. The editor contains three tabs:</p> > >-<p>The default host name for the location is <kbd><b>localhost</b></kbd>. If the intention is to run on another computer, enter the name of that >-computer in the <b>Host name</b> field.</p> >+<h2>Overview</h2> > >-<p>Property Groups references <i>General Properties </i>and<i> Eclipse Workbench Properties</i> sections, which are also separately shown on the >-right-hand side of the Location editor overview tab view. Each references respectively the <i>General Properties</i> and<i> Eclipse Workbench >-Properties</i> tabs. both reference the <b>General Properties</b> tab. Clicking on the <b>More...</b> button in either the <i>General >-Properties</i> or <i>Eclipse Workbench Properties</i> sections switches to their respective tab views.</p> >+<p>This tab provides an overview of the test location.</p> > >-<h3><a name="_Toc116098741"><b>Eclipse Workbench Properties</b></a></h3> >+<p>This tab contains three sections:</p> >+ >+<ul> >+ <li> >+ <p><b>General Information</b></p> >+ <p>Contains the test location's name, description, file path within the workspace, and host name or IP address. The test location's name<sup>1</sup>, description, and host name or IP address are editable.</p> >+ <br/> >+ <p>The connection to the target host may be tested by clicking the <b>Test Connection</b> link<sup>2</sup>.</p> >+ <br/> >+ </li> >+ <li> >+ <p><b>Property Groups</b></p> >+ <p>Contains a link to the General Properties and Eclipse Workbench Properties tab. Clicking a link will open the associated tab.</p> >+ <br/> >+ </li> >+ <li> >+ <p><b>Eclipse Workbench Properties</b></p> >+ <p>Contains links to the Eclipse Workbench properties in the Eclipse Workbench Properties tab. Clicking a link or the More... button will >+ open the Eclipse Workbench Properties tab.</p> >+ <br/> >+ <p>Note, the Eclipse Workbench Properties section will only appear if one or more Eclipse Workbench properties are associated with the test location.</p> >+ <br/> >+ </li> >+ <li> >+ <p><b>General Properties</b></p> >+ <p>Contains links to the general properties in the General Properties tab. Clicking a link or the More... button will >+ open the General Properties tab.</p> >+ <br/> >+ <p>Note, the General Properties section will only appear if one or more general properties are associated with the test location.</p> >+ <br/> >+ </li> >+</ul> >+ >+<p>[1] Test locations have a file name and logical name. The logical name is used in the Test Navigator, dialogs, editors, and wizards to represent the test location. >+The file name represents the test location file (<i>*.location</i>) within the workspace. When the test location is created, the logical name defaults to the file name >+(excluding the <i>.location</i> file extension) and may be modified without modifying the file name. The logical name allows customization of the test location name >+without affecting the file name within the workspace.</p> >+ >+<p>[2] The <a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/concepts/ac/c_ac_ovr.html">Agent Controller</a> or >+<a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/concepts/ac/ciacintro.html">Integrated Agent Controller</a> >+(local host only) is required to be configured and running.</p> >+ >+<h2>General Properties</h2> >+ >+<p>This tab contains the table of general properties associated with the test location. For example, the <i>CLASSPATH</i> general property contains >+dependencies on the target host.</p> >+ >+<p>In addition, the <i>ROOTDIR</i> general property contains absolute path of the directory on the target host where >+the dependencies configured in <a href="../concepts/cartifacteditor.htm">Artifact editor</a> are deployed when a test suite is executed. If the >+<i>ROOTDIR</i> general property is not provided or invalid for the target host, the dependencies are deployed to a temporary directory on the target host.</p> >+ >+<p>Note, the General Properties tab will only appear if one or more general properties are associated with the test location.</p> >+ >+<p>General properties can be added to the table by clicking the <b>Add...</b> button and entering the property name, operator (<i>=</i>, <i>!=</i>, <i>></i>, <i><</i>, <i>>=</i>, or <i><=</i>), and value.</p> >+ >+<p>All file paths are absolute and operating system dependent based on the target operating system.</p> >+ >+<p>Selected general properties can be removed (<b>Remove</b>), moved up (<b>Up</b>), or moved down (<b>Down</b>). Existing general properties may be edited by double-clicking >+the general property in the table and and modifying the property name, operator, and/or value.</p> > >-<p>This is concerned with the setting of properties relating to the deployment of a TPTP JUnit Plug-in Test. It is covered in the help documentation >-describing TPTP JUnit Plug-in Test.</p> >+<h2>Eclipse Workbench Properties</h2> > >-<h3><a name="_Toc116098742"><b>General Properties</b></a></h3> >+<p>This tab contains the table of Eclipse Workbench properties associated with the test location, as defined in the <a href="../../org.eclipse.pde.doc.user/guide/tools/preference_pages/target_platform.htm">Target Platform</a>.</p> > >-<p> >-The functionality available here is identical to that described for the <b>General Properties</b> tab in the Artifact Editor. >-</p> >+<p>Note, the Eclipse Workbench Properties tab will only appear if one or more Eclipse Workbench properties are associated with the test location.</p> > >-<p> >-<b>Related concepts</b><br/> >-<a href="cartifacteditor.htm">Artifact Editor - overview</a><br/> >-<a href="cdeployeditor.htm">Deployment Editor - overview</a><br/> >-</p> >+<p>All file paths are absolute and operating system dependent based on the target operating system.</p> > > <p> > <b>Related tasks</b><br/> >-<a href="../tasks/tcreateartifact.htm">Creating an artifact</a><br/> >-<a href="../tasks/tcreatetestdeployment.htm">Creating a deployment</a><br/> > <a href="../tasks/tcreatelocation.htm">Creating a location</a><br/> >-<a href="../tasks/tassociateartifact.htm">Forming an artifact and location pairing</a><br/> > </p> > >- > </body> > > </html> >Index: concepts/cdeployeditor.htm >=================================================================== >RCS file: /cvsroot/tptp/test/org.eclipse.hyades.test.doc.user/concepts/cdeployeditor.htm,v >retrieving revision 1.5 >diff -u -r1.5 cdeployeditor.htm >--- concepts/cdeployeditor.htm 3 May 2007 14:33:15 -0000 1.5 >+++ concepts/cdeployeditor.htm 18 Apr 2008 16:02:18 -0000 >@@ -2,7 +2,7 @@ > <html lang="en-us" xml:lang="en-us"> > <!-- > /********************************************************************** >- * Copyright (c) 2006, 2007 Scapa Technologies and others. >+ * Copyright (c) 2006, 2008 Scapa Technologies and others. > * All rights reserved. This content is made available under > * the terms of the Eclipse Public License v1.0 > * which accompanies this distribution, and is available at >@@ -15,55 +15,96 @@ > **********************************************************************/ > --> > >- > <head> > <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" /> > <link rel="StyleSheet" href="../css/book.css" type="text/css" /> > >-<title>Deployment Editor - overview</title> >+<title>Editing a deployment</title> > </head> > > <body> > >+<h1>Editing a deployment</h1> > >-<h1>Deployment Editor - overview</h1> >-<p> >-The Deployment editor associates test artifacts with test locations. >-There are 2 main tabs in the editor: <b>Overview</b> and <b>Pairs</b>. >-</p> >- >-<h2>Overview Tab</h2> >- >-<p>The <i>General Information</i> section provides the deployment's name, description, >-and its path within the workspace.</p> >- >-<p>The <b>Artifacts</b> and <b>Locations</b> sections are subsequently >-associated with the deployment.</p> >-<p><img border="1" src="../images/deploy_editor.gif" width="492" >- height="423" alt=""/></p> >- >-<h2>Pairs Tab</h2> >+<p>Test deployments are edited using the Deployment editor. The editor contains three tabs:</p> > >-The <i>Pairs</i> tab is used to add Artifacts and Locations and to form Artifact Location pairs. <br /> >-<img border="0" src="../images/creatingATestDeployment_image010.gif" >- width="514" height="358" alt=""/> >+<h2>Overview</h2> > >-<h2>Locations</h2> >+<p>This tab provides an overview of the test deployment.</p> > >-<p>The functionality available here is identical to that described for the <b>General Properties</b> tab in the artifact editor.</p> >- >-<p> >-<b>Related concepts</b><br/> >-<a href="cartifacteditor.htm">Artifact Editor - overview</a><br/> >-<a href="clocationeditor.htm">Location Editor - overview</a><br/> >-</p> >+<p>This tab contains three sections:</p> >+ >+<ul> >+ <li> >+ <p><b>General Information</b></p> >+ <p>Contains the test deployment's name, description, and file path within the workspace. The test deployment's name<sup>1</sup> and description are editable.</p> >+ <br/> >+ </li> >+ <li> >+ <p><b>Test Artifacts</b></p> >+ <p>Contains links to the test artifacts in the Pairs tab. Clicking a link or the More... button will open the Pairs tab.</p> >+ <br/> >+ </li> >+ <li> >+ <p><b>Test Locations</b></p> >+ <p>Contains links to the test locations in the Pairs tab. Clicking a link or the More... button will open the Pairs tab.</p> >+ <br/> >+ </li> >+ <li> >+ <p><b>Test</b></p> >+ <p>Contains the test suites associated with the test artifacts.</p> >+ <br/> >+ </li> >+</ul> >+ >+<p>[1] Test deployments have a file name and logical name. The logical name is used in the Test Navigator, dialogs, editors, and wizards to represent the test deployment. >+The file name represents the test deployment file (<i>*.deploy</i>) within the workspace. When the test deployment is created, the logical name defaults to the file name >+(excluding the <i>.deploy</i> file extension) and may be modified without modifying the file name. The logical name allows customization of the test deployment name >+without affecting the file name within the workspace.</p> >+ >+<h2>Pairs</h2> >+ >+<p>This tab pairs test artifacts and test locations for executing a test suite.</p> >+ >+<p>This tab contains three sections:</p> >+ >+<ul> >+ <li> >+ <p><b>Artifacts</b></p> >+ <p>Contains the test artifacts associated with the test deployment.</p> >+ <br/> >+ <p>Test artifacts can be added to the list by clicking the <b>Add...</b> button and selecting the test artifacts or creating a <a href="../tasks/tcreateartifact.htm">new test artifact</a>.</p> >+ <br/> >+ <p>Selected test artifacts can be removed (<b>Remove</b>), moved up (<b>Up</b>), moved down (<b>Down</b>), or opened in the Artifact editor (<b>Open...</b>).</p> >+ <br/> >+ </li> >+ <li> >+ <p><b>Locations</b></p> >+ <p>Contains the test locations associated with the test deployment.</p> >+ <br/> >+ <p>Test locations can be added to the list by clicking the <b>Add...</b> button and selecting the test locations or creating a <a href="../tasks/tcreatelocation.htm">new test location</a>.</p> >+ <br/> >+ <p>Selected test locations can be removed (<b>Remove</b>), moved up (<b>Up</b>), moved down (<b>Down</b>), or opened in the Location editor (<b>Open...</b>).</p> >+ <br/> >+ </li> >+ <li> >+ <p><b>Artifact Location Pairs</b></p> >+ <br/> >+ <p>Contains the pairs test artifacts and test locations for executing a test suite.</p> >+ <br/> >+ <p>Create pairs of test artifacts and test locations by selecting a test artifact in the Artifacts list and a test location in the Locations list and clicking the down-arrow button (<img border="0" >+ src="../images/downArrow.gif" width="16" height="16" alt="Image of down arrow."/>).</p> >+ <br/> >+ <p>Selected pairs of test artifacts and test locations can be removed (<b>Remove</b>), moved up (<b>Up</b>), or moved down (<b>Down</b>).</p> >+ <br/> >+ </li> >+</ul> > > <p> > <b>Related tasks</b><br/> > <a href="../tasks/tcreateartifact.htm">Creating an artifact</a><br/> >-<a href="../tasks/tcreatetestdeployment.htm">Creating a deployment</a><br/> > <a href="../tasks/tcreatelocation.htm">Creating a location</a><br/> >-<a href="../tasks/tassociateartifact.htm">Forming an artifact and location pairing</a><br/> >+<a href="../tasks/tcreatetestdeployment.htm">Creating a deployment</a><br/> > </p> > > </body> >Index: tasks/tcreatetestdeployment.htm >=================================================================== >RCS file: /cvsroot/tptp/test/org.eclipse.hyades.test.doc.user/tasks/tcreatetestdeployment.htm,v >retrieving revision 1.4 >diff -u -r1.4 tcreatetestdeployment.htm >--- tasks/tcreatetestdeployment.htm 3 May 2007 14:33:15 -0000 1.4 >+++ tasks/tcreatetestdeployment.htm 18 Apr 2008 16:02:18 -0000 >@@ -2,7 +2,7 @@ > <html lang="en-us" xml:lang="en-us"> > <!-- > /********************************************************************** >- * Copyright (c) 2006, 2007 Scapa Technologies and others. >+ * Copyright (c) 2006, 2008 Scapa Technologies and others. > * All rights reserved. This content is made available under > * the terms of the Eclipse Public License v1.0 > * which accompanies this distribution, and is available at >@@ -23,36 +23,40 @@ > > <body> > >- > <h1>Creating a deployment</h1> >-<p> >-Test deployments typically consist of a paired test artifact and test location. >-Through the launch configuration mechanism, >-TPTP interprets the pair and deploys the test artifacts on the host computer >-specified. >-</p> > >-Create the deployment by following these steps: >+<p>Test deployments pair test artifacts and test locations for executing a test suite.</p> >+ >+<p>Create a test deployment:</p> >+ > <ol> >- <li>Right-click in the <b>Test Navigator</b> and select <b>New</b> > <b>Test Element...</b> The New wizard opens.</li> >- <li>Expand <b>Test Assets</b> and select <b>Deployment </b>then click on <b>Next</b> to open the <b>New Deployment </b>dialog.</li> >- <li>Select the parent folder and enter the deployment name, <i>testDeployment</i>. Click on <b>Next</b> and optionally enter a description >- for the deployment.</li> >- <li>Click on <b>Finish</b>. The <b>Deployment editor</b> launches.</li> >+ <li>Right-click in the Test Navigator and select <b>New</b> > <b>Test Element...</b>.</li> >+ <li>Select <b>Test Assets</b> > <b>Deployment</b> and click <b>Next</b>.</li> >+ <li>Provide the parent folder and the name for the test deployment and click <b>Next</b>.</li> >+ <li>Optionally, provide a description for the test deployment and click <b>Next</b>.</li> >+ <li>Select or create the associated test artifacts by clicking the <b>New...</b> button and >+ selecting the test artifacts or creating a <a href="tcreateartifact.htm">new test artifact</a>. >+ Selected test artifacts can be removed (<b>Remove</b>), moved up (<b>Up</b>), or moved down (<b>Down</b>).</li> >+ <li>Click <b>Next</b>.</li> >+ <li>Select or create the associated test locations by clicking the <b>New...</b> button and >+ selecting the test locations or creating a <a href="tcreatelocation.htm">new test location</a>. >+ Selected test locations can be removed (<b>Remove</b>), moved up (<b>Up</b>), or moved down (<b>Down</b>).</li> >+ <li>Click <b>Next</b>.</li> >+ <li>Create pairs of test artifacts and test locations by selecting a test artifact and test location and clicking the down-arrow button (<img border="0" >+ src="../images/downArrow.gif" width="16" height="16" alt="Image of down arrow."/>). Selected pairs of test artifacts and test locations can be removed >+ (<b>Remove</b>), moved up (<b>Up</b>), or moved down (<b>Down</b>).</li> >+ <li>Click <b>Finish</b> to create the test deployment.</li> > </ol> > > <p> > <b>Related concepts</b><br/> >-<a href="../concepts/cartifacteditor.htm">Artifact Editor - overview</a><br/> >-<a href="../concepts/cdeployeditor.htm">Deployment Editor - overview</a><br/> >-<a href="../concepts/clocationeditor.htm">Location Editor - overview</a><br/> >+<a href="../concepts/cdeployeditor.htm">Editing a deployment</a><br/> > </p> > > <p> > <b>Related tasks</b><br/> > <a href="tcreateartifact.htm">Creating an artifact</a><br/> > <a href="tcreatelocation.htm">Creating a location</a><br/> >-<a href="tassociateartifact.htm">Forming an artifact and location pairing</a><br/> > </p> > > </body> >Index: tasks/tdeploymentintro.htm >=================================================================== >RCS file: /cvsroot/tptp/test/org.eclipse.hyades.test.doc.user/tasks/tdeploymentintro.htm,v >retrieving revision 1.4 >diff -u -r1.4 tdeploymentintro.htm >--- tasks/tdeploymentintro.htm 3 May 2007 14:33:14 -0000 1.4 >+++ tasks/tdeploymentintro.htm 18 Apr 2008 16:02:18 -0000 >@@ -2,7 +2,7 @@ > <html lang="en-us" xml:lang="en-us"> > <!-- > /********************************************************************** >- * Copyright (c) 2006, 2007 Scapa Technologies and others. >+ * Copyright (c) 2006, 2008 Scapa Technologies and others. > * All rights reserved. This content is made available under > * the terms of the Eclipse Public License v1.0 > * which accompanies this distribution, and is available at >@@ -26,49 +26,31 @@ > > <h1>Creating a test deployment</h1> > >-<p>This section describes how to create a deployment for your test suite. The example is set within the context of the Test perspective. >-We shall execute the following steps:</p> >+<p>This section describes creating and editing test artifacts, locations, and deployments for executing a test suite.</p> > > <ul> > <li> >- <a href="tcreatetestdeployment.htm">Creating a deployment</a> >- <p> >- Test deployments typically consist of a paired test artifact and test location. >- Through the launch configuration mechanism, >- TPTP interprets the pair and deploys the test artifacts on the host computer >- specified. >- </p> >- <br/> >- </li> >- <li> > <a href="tcreateartifact.htm">Creating an artifact</a> >- <p> >- Test artifacts associate objects such as test suites and datapools; that is, >- artifacts make an asset available to a test suite. >- </p> >+ <p>Test artifacts associate test assets, such as test suites and datapools, with a test deployment.</p> > <br/> > </li> > <li> > <a href="tcreatelocation.htm">Creating a location</a> >- <p> >- Test locations identify the computer where the test suite will run. >- </p> >+ <p>Test locations associate a target host with a test deployment.</p> > <br/> > </li> > <li> >- <a href="tassociateartifact.htm">Forming an artifact and location pairing</a> >- <p> >- Create the pair of test artifact and location to be used by the test deployment. >- </p> >+ <a href="tcreatetestdeployment.htm">Creating a deployment</a> >+ <p>Test deployments pair test artifacts and test locations for executing a test suite.</p> > <br/> > </li> > </ul> > > <p> > <b>Related concepts</b><br/> >-<a href="../concepts/cartifacteditor.htm">Artifact Editor - overview</a><br/> >-<a href="../concepts/cdeployeditor.htm">Deployment Editor - overview</a><br/> >-<a href="../concepts/clocationeditor.htm">Location Editor - overview</a><br/> >+<a href="../concepts/cartifacteditor.htm">Editing an artifact</a><br/> >+<a href="../concepts/clocationeditor.htm">Editing a location</a><br/> >+<a href="../concepts/cdeployeditor.htm">Editing a deployment</a><br/> > </p> > > </body> >Index: tasks/trun.htm >=================================================================== >RCS file: /cvsroot/tptp/test/org.eclipse.hyades.test.doc.user/tasks/trun.htm,v >retrieving revision 1.11 >diff -u -r1.11 trun.htm >--- tasks/trun.htm 3 May 2007 14:33:15 -0000 1.11 >+++ tasks/trun.htm 18 Apr 2008 16:02:18 -0000 >@@ -74,7 +74,7 @@ > > <p> > <b>Related concepts</b><br/> >-<a href="../concepts/cdeployeditor.htm">Deployment Editor - overview</a><br/> >+<a href="../concepts/cdeployeditor.htm">Editing a deployment</a><br/> > </p> > > <p> >Index: tasks/tcreateartifact.htm >=================================================================== >RCS file: /cvsroot/tptp/test/org.eclipse.hyades.test.doc.user/tasks/tcreateartifact.htm,v >retrieving revision 1.5 >diff -u -r1.5 tcreateartifact.htm >--- tasks/tcreateartifact.htm 3 May 2007 14:33:14 -0000 1.5 >+++ tasks/tcreateartifact.htm 18 Apr 2008 16:02:18 -0000 >@@ -2,7 +2,7 @@ > <html lang="en-us" xml:lang="en-us"> > <!-- > /********************************************************************** >- * Copyright (c) 2006, 2007 IBM Corporation. >+ * Copyright (c) 2006, 2008 IBM Corporation. > * All rights reserved. This content is made available under > * the terms of the Eclipse Public License v1.0 > * which accompanies this distribution, and is available at >@@ -22,51 +22,31 @@ > > <body> > >- > <h1>Creating an artifact</h1> >-<p> >-Test artifacts associate objects such as test suites and datapools; that is, >-artifacts make an asset available to a test suite. >-</p> > >-<p>Repeat the same sequence of steps as for creating a deployment but this time >-create an artifact named <i>testArtifact</i>.</p> >+<p>Test artifacts associate test assets, such as test suites and datapools, with a test deployment.</p> >+ >+<p>Create a test artifact:</p> > > <ol> >- <li> >- Right-click in the <b>Test Navigator</b> and select <b>New</b> > <b>Test Element...</b> >- </li> >- <li> >- Open <b>Test Assets</b> and select <b>Artifact</b>. >- </li> >- <li> >- Click on <b>Next</b> to open the <b>New Artifact</b> dialog. >- </li> >- <li> >- Select the parent folder and enter the artifact name (<i>testArtifact</i>). >- </li> >- <li> >- Click on <b>Next</b> and optionally enter a description for the artifact. >- </li> >- <li> >- Click on <b>Finish</b>. The <b>Artifact editor</b> opens.</li> >+ <li>Right-click in the Test Navigator and select <b>New</b> > <b>Test Element...</b>.</li> >+ <li>Select <b>Test Assets</b> > <b>Artifact</b> and click <b>Next</b>.</li> >+ <li>Provide the parent folder and the name for the test artifact and click <b>Next</b>.</li> >+ <li>Optionally, provide a description for the test artifact and click <b>Next</b>.</li> >+ <li>Select the associated test assets, such as test suites and datapools.</li> >+ <li>Click <b>Finish</b> to create the test artifact.</li> > </ol> > > <p> > <b>Related concepts</b><br/> >-<a href="../concepts/cartifacteditor.htm">Artifact Editor - overview</a><br/> >-<a href="../concepts/cdeployeditor.htm">Deployment Editor - overview</a><br/> >-<a href="../concepts/clocationeditor.htm">Location Editor - overview</a><br/> >+<a href="../concepts/cartifacteditor.htm">Editing an artifact</a><br/> > </p> > > <p> > <b>Related tasks</b><br/> > <a href="tcreatetestdeployment.htm">Creating a deployment</a><br/> >-<a href="tcreatelocation.htm">Creating a location</a><br/> >-<a href="tassociateartifact.htm">Forming an artifact and location pairing</a><br/> > </p> > >- > </body> > > </html> >Index: tasks/tcreatelocation.htm >=================================================================== >RCS file: /cvsroot/tptp/test/org.eclipse.hyades.test.doc.user/tasks/tcreatelocation.htm,v >retrieving revision 1.5 >diff -u -r1.5 tcreatelocation.htm >--- tasks/tcreatelocation.htm 3 May 2007 14:33:15 -0000 1.5 >+++ tasks/tcreatelocation.htm 18 Apr 2008 16:02:18 -0000 >@@ -2,7 +2,7 @@ > <html lang="en-us" xml:lang="en-us"> > <!-- > /********************************************************************** >- * Copyright (c) 2006, 2007 Scapa Technologies and others. >+ * Copyright (c) 2006, 2008 Scapa Technologies and others. > * All rights reserved. This content is made available under > * the terms of the Eclipse Public License v1.0 > * which accompanies this distribution, and is available at >@@ -23,60 +23,37 @@ > > <body> > >- > <h1>Creating a location</h1> >-<p> >-Test locations identify the computer where the test suite will run. >-</p> > >-<p> >-Repeat the same sequence of steps as for creating a deployment but for this >-example create a location named <b>testLocation</b>. >-</p> >+<p>Test locations associate a target host with a test deployment. The test suite will be executed >+on the target host specified in the test location.</p> >+ >+<p>Create a test location:</p> > > <ol> >- <li> >- Right-click in the <b>Test Navigator</b> and select >- <b>New</b> > <b>Test Element...</b> >- </li> >- <li> >- Open <b>Test Assets</b> and select <b>Location</b>. >- </li> >- <li> >- Click on <b>Next</b> to open the <b>New Location</b> dialog. >- </li> >- <li> >- Select the parent folder and enter the artifact name (<i>testLocation</i>). >- </li> >- <li> >- Click on <b>Next</b> and optionally enter a description for the location. >- </li> >- <li> >- Click <b>Finish</b>. The <i>Location editor</i> opens. >- </li> >+ <li>Right-click in the Test Navigator and select <b>New</b> > <b>Test Element...</b>.</li> >+ <li>Select <b>Test Assets</b> > <b>Location</b> and click <b>Next</b>.</li> >+ <li>Provide the parent folder and the name for the test location and click <b>Next</b>.</li> >+ <li>Optionally, provide a description for the test location and click <b>Next</b>.</li> >+ <li>Enter the host name or IP address of the target host. By default, <i>localhost</i> is entered. Test the >+ connection to the target host by clicking the <b>Test Connection</b> link<sup>1</sup>.</li> >+ <li>Click <b>Finish</b> to create the test location.</li> > </ol> > >-<p>If the intention is to run tests on another computer, the name of that computer must be entered in the <b>H</b><b>ost name</b> field >-of the relevant location.</p> >- >-<p>Where a TPTP JUnit Test is being deployed remotely, there are a number of other considerations to take into account. These are covered in >-the documentation relating to TPTP JUnit Test.</p> >- >+<p>[1] The <a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/concepts/ac/c_ac_ovr.html">Agent Controller</a> or >+<a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/concepts/ac/ciacintro.html">Integrated Agent Controller</a> >+(local host only) is required to be configured and running.</p> >+ > <p> > <b>Related concepts</b><br/> >-<a href="../concepts/cartifacteditor.htm">Artifact Editor - overview</a><br/> >-<a href="../concepts/cdeployeditor.htm">Deployment Editor - overview</a><br/> >-<a href="../concepts/clocationeditor.htm">Location Editor - overview</a><br/> >+<a href="../concepts/clocationeditor.htm">Editing a location</a><br/> > </p> > > <p> > <b>Related tasks</b><br/> > <a href="tcreatetestdeployment.htm">Creating a deployment</a><br/> >-<a href="tcreateartifact.htm">Creating an artifact</a><br/> >-<a href="tassociateartifact.htm">Forming an artifact and location pairing</a><br/> > </p> > >- > </body> > > </html> >Index: tasks/tcreateperformancetestreports.htm >=================================================================== >RCS file: /cvsroot/tptp/test/org.eclipse.hyades.test.doc.user/tasks/tcreateperformancetestreports.htm,v >retrieving revision 1.4 >diff -u -r1.4 tcreateperformancetestreports.htm >--- tasks/tcreateperformancetestreports.htm 16 Apr 2008 14:50:23 -0000 1.4 >+++ tasks/tcreateperformancetestreports.htm 18 Apr 2008 16:02:18 -0000 >@@ -66,24 +66,24 @@ > </tbody> > </table> > >-[1] Adobe's <a href="http://www.adobe.com/svg/viewer/install/main.html">Scalable Vector Graphics (SVG)</a> browser plug-in is required. >+<p>[1] Adobe's <a href="http://www.adobe.com/svg/viewer/install/main.html">Scalable Vector Graphics (SVG)</a> browser plug-in is required.</p> > >-<p>Configure the fonts used when generating the performance test report:</p> >+<p>Configure the fonts used when generating a performance test report:</p> > <ol> >- <li>Open the <b>Window > Preferences</b> dialog.</li> >- <li>Select the report <b>Test > Test Report > Font</b> preference page.</li> >- <li>Configure the fonts used when generating the performance test report.</li> >- <li>Select <b>OK</b>.</li> >+ <li>Select <b>Window</b> > <b>Preferences...</b> from the file menu.</li> >+ <li>Select the report <b>Test</> > <b>Test Reports<b> > <b>Fonts</b> preference page.</li> >+ <li>Configure the fonts used when generating a performance test report.</li> >+ <li>Click <b>OK</b> to save the preferences.</li> > </ol> > >-<p>Generate the performance test report:</p> >+<p>Generate a performance test report:</p> > <ol> >- <li>Right-click on a performance test suite in the Test Navigator and select <strong>Report... </strong> from the context menu.</li> >- <li>The <strong>New Report</strong> dialog opens.</li> >- <li>Select one of the performance test report types and click on <strong>Next </strong>.</li> >- <li>Provide the parent folder and a name for the performance test report, then click on <strong>Next</strong>.</li> >+ <li>Right-click on a performance test suite in the Test Navigator and select <b>Report... </b>.</li> >+ <li>Select one of the performance test report types and click <b>Next </b>.</li> >+ <li>Provide the parent folder and the name for the performance test report and click <b>Next</b>.</li> > <li>Optionally, provide the report window (start and end data and time) for the performance test report.</li> >- <li>Click <strong>Finish </strong> to generate the performance test report.</li> >+ <li>Click <b>Finish </b> to generate the performance test report.</li> > </ol> >+ > </body> > </html> >Index: tasks/tcreatetestreports.htm >=================================================================== >RCS file: /cvsroot/tptp/test/org.eclipse.hyades.test.doc.user/tasks/tcreatetestreports.htm,v >retrieving revision 1.3 >diff -u -r1.3 tcreatetestreports.htm >--- tasks/tcreatetestreports.htm 11 Apr 2008 18:43:23 -0000 1.3 >+++ tasks/tcreatetestreports.htm 18 Apr 2008 16:02:18 -0000 >@@ -56,24 +56,24 @@ > </tbody> > </table> > >-[1] Adobe's <a href="http://www.adobe.com/svg/viewer/install/main.html">Scalable Vector Graphics (SVG)</a> browser plug-in is required. >+<p>[1] Adobe's <a href="http://www.adobe.com/svg/viewer/install/main.html">Scalable Vector Graphics (SVG)</a> browser plug-in is required.</p> > >-<p>Configure the fonts used when generating the test report:</p> >+<p>Configure the fonts used when generating a test report:</p> > <ol> >- <li>Open the <b>Window > Preferences</b> dialog.</li> >- <li>Select the report <b>Test > Test Report > Font</b> preference page.</li> >- <li>Configure the fonts used when generating the test report.</li> >- <li>Select <b>OK</b>.</li> >+ <li>Select <b>Window</b> > <b>Preferences...</b> from the file menu.</li> >+ <li>Select the report <b>Test</> > <b>Test Reports<b> > <b>Fonts</b> preference page.</li> >+ <li>Configure the fonts used when generating a test report.</li> >+ <li>Click <b>OK</b> to save the preferences.</li> > </ol> > >-<p>Generate the test report:</p> >+<p>Generate a test report:</p> > <ol> >- <li>Right-click on a test suite in the Test Navigator and select <strong>Report... </strong> from the context menu.</li> >- <li>The <strong>New Report</strong> dialog opens.</li> >- <li>Select one of the test report types and click on <strong>Next </strong>.</li> >- <li>Provide the parent folder and a name for the test report, then click on <strong>Next</strong>.</li> >+ <li>Right-click on a test suite in the Test Navigator and select <b>Report... </b>.</li> >+ <li>Select one of the test report types and click <b>Next </b>.</li> >+ <li>Provide the parent folder and the name for the test report and click <b>Next</b>.</li> > <li>Optionally, provide the report window (start and end data and time) for the test report.</li> >- <li>Click <strong>Finish </strong> to generate the test report.</li> >+ <li>Click <b>Finish </b> to generate the test report.</li> > </ol> >+ > </body> > </html> >Index: tasks/tassociateartifact.htm >=================================================================== >RCS file: tasks/tassociateartifact.htm >diff -N tasks/tassociateartifact.htm >--- tasks/tassociateartifact.htm 3 May 2007 14:33:14 -0000 1.7 >+++ /dev/null 1 Jan 1970 00:00:00 -0000 >@@ -1,108 +0,0 @@ >-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"> >-<html lang="en-us" xml:lang="en-us"> >-<!-- >-/********************************************************************** >- * Copyright (c) 2006, 2007 Scapa Technologies and others. >- * All rights reserved. This content is 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 >- * $Id: tassociateartifact.htm,v 1.7 2007/05/03 14:33:14 paules Exp $ >- * >- * Contributors: >- * Scapa Technologies - Initial contribution >- * IBM - updates >- **********************************************************************/ >- --> >- >-<head> >-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" /> >-<link rel="StyleSheet" href="../css/book.css" type="text/css" /> >- >-<title>Forming an artifact and location pairing</title> >-</head> >- >-<body> >- >- >-<h1>Forming an artifact and location pairing</h1> >-<p> >-Create the pair of test artifact and location to be used by the test >-deployment. >-</p> >- >-<p>If the <b>Deployment editor</b> is not already open, open it by double-clicking on <i>testDeployment.deploy</i>. Select >-the <b>Pairs</b> tab.<br /> >-<img width="474" height="428" src="../images/creatingATestDeployment_image019.png" alt="" /></p><p></p> >- >-<h3>Adding the Artifact</h3> >- >-<ol> >- <li> >- Click the <b>Add...</b> button adjacent to the <b>Artifacts </b>section. The <b>Add Artifact Association</b> dialog launches.</li> >- <li>Select the <b>Use an existing resource</b> option. Either type in the path >- reference for <i>testArtifact</i> in the <b>Existing resource</b> field, or use >- the <b>Browse...</b> button to navigate to it and select it. >- </li> >- <li> >- Click <b>Finish</b>. The artifact will be added to the list in the <b>Artifacts</b> section. >- </li> >-</ol><h3>Adding the Location</h3> >- >-<p>This follows a similar process to that for adding an artifact. >-<ol> >- <li> >- Click on the <b>Add...</b> button adjacent to the <b>Locations </b>section. >- The <b>Add Location Association</b> dialog launches. >- </li> >- <li>Select the <b>Use an existing resource</b> >- option and either type in the path reference for <i>testLocation</i> in the >- <b>Existing resource</b> field, or use the <b>Browse...</b> button to navigate to >- it and select it. >- </li> >- <li> >- Click <b>Finish</b>. The location will be added to the list in the <b>Locations</b> section. >- </li> >-</ol> >-</p> >- >-<p><img width="473" height="214" src="../images/creatingATestDeployment_image023.png" alt="" /></p> >- >-<p>You can add or remove items from the <b>Artifacts </b>or <b>Locations</b> lists by using their respective <b>Add...</b> or <b>Remove</b> >-buttons. To remove an item, select it and then press the <b>Remove</b> button.</p> >- >-<p>Where there is more than one item in either list, their relative ordering can be modified by selecting an item within the list and then pressing >-the <b>Up</b> or <b>Down</b> buttons to move the selected item up or down the list, respectively.</p> >- >-<p>Press the <b>Open...</b> button in either the Artifacts or Locations lists to open the Artifact or Location editor respectively for whichever >-list item is selected.</p> >- >-<h3>Forming the Artifact and Location Pairing</h3> >- >-<p>Now click on the down-arrow button (<img border="0" >- src="../images/downArrow.gif" width="16" height="16" alt="Image of down arrow."/>) in the middle of the <i>Pairs</i> tab view to form the <i>testArtifact</i> and <i>testLocation</i> pairing.<br /> >-<img width="471" height="113" src="../images/creatingATestDeployment_image024.png" alt=""/></p> >- >-<p>To remove a pairing, select it and then press the <b>Remove</b> button. Where there is more than one pair in the >-list, their relative ordering can be modified by selecting an item within the list and then pressing the <b>Up</b> or <b>Down</b> >-buttons to move the selected item up or down the list, respectively.</p> >- >-<p> >-<b>Related concepts</b><br/> >-<a href="../concepts/cartifacteditor.htm">Artifact Editor - overview</a><br/> >-<a href="../concepts/cdeployeditor.htm">Deployment Editor - overview</a><br/> >-<a href="../concepts/clocationeditor.htm">Location Editor - overview</a><br/> >-</p> >- >-<p> >-<b>Related tasks</b><br/> >-<a href="tcreatetestdeployment.htm">Creating a deployment</a><br/> >-<a href="tcreateartifact.htm">Creating an artifact</a><br/> >-<a href="tcreatelocation.htm">Creating a location</a><br/> >-</p> >- >- >- >-</body> >- >-</html> >Index: ref/rdeploymentGroundRules.htm >=================================================================== >RCS file: ref/rdeploymentGroundRules.htm >diff -N ref/rdeploymentGroundRules.htm >--- ref/rdeploymentGroundRules.htm 11 Mar 2008 18:12:20 -0000 1.7 >+++ /dev/null 1 Jan 1970 00:00:00 -0000 >@@ -1,181 +0,0 @@ >-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"> >-<html lang="en-us" xml:lang="en-us"> >-<!-- >-/********************************************************************** >- * Copyright (c) 2006, 2008 Scapa Technologies and others. >- * All rights reserved. This content is 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 >- * $Id: rdeploymentGroundRules.htm,v 1.7 2008/03/11 18:12:20 paules Exp $ >- * >- * Contributors: >- * Scapa Technologies - Initial contribution >- * IBM - updates >- **********************************************************************/ >- --> >- >-<head> >-<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1" /> >-<link rel=StyleSheet href="../css/book.css" type="text/css" /> >- >-<title>Deployment ground rules</title> >-</head> >- >-<body> >- >-<div> >- >-<div> >- >-<h1><a name="_Toc116098723"><b>Deployment ground rules</b></a></h1> >- >-</div> >- >-<h3><a name="_Toc116098724"><b>General</b></a></h3> >- >-<p>TPTP only concerns itself with the properties CLASSPATH and ROOTDIR.</p> >- >-<h3><a name="_Toc116098725"><b>Files to be deployed</b></a></h3> >- >-<p>The files to be deployed at execution time are:</p> >- >-<p align=left>1. Everything on the class path of the test project <i>except</i> the following file types: <b>.java</b>, >-<b>.execution</b>, <b>.testsuite</b>, <b>.deploy</b>, <b>.location</b>, <b>.artifact</b>.</p> >- >-<p align=left>2. Any test assets associated with the Artifact being used for test execution</p> >- >-<p align=left>3. Property <b>CLASSPATH</b> of the General Properties of the Artifact that is used for test execution.</p> >- >-<p> </p> >- >-<h3><a name="_Toc116098726"><b>ROOTDIR Considerations</b></a></h3> >- >-<p>The following procedure is used to calculate ROOTDIR:</p> >- >-<table border=1 cellspacing=0 cellpadding=0> >- <tr> >- <th width=55 valign=top>Step</th> >- <th width=55 valign=top>Instructions</th> >- </tr> >- <tr> >- <td width=55 valign=top> >- <p>Step 1</p> >- </td> >- <td width=561 valign=top> >- <p>TPTP first looks on the remote machine for the ROOTDIR location property (if specified); if this exists, then its value is taken as the output >- from this step.</p> >- <p> </p> >- <p>If the ROOTDIR location property has not been specified, or if it has but does not exist on the remote machine, TPTP derives one using the >- temporary directory found on the remote machine's environment; it looks for LOCAL_AGENT_TEMP_DIR, TEMP, and TMP, in that order, and, whichever is >- found first is taken as the output from this step.</p> >- </td> >- </tr> >- <tr> >- <td width=55 valign=top> >- <p>Step 2</p> >- </td> >- <td width=561 valign=top> >- <p align=left>TPTP looks for the USR_NAME location property on the local machine. If this does not exist it pulls the user.name property from Java >- (System.getProperty("user.name")).</p> >- </td> >- </tr> >- <tr> >- <td width=55 valign=top> >- <p>Step 3</p> >- </td> >- <td width=561 valign=top> >- <p>TPTP concatenates the outputs from Steps 1 and 2 and takes this to be the ROOTDIR to use.</p> >- </td> >- </tr> >-</table> >- >-<p> </p> >- >-<h3><a name="_Toc116098727"><b>CLASSPATH Considerations</b></a></h3> >- >-<p>To set up JARs that will be deployed and rooted under your ROOTDIR, set up the CLASSPATH parameter for your artifact; to set up JARs that do not >-need to be deployed (for instance, they already exist on the location/machine to be deployed to) but still need to be included in the class path, >-then set up the CLASSPATH parameter in your location. So the distinction between artifact and location CLASSPATH is whether you want the JAR >-deployed and referenced or just referenced at the deployment location.</p> >- >-<h3><a name="_Toc116098728"><b>Excluded Libraries</b></a></h3> >- >-<p>Certain libraries are not deployed even if they are listed in the artifact's class path property. They are: >-<ul> >- <li>commons-logging.jar</li> >- <li>common-model.jar</li> >- <li>common.runner.jar</li> >- <li>datapool_api.jar</li> >- <li>ecore.jar</li> >- <li>ecore.xmi.jar</li> >- <li>hcframe.jar</li> >- <li>hexcore.jar</li> >- <li>hexl.jar</li> >- <li>hexr.jar</li> >- <li>hexrecr.jar</li> >- <li>hgla.jar</li> >- <li>hglaconfig.jar</li> >- <li>hmodel.jar</li> >- <li>hparse.jar</li> >- <li>hl14.jar</li> >- <li>hlcommons.jar</li> >- <li>hlcore.jar</li> >- <li>hlevents.jar</li> >- <li>hlcbe101.jar</li> >- <li>urlRecorder.runner.jar</li> >- <li>http.runner.jar</li> >- <li>java.runner.jar</li> >- <li>jmxagent.jar</li> >- <li>junit.jar</li> >- <li>runtime.jar</li> >- <li>xercesImpl.jar</li> >- <li>xmlParserAPIs.jar</li> >-</ul> >-</p> >- >-<p> </p> >- >-<h3><a name="_Toc115944850"></a><a name="_Toc116098729"><b>Agent Controller Considerations</b></a></h3> >- >-<p>Workbench clients before TPTP 3.3 cannot use agent controllers of TPTP 3.3 and beyond (they must continue to use older, pre-TPTP >-3.3 agent controllers). Clients of TPTP 3.3 and beyond can use both old and new agent controllers. In summary, currently, the client/server >-support in TPTP is the following:</p> >- >-<h4>TPTP 3.3+ Clients</h4> >- >-<p>Clients >= TPTP 3.3 and Server >= TPTP 3.3 [use new file transfer protocol if unsecured Agent Controller, old file transfer protocol if >-secure AC]</p> >- >-<p>Clients >= TPTP 3.3 and Server < TPTP 3.3 [use old file transfer protocol for unsecured and secured Agent Controllers]</p> >- >-<h4>TPTP Earlier Clients</h4> >- >-<p>Clients < TPTP 3.3 and Server >= TPTP 3.3 [this combination does not function due to older clients not understanding new server file transfer >-protocol]</p> >- >-<p>Clients < TPTP 3.3 and Server < TPTP 3.3 [uses old file transfer protocol for unsecured and secured Agent Controllers]</p> >- >-<p>There were file transfer service changes in TPTP 3.3 and TPTP 4.0 (to enhance the speed of deployment) that caused a new file transfer service >-protocol to be used, any clients before TPTP 3.3 do not know about this new protocol and therefore test deployment will fail. Newer clients know >-about the new and old protocols and therefore deployment will work.</p> >- >-<h3><a name="_Toc115944851"></a><a name="_Toc116098730"><b>OS Considerations</b></a></h3> >- >-<h4>File Path Naming Conventions</h4> >- >-<p>Ensure that any file paths that you set in properties properly reflect the OS naming conventions for the target machine. For example, if you are >-deploying to a Linux machine from a Windows client, and you have specified ROOTDIR, say, check that its value is a legal path for Linux.</p> >- >-<h4>Absolute Paths</h4> >- >-<p>All paths <i>must</i> be absolute. For example, on Windows, "C:\myRootDir" is appropriate and on Linux "/home/user/myRootDir" >-is appropriate - all paths must be absolute and not relative.</p> >- >-<p> </p> >- >-</div> >- >-</body> >- >-</html> >Index: toc/deploy_toc.xml >=================================================================== >RCS file: /cvsroot/tptp/test/org.eclipse.hyades.test.doc.user/toc/deploy_toc.xml,v >retrieving revision 1.1 >diff -u -r1.1 deploy_toc.xml >--- toc/deploy_toc.xml 5 Dec 2007 20:04:00 -0000 1.1 >+++ toc/deploy_toc.xml 18 Apr 2008 16:02:18 -0000 >@@ -1,7 +1,7 @@ > <?xml version="1.0" encoding="utf-8"?> > <!-- > /********************************************************************** >- * Copyright (c) 2007 IBM Corporation. >+ * Copyright (c) 2007, 2008 IBM Corporation. > * All rights reserved. This content > * is made available under the terms of the Eclipse Public License v1.0 > * which accompanies this distribution, and is available at >@@ -15,13 +15,14 @@ > <?NLS TYPE="org.eclipse.help.toc"?> > <toc label="Common test deployment topics"> > <topic label="Creating a test deployment" href="tasks/tdeploymentintro.htm"> >- <topic label="Creating an artifact" href="tasks/tcreateartifact.htm"/> >- <topic label="Artifact Editor - overview" href="concepts/cartifacteditor.htm"/> >- <topic label="Creating a location" href="tasks/tcreatelocation.htm"/> >- <topic label="Location Editor - overview" href="concepts/clocationeditor.htm"/> >- <topic label="Creating a deployment" href="tasks/tcreatetestdeployment.htm"/> >- <topic label="Deployment Editor - overview" href="concepts/cdeployeditor.htm"/> >- <topic label="Forming an artifact and location pairing" href="tasks/tassociateartifact.htm"/> >- <topic label="Deployment ground rules" href="ref/rdeploymentGroundRules.htm"/> >+ <topic label="Creating an artifact" href="tasks/tcreateartifact.htm"> >+ <topic label="Editing an artifact" href="concepts/cartifacteditor.htm"/> >+ </topic> >+ <topic label="Creating a location" href="tasks/tcreatelocation.htm"> >+ <topic label="Editing a location" href="concepts/clocationeditor.htm"/> >+ </topic> >+ <topic label="Creating a deployment" href="tasks/tcreatetestdeployment.htm"> >+ <topic label="Editing a deployment" href="concepts/cdeployeditor.htm"/> >+ </topic> > </topic> > </toc> >\ No newline at end of file >#P org.eclipse.tptp.test.report.birt.doc.user >Index: tasks/treporttest.xhtml >=================================================================== >RCS file: /cvsroot/tptp/test/org.eclipse.tptp.test.report.birt.doc.user/tasks/treporttest.xhtml,v >retrieving revision 1.13 >diff -u -r1.13 treporttest.xhtml >--- tasks/treporttest.xhtml 11 Apr 2008 18:43:20 -0000 1.13 >+++ tasks/treporttest.xhtml 18 Apr 2008 16:02:19 -0000 >@@ -58,16 +58,15 @@ > </tbody> > </table> > >-[1] Adobe's <a href="http://www.adobe.com/svg/viewer/install/main.html">Scalable Vector Graphics (SVG)</a> browser plug-in is required. >+<p>[1] Adobe's <a href="http://www.adobe.com/svg/viewer/install/main.html">Scalable Vector Graphics (SVG)</a> browser plug-in is required.</p> > >-<p>Generate the BIRT test report:</p> >+<p>Generate a BIRT test report:</p> > <ol> >- <li>Right-click on a test suite in the Test Navigator and select <strong>Report... </strong> from the context menu.</li> >- <li>The <strong>New Report</strong> dialog opens.</li> >- <li>Select one of the BIRT test report types and click on <strong>Next </strong>.</li> >- <li>Provide the parent folder and a name for the BIRT test report, then click on <strong>Next</strong>.</li> >+ <li>Right-click on a test suite in the Test Navigator and select <b>Report... </b>.</li> >+ <li>Select one of the BIRT test report types and click <b>Next </b>.</li> >+ <li>Provide the parent folder and the name for the BIRT test report and click <b>Next</b>.</li> > <li>Optionally, provide the report window (start and end data and time) for the BIRT test report.</li> >- <li>Click <strong>Finish </strong> to generate the BIRT test report.</li> >+ <li>Click <b>Finish </b> to generate the BIRT test report.</li> > </ol> > </body> > </html> >#P org.eclipse.tptp.test.recorders.url.doc.user >Index: tasks/trecordtest.html >=================================================================== >RCS file: /cvsroot/tptp/test/org.eclipse.tptp.test.recorders.url.doc.user/tasks/trecordtest.html,v >retrieving revision 1.3 >diff -u -r1.3 trecordtest.html >--- tasks/trecordtest.html 9 Apr 2008 19:57:38 -0000 1.3 >+++ tasks/trecordtest.html 18 Apr 2008 16:02:20 -0000 >@@ -37,7 +37,7 @@ > a test from the recording, and opening the test in the test editor. You can > record a test from Internet Explorer (the default on Windows) or from another > browser.</p> >-<div class="p">Optionally launch the <a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/tasks/ac/tworkwac.html">Agent Controller</a> on the local host or default to the <a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/concepts/ac/ciacintro.html">Integrated Agent Controller</a> >+<div class="p">Optionally launch the <a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/concepts/ac/c_ac_ovr.html">Agent Controller</a> on the local host or default to the <a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/concepts/ac/ciacintro.html">Integrated Agent Controller</a> > <p>If you will record with Internet Explorer, you do not need > to set your browser preferences. However, this procedure assumes that the > defaults are set, so you might want to click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span></span>, expand Test, select <span class="uicontrol">HTTP >#P org.eclipse.tptp.test.tools.manual.doc.user >Index: tasks/tprereqmanualtestconfiguration.htm >=================================================================== >RCS file: /cvsroot/tptp/test/org.eclipse.tptp.test.tools.manual.doc.user/tasks/tprereqmanualtestconfiguration.htm,v >retrieving revision 1.3 >diff -u -r1.3 tprereqmanualtestconfiguration.htm >--- tasks/tprereqmanualtestconfiguration.htm 16 Apr 2008 14:52:01 -0000 1.3 >+++ tasks/tprereqmanualtestconfiguration.htm 18 Apr 2008 16:02:21 -0000 >@@ -34,14 +34,14 @@ > <li>Open the <b>Test</b> perspective. Select <b>Window</b> > <b>Open Perspective</b> > <b>Other...</b> > <b>Test</b> > <b>OK</b>.</li> > <li>For local deployments: > <ol> >- <li>Optionally launch the <a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/tasks/ac/tworkwac.html">Agent Controller</a> on the local host or default to the <a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/concepts/rac/ciacintro.html">Integrated Agent Controller</a>.</li> >+ <li>Optionally launch the <a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/concepts/ac/c_ac_ovr.html">Agent Controller</a> on the local host or default to the <a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/concepts/ac/ciacintro.html">Integrated Agent Controller</a>.</li> > > <li>Optionally create a test deployment or default to the <i>local_deployment</i> deployment.</li> > </ol> > </li> > <li>For remote deployments: > <ol> >- <li>Launch the <a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/tasks/ac/tworkwac.html">Agent Controller</a> on the remote host.</li> >+ <li>Launch the <a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/concepts/ac/c_ac_ovr.html">Agent Controller</a> on the remote host.</li> > <li>Create a test deployment to the remote host.</li> > </ol> > </li> >@@ -50,14 +50,15 @@ > <br/> > > <p><strong>Related concepts</strong><br/> >- <a href="../concepts/cmanualtestoverview.htm">Manual testing with TPTP - overview</a><br/> >+ <a href="../concepts/cmanualtestoverview.htm">Testing manually</a><br/> > </p> > > <p><strong>Related tasks</strong><br/> > <a href="tdeploymentintro.htm">Creating a test deployment</a><br/> > <a href="trunningmanualtestsuite.htm">Running a manual test</a><br/> > <a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/tasks/ac/tiactesting.html">Testing with a local deployment</a><br/> >- <a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/tasks/ac/tworkwac.html">Working with the Agent Controller</a><br/> >+ <a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/concepts/ac/c_ac_ovr.html">Working with the Agent Controller</a><br/> >+ <a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/concepts/ac/ciacintro.html">Working with the Integrated Agent Controller</a><br/> > > </p> > </body> >#P org.eclipse.tptp.test.tools.junit.plugin.doc.user >Index: tasks/tdeploy2.htm >=================================================================== >RCS file: tasks/tdeploy2.htm >diff -N tasks/tdeploy2.htm >--- tasks/tdeploy2.htm 9 Apr 2008 19:57:53 -0000 1.2 >+++ /dev/null 1 Jan 1970 00:00:00 -0000 >@@ -1,65 +0,0 @@ >-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"> >-<html lang="en-us" xml:lang="en-us"> >-<!-- >-/********************************************************************** >- * Copyright (c) 2005, 2008 Scapa Technologies and others. >- * All rights reserved. This content is 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 >- * $Id: tdeploy2.htm,v 1.2 2008/04/09 19:57:53 paules Exp $ >- * >- * Contributors: >- * Scapa Technologies - Initial contribution >- * IBM - updates >- **********************************************************************/ >- --> >-<head> >-<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/> >-<link rel=StyleSheet href="../css/book.css" type="text/css"/> >- >-<title>Create a deployment</title> >-</head> >- >-<body> >- >-<h1><b>Create a deployment</b></h1> >- >-<p>To complete the deployment process we need to >-establish a TPTP deployment to associate the <i>workLOC</i> workbench location with. </p> >- >-<p>Note that the >-deployment editor is fully described in the referenced topics below. In this example we simply show the necessary steps >-required to create the deployment and associate the <i>workLOC</i> workbench location >-with it.</p> >- >-Proceed as follows: >-<ol> >- <li>Create a deployment named <i>workDEPLOY</i>.</li> >- <li>Select the <b>Pairs</b> tab.</li> >- <li>In the <b>Locations</b> section, click the <b>Add...</b> button. The <b>Add Location Association</b> dialog launches.</li> >- <li>Choose <b>Existing Resource</b> and type or browse to <i>workLOC</i>.</li> >- <li>Click <b>Finish</b>. <i>workLOC</i> will be added to the <b>Locations</b> list.</li> >-</ol> >- >-<p>Note that there is no need to provide an >-Artifact in this case.</p> >- >-<p> >-<b>Related concepts</b><br/> >-<a href="../../org.eclipse.hyades.test.doc.user/concepts/cartifacteditor.htm">Artifact Editor - overview</a><br/> >-<a href="../../org.eclipse.hyades.test.doc.user/concepts/cdeployeditor.htm">Deployment Editor - overview</a><br/> >-<a href="../../org.eclipse.hyades.test.doc.user/concepts/clocationeditor.htm">Location Editor - overview</a><br/> >-</p> >- >-<p> >-<b>Related tasks</b><br/> >-<a href="../../org.eclipse.hyades.test.doc.user/tasks/tcreateartifact.htm">Creating an artifact</a><br/> >-<a href="../../org.eclipse.hyades.test.doc.user/tasks/tcreatetestdeployment.htm">Creating a deployment</a><br/> >-<a href="../../org.eclipse.hyades.test.doc.user/tasks/tcreatelocation.htm">Creating a location</a><br/> >-<a href="../../org.eclipse.hyades.test.doc.user/tasks/tassociateartifact.htm">Forming an artifact and location pairing</a><br/> >-</p> >- >-</body> >- >-</html> >Index: tasks/tdeploy.htm >=================================================================== >RCS file: tasks/tdeploy.htm >diff -N tasks/tdeploy.htm >--- tasks/tdeploy.htm 9 Apr 2008 19:57:53 -0000 1.2 >+++ /dev/null 1 Jan 1970 00:00:00 -0000 >@@ -1,50 +0,0 @@ >-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"> >-<html lang="en-us" xml:lang="en-us"> >-<!-- >-/********************************************************************** >- * Copyright (c) 2006, 2008 Scapa Technologies and others. >- * All rights reserved. This content is 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 >- * $Id: tdeploy.htm,v 1.2 2008/04/09 19:57:53 paules Exp $ >- * >- * Contributors: >- * Scapa Technologies - Initial contribution >- * IBM - updates >- **********************************************************************/ >- --> >-<head> >-<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/> >-<link rel=StyleSheet href="../css/book.css" type="text/css"/> >-<title>Deploying a JUnit plug-in test</title> >-</head> >- >-<body> >- >-<h1>Deploying a JUnit plug-in test</h1> >- >-<p>Deploying a JUnit plug-in test normally >-requires the creation and configuration of a workbench location. If the >-deployment is local, there is a default deployment, <b>Deployment on the >-local workbench</b>, that is automatically selected within the <b>Run</b> dialog if a TPTP JUnit >-plug-in test is selected. </p> >- >-<p align=center><img width=783 height=488 >-src="../images/deploy_image002.jpg" alt=""/></p> >- >-<p><b>Note:</b> The >-default deployment <b>Deployment on the local >-workbench</b> does not provide, for example, instance reuse, a headless workbench, nor does it run tests >-in the UI thread. To obtain these features and other features, you must set up >-a specific workbench location.</p> >- >-<p> >-<b>Related tasks</b><br/> >-<a href="../../org.eclipse.hyades.test.doc.user/tasks/tdeploymentintro.htm">Creating a deployment</a><br/> >-<a href="tcreateWorkbenchLocation.htm">Creating a workbench location</a><br/> >-</p> >- >-</body> >- >-</html> >Index: tasks/tcreateWorkbenchLocation.htm >=================================================================== >RCS file: /cvsroot/tptp/test/org.eclipse.tptp.test.tools.junit.plugin.doc.user/tasks/tcreateWorkbenchLocation.htm,v >retrieving revision 1.2 >diff -u -r1.2 tcreateWorkbenchLocation.htm >--- tasks/tcreateWorkbenchLocation.htm 9 Apr 2008 19:57:53 -0000 1.2 >+++ tasks/tcreateWorkbenchLocation.htm 18 Apr 2008 16:02:21 -0000 >@@ -24,48 +24,37 @@ > > <h1>Creating a workbench location</h1> > >-<p> >-A workbench location is used to specify where a TPTP JUnit Plug-in test will run. >-</p> >+<p>Test workbench locations associate a target host with a test deployment. The test suite will be executed >+on the target host specified in the test workbench location.</p> >+ >+<p>Create a test workbench location:</p> > > <ol> >- <li> >- Select <b>File</b> > <b>New</b> > <b>Other</b> > <b>Workbench Location</b> >- > <b>Test </b>> <b>Test Assets</b>. Click <b>Next</b>. >- </li> >- <li> >- In the "Enter or select the parent folder" field, type <i>pluginProject/src</i>. >- In the Name field type <i>workLOC</i>. >- </li> >- <li> >- Click <b>Next</b> to launch the <b>Workbench Details</b> dialog. >- <ul> >- <li> >- Select 'On the local workbench' if local deployment is required; >- otherwise select 'On another workbench' and provide the Host name, >- address, and the relevant Eclipse installation directory. >- </li> >- <li> >- If you want the same Eclipse instance to be reused<i></i> (i.e. >- it will <i>not</i> shutdown and restart between test runs), >- then check the 'Allow the same instance to be reused' check box. >- Similarly, if you require a <i>headless workbench</i> or to >- <i>run tests in the UI thread</i>, check the appropriate check >- boxes in the dialog. >- </li> >- </ul> >- </li> >- <li> >- Click <b>Next</b> and provide a description of your workbench location >- if required. >- </li> >- <li> >- Click <b>Finish</b>. The workbench location editor will open with the >- <i>Overview</i> tab open. (If not, double-click on the <i>workLOC</i> >- location file.) >- </li> >+ <li>Right-click in the Test Navigator and select <b>New</b> > <b>Test Element...</b>.</li> >+ <li>Select <b>Test Assets</b> > <b>Workbench Location</b> and click <b>Next</b>.</li> >+ <li>Provide the parent folder and the name for the test workbench location and click <b>Next</b>.</li> >+ <li>Optionally, provide a description for the test workbench location and click <b>Next</b>.</li> >+ <li>Select the target workbench as either the local workbench, as defined in the <a href="../../org.eclipse.pde.doc.user/guide/tools/preference_pages/target_platform.htm">Target Platform</a>, >+ or another workbench. If another workbench is selected, enter the host name or IP address of the target host, Eclipse location (<i><Eclipse installation directory absolute path>/eclipse</i>), >+ workspace location (<i><Eclipse workspace directory absolute path>/eclipse</i>), operating system, windowing system, architecture, and locale for the host where the other workbench is installed. >+ Test the connection to the target host by clicking the <b>Test Connection</b> link<sup>1</sup>. Select the main options for the target workbench</li> >+ <li>Click <b>Finish</b> to create the test workbench location.</li> > </ol> > >+<p>[1] The <a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/concepts/ac/c_ac_ovr.html">Agent Controller</a> or >+<a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/concepts/ac/ciacintro.html">Integrated Agent Controller</a> >+(local host only) is required to be configured and running.</p> >+ >+<p> >+<b>Related concepts</b><br/> >+<a href="../concepts/cworkbenchLocationEditor.htm">Editing a workbench location</a><br/> >+</p> >+ >+<p> >+<b>Related tasks</b><br/> >+<a href="../../org.eclipse.hyades.test.doc.user/tasks/tcreatetestdeployment.htm">Creating a deployment</a><br/> >+</p> >+ > </body> > > </html> >Index: concepts/cworkbenchLocationEditor.htm >=================================================================== >RCS file: /cvsroot/tptp/test/org.eclipse.tptp.test.tools.junit.plugin.doc.user/concepts/cworkbenchLocationEditor.htm,v >retrieving revision 1.2 >diff -u -r1.2 cworkbenchLocationEditor.htm >--- concepts/cworkbenchLocationEditor.htm 9 Apr 2008 19:57:54 -0000 1.2 >+++ concepts/cworkbenchLocationEditor.htm 18 Apr 2008 16:02:21 -0000 >@@ -26,76 +26,77 @@ > <body> > > <h1>Workbench location editor</h1> >-<p> >-Use the Workbench location editor if necessary to adjust the workbench >-location where the JUnit plug-in test will run. >-The editor has three tabs: Overview, Eclipse Workbench Properties, and General Properties.</p> >- >-<p align="center"><img border="0" src="../images/workbenchLocationEditor_image002.gif" >- width="523" height="468" alt="" /></p> >- >-<p> </p> >- >-<p> </p> > >-<h3><b>Overview Tab</b></h3> >+<p>Test workbench locations are edited using the Location editor. The editor contains three tabs:</p> > >-<p>The General Information section provides the Workbench >-Location name (workLOC in this example), description, the path to the workLOC file >-(/pluginProject/src/workLOC.location), and the host name (localhost). </p> >+<h2>Overview</h2> > >-<p>The <i>Property Groups</i> >-section provides links to <b>Eclipse Workbench Properties</b> and <b>General Properties</b>. These also have their >-own sections in this page and tabs in the editor. Selecting <b>Eclipse Workbench >-Properties</b> or <b>General Properties</b> >-anywhere within the <i>Overview</i> tab >-page has the same effect as selecting their respective editor tabs.</p> >- >-<p> >-The links >-provided in the <b>Eclipse Workbench Properties</b> >-section all result, if selected, in the editor switching to >-the <b>Eclipse Workbench Properties</b> >-tab page where the actual relevant property setting facilities are found. >-</p> >+<p>This tab provides an overview of the test workbench location.</p> > >-<h3><b>Eclipse Workbench Properties Tab</b></h3> >+<p>This tab contains three sections:</p> > >-<p align=center><img width=517 height=424 >-src="../images/workbenchLocationEditor_image003.png" alt=""/></p> >+<ul> >+ <li> >+ <p><b>General Information</b></p> >+ <p>Contains the test workbench location's name, description, file path within the workspace, and host name or IP address. The test workbench location's name<sup>1</sup>, description, and host name or IP address are editable.</p> >+ <br/> >+ <p>The connection to the target host may be tested by clicking the <b>Test Connection</b> link<sup>2</sup>.</p> >+ <br/> >+ </li> >+ <li> >+ <p><b>Property Groups</b></p> >+ <p>Contains a link to the General Properties and Eclipse Workbench Properties tab. Clicking a link will open the associated tab.</p> >+ <br/> >+ </li> >+ <li> >+ <p><b>Eclipse Workbench Properties</b></p> >+ <p>Contains links to the Eclipse Workbench properties in the Eclipse Workbench Properties tab. Clicking a link or the More... button will >+ open the Eclipse Workbench Properties tab.</p> >+ <br/> >+ </li> >+ <li> >+ <p><b>General Properties</b></p> >+ <p>Contains links to the general properties in the General Properties tab. Clicking a link or the More... button will >+ open the General Properties tab.</p> >+ <br/> >+ <p>Note, the General Properties section will only appear if one or more general properties are associated with the test workbench location.</p> >+ <br/> >+ </li> >+</ul> >+ >+<p>[1] Test workbench locations have a file name and logical name. The logical name is used in the Test Navigator, dialogs, editors, and wizards to represent the test workbench location. >+The file name represents the test workbench location file (<i>*.location</i>) within the workspace. When the test workbench location is created, the logical name defaults to the file name >+(excluding the <i>.location</i> file extension) and may be modified without modifying the file name. The logical name allows customization of the test workbench location name >+without affecting the file name within the workspace.</p> >+ >+<p>[2] The <a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/concepts/ac/c_ac_ovr.html">Agent Controller</a> or >+<a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/concepts/ac/ciacintro.html">Integrated Agent Controller</a> >+(local host only) is required to be configured and running.</p> >+ >+<h2>General Properties</h2> >+ >+<p>This tab contains the table of general properties associated with the test workbench location.</p> >+ >+<p>Note, the General Properties tab will only appear if one or more general properties are associated with the test workbench location.</p> >+ >+<p>General properties can be added to the table by clicking the <b>Add...</b> button and entering the property name, operator (<i>=</i>, <i>!=</i>, <i>></i>, <i><</i>, <i>>=</i>, or <i><=</i>), and value.</p> >+ >+<p>All file paths are absolute and operating system dependent based on the target operating system.</p> > >-<p> </p> >+<p>Selected general properties can be removed (<b>Remove</b>), moved up (<b>Up</b>), or moved down (<b>Down</b>). Existing general properties may be edited by double-clicking >+the general property in the table and and modifying the property name, operator, and/or value.</p> > >-<p>This page offers facilities to set particular Eclipse >-Workbench properties. <i></i></p> >+<h2>Eclipse Workbench Properties</h2> > >-<p>Of particular interest to <b>TPTP JUnit Plug-in Test</b> users are the properties <i>eclipseLocation</i>, <i>allowReuse</i>, <i>headless</i>, and <i>uiThread</i>, >-for which options were provided when creating the <b>Workbench Location</b>.</p> >+<p>This tab contains the table of Eclipse Workbench properties associated with the test workbench location, as defined in the <a href="../../org.eclipse.pde.doc.user/guide/tools/preference_pages/target_platform.htm">Target Platform</a>.</p> > >-<p>The other properties should already be familiar to >-Eclipse plug-in developers.</p> >- >-<h3><b>General Properties Tab</b></h3> >- >-<p align=center><img width=301 height=211 >-src="../images/workbenchLocationEditor_image005.png" alt=""/></p> >- >-<p> </p> >- >-<p>The <i>General >-Properties</i> page provides facilities to add additional properties >-over and above those specifiable in the <i>Eclipse >-Workbench Properties</i> page. A detailed explanation of how to >-configure <i>General Properties</i> is >-written in the topic <i>Creating a Test >-Deployment</i>.</p> >- >-<p> </p> >+<p>All file paths are absolute and operating system dependent based on the target operating system.</p> > > <p> >-<b>Related tasks</b><br /> >-<a href="../../org.eclipse.hyades.test.doc.user/tasks/tdeploymentintro.htm">Creating a Test Deployment</a><br /> >+<b>Related tasks</b><br/> >+<a href="../tasks/tcreateWorkbenchLocation.htm">Creating a workbench location</a><br/> > </p> >+ > </body> > > </html> >Index: toc/junitplugin_toc.xml >=================================================================== >RCS file: /cvsroot/tptp/test/org.eclipse.tptp.test.tools.junit.plugin.doc.user/toc/junitplugin_toc.xml,v >retrieving revision 1.3 >diff -u -r1.3 junitplugin_toc.xml >--- toc/junitplugin_toc.xml 16 Apr 2008 19:32:51 -0000 1.3 >+++ toc/junitplugin_toc.xml 18 Apr 2008 16:02:21 -0000 >@@ -28,10 +28,9 @@ > </topic> > <topic label="Tutorial: Accessing a datapool from a JUnit Plug-in test" href="../org.eclipse.hyades.test.doc.user/samples/saccessdp.htm"/> > </topic> >- <topic label="Creating a workbench location" href="tasks/tcreateWorkbenchLocation.htm"/> >- <topic label="Workbench location editor" href="concepts/cworkbenchLocationEditor.htm"/> >- <topic label="Create a deployment" href="tasks/tdeploy2.htm"/> >- <topic label="Deploying a JUnit plug-in test" href="tasks/tdeploy.htm"/> >+ <topic label="Creating a workbench location" href="tasks/tcreateWorkbenchLocation.htm"> >+ <topic label="Editing a workbench location" href="concepts/cworkbenchLocationEditor.htm"/> >+ </topic> > <topic label="Running a test" href="../org.eclipse.hyades.test.doc.user/tasks/trun.htm"/> > > <link toc="../org.eclipse.hyades.test.doc.user/toc/logviewer_toc.xml"/>
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 201892
: 96616