* Copyright (c) 2006, 2007 Scapa Technologies and others.

 * Copyright (c) 2006, 2008 Scapa Technologies and others.

<title>Artifact Editor - overview</title>

<title>Editing an artifact</title>

<h1>Artifact Editor - overview</h1>

<p>Test artifacts are edited using the Artifact editor.  The editor contains three tabs:</p> 

<p>

<h2>Overview</h2>

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>&nbsp; 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 =, !=, &gt;, &lt;, &gt;=, or &lt;= 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>

<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>

<ul>

<b>Related concepts</b><br/>

	<li>

<a href="cdeployeditor.htm">Deployment Editor - overview</a><br/>

		<p><b>General Information</b></p>

<a href="clocationeditor.htm">Location Editor - overview</a><br/>

		<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>

</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>&gt;</i>, <i>&lt;</i>, <i>&gt;=</i>, or <i>&lt;=</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>

 * Copyright (c) 2006, 2007 Scapa Technologies and others.

 * Copyright (c) 2006, 2008 Scapa Technologies and others.

<title>Location Editor - overview</title>

<title>Editing a location</title>

<h1>Location Editor - overview</h1>

<p>Test locations are edited using the Location editor.  The editor contains three tabs:</p> 

<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>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

<h2>Overview</h2>

computer in the <b>Host name</b> field.</p>

<p>Property Groups references <i>General Properties </i>and<i> Eclipse Workbench Properties</i> sections, which are also separately shown on the

<p>This tab provides an overview of the test location.</p>

right-hand side of the Location editor overview tab view. Each&nbsp; 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>

<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>&gt;</i>, <i>&lt;</i>, <i>&gt;=</i>, or <i>&lt;=</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

<h2>Eclipse Workbench Properties</h2>

describing TPTP JUnit Plug-in Test.</p>

<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>

<p>Note, the Eclipse Workbench Properties tab will only appear if one or more Eclipse Workbench properties are associated with the test location.</p>

The functionality available here is identical to that described for the <b>General Properties</b> tab in the Artifact Editor.

</p>

<p>

<p>All file paths are absolute and operating system dependent based on the target operating system.</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>

 * Copyright (c) 2006, 2007 Scapa Technologies and others.

 * Copyright (c) 2006, 2008 Scapa Technologies and others.

<title>Deployment Editor - overview</title>

<title>Editing a deployment</title>

<h1>Deployment Editor - overview</h1>

<p>Test deployments are edited using the Deployment editor.  The editor contains three tabs:</p> 

<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>

The <i>Pairs</i> tab is used to add Artifacts and Locations and to form Artifact Location pairs. <br />

<h2>Overview</h2>

<img border="0" src="../images/creatingATestDeployment_image010.gif"

	width="514" height="358" alt=""/>

<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>This tab contains three sections:</p>

<p>

<ul>

<b>Related concepts</b><br/>

	<li>

<a href="cartifacteditor.htm">Artifact Editor - overview</a><br/>

		<p><b>General Information</b></p>

<a href="clocationeditor.htm">Location Editor - overview</a><br/>

		<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>

</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>

<a href="../tasks/tassociateartifact.htm">Forming an artifact and location pairing</a><br/>

<a href="../tasks/tcreatetestdeployment.htm">Creating a deployment</a><br/>

 * Copyright (c) 2006, 2007 Scapa Technologies and others.

 * Copyright (c) 2006, 2008 Scapa Technologies and others.

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>

	<li>Right-click in the <b>Test Navigator</b> and select&nbsp; <b>New</b> &gt; <b>Test Element...</b> The New wizard opens.</li>

	<li>Right-click in the Test Navigator and select <b>New</b> &gt; <b>Test Element...</b>.</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 <b>Test Assets</b> &gt; <b>Deployment</b> and click <b>Next</b>.</li>

	<li>Select the parent folder and enter the deployment name, <i>testDeployment</i>. Click on <b>Next</b> and optionally enter a description

    <li>Provide the parent folder and the name for the test deployment and click <b>Next</b>.</li>

	for the deployment.</li>

    <li>Optionally, provide a description for the test deployment and click <b>Next</b>.</li>

	<li>Click on <b>Finish</b>. The  <b>Deployment editor</b> launches.</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>

<a href="../concepts/cartifacteditor.htm">Artifact Editor - overview</a><br/>

<a href="../concepts/cdeployeditor.htm">Editing a deployment</a><br/>

<a href="../concepts/cdeployeditor.htm">Deployment Editor - overview</a><br/>

<a href="../concepts/clocationeditor.htm">Location Editor - overview</a><br/>

 * Copyright (c) 2006, 2007 Scapa Technologies and others.

 * Copyright (c) 2006, 2008 Scapa Technologies and others.

<p>This section describes how to create a deployment for your test suite. The example is set within the context of the Test perspective.

<p>This section describes creating and editing test artifacts, locations, and deployments for executing a test suite.</p>

We shall execute the following steps:</p>

		<p>

		<p>Test artifacts associate test assets, such as test suites and datapools, with a test deployment.</p>

		Test artifacts associate objects such as test suites and datapools; that is,

		artifacts make an asset available to a test suite.

		</p>

		<p>

		<p>Test locations associate a target host with a test deployment.</p>

		Test locations identify the computer where the test suite will run.

		</p>

		<a href="tassociateartifact.htm">Forming an artifact and location pairing</a>

		<a href="tcreatetestdeployment.htm">Creating a deployment</a>

		<p>

		<p>Test deployments pair test artifacts and test locations for executing a test suite.</p>

		Create the pair of test artifact and location to be used by the test deployment.

		</p>

<a href="../concepts/cartifacteditor.htm">Artifact Editor - overview</a><br/>

<a href="../concepts/cartifacteditor.htm">Editing an artifact</a><br/>

<a href="../concepts/cdeployeditor.htm">Deployment Editor - overview</a><br/>

<a href="../concepts/clocationeditor.htm">Editing a location</a><br/>

<a href="../concepts/clocationeditor.htm">Location Editor - overview</a><br/>

<a href="../concepts/cdeployeditor.htm">Editing a deployment</a><br/>

<a href="../concepts/cdeployeditor.htm">Deployment Editor - overview</a><br/>

<a href="../concepts/cdeployeditor.htm">Editing a deployment</a><br/>

 * Copyright (c) 2006, 2007 IBM Corporation.

 * Copyright (c) 2006, 2008 IBM Corporation.

<p>Repeat the same sequence of steps as for creating a deployment but this time 

<p>Test artifacts associate test assets, such as test suites and datapools, with a test deployment.</p>

create an artifact named <i>testArtifact</i>.</p>

<p>Create a test artifact:</p>

	<li>

	<li>Right-click in the Test Navigator and select <b>New</b> &gt; <b>Test Element...</b>.</li>

	Right-click in the <b>Test Navigator</b> and select <b>New</b> &gt; <b>Test Element...</b>

	<li>Select <b>Test Assets</b> &gt; <b>Artifact</b> and click <b>Next</b>.</li>

	</li>

    <li>Provide the parent folder and the name for the test artifact and click <b>Next</b>.</li>

	<li>

    <li>Optionally, provide a description for the test artifact and click <b>Next</b>.</li>

	Open <b>Test Assets</b> and select <b>Artifact</b>.

    <li>Select the associated test assets, such as test suites and datapools.</li>

	</li>

    <li>Click <b>Finish</b> to create the test artifact.</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>

<a href="../concepts/cartifacteditor.htm">Artifact Editor - overview</a><br/>

<a href="../concepts/cartifacteditor.htm">Editing an artifact</a><br/>

<a href="../concepts/cdeployeditor.htm">Deployment Editor - overview</a><br/>

<a href="../concepts/clocationeditor.htm">Location Editor - overview</a><br/>

 * Copyright (c) 2006, 2007 Scapa Technologies and others.

 * Copyright (c) 2006, 2008 Scapa Technologies and others.

<p>

<p>Test locations associate a target host with a test deployment.  The test suite will be executed 

Repeat the same sequence of steps as for creating a deployment but for this

on the target host specified in the test location.</p>

example create a location named <b>testLocation</b>.

</p>

<p>Create a test location:</p>

	<li>

	<li>Right-click in the Test Navigator and select <b>New</b> &gt; <b>Test Element...</b>.</li>

	Right-click in the <b>Test Navigator</b> and select&nbsp; 

	<li>Select <b>Test Assets</b> &gt; <b>Location</b> and click <b>Next</b>.</li>

	<b>New</b> &gt; <b>Test Element...</b>

    <li>Provide the parent folder and the name for the test location and click <b>Next</b>.</li>

	</li>

    <li>Optionally, provide a description for the test location and click <b>Next</b>.</li>

	<li>

    <li>Enter the host name or IP address of the target host. By default, <i>localhost</i> is entered.  Test the 

	Open <b>Test Assets</b> and select <b>Location</b>.

    connection to the target host by clicking the <b>Test Connection</b> link<sup>1</sup>.</li>

	</li>

    <li>Click <b>Finish</b> to create the test location.</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>

<p>If the intention is to run tests on another computer, the name of that computer must be entered&nbsp;in the <b>H</b><b>ost name</b> field

<p>[1] The <a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/concepts/ac/c_ac_ovr.html">Agent Controller</a> or 

of the relevant location.</p>

<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>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>

<a href="../concepts/cartifacteditor.htm">Artifact Editor - overview</a><br/>

<a href="../concepts/clocationeditor.htm">Editing a location</a><br/>

<a href="../concepts/cdeployeditor.htm">Deployment Editor - overview</a><br/>

<a href="../concepts/clocationeditor.htm">Location Editor - overview</a><br/>

[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>

 	<li>Open the <b>Window &gt; Preferences</b> dialog.</li>

 	<li>Select <b>Window</b> &gt; <b>Preferences...</b> from the file menu.</li>

	<li>Select the report <b>Test &gt; Test Report &gt; Font</b> preference page.</li>

	<li>Select the report <b>Test</> &gt; <b>Test Reports<b> &gt; <b>Fonts</b> preference page.</li>

	<li>Configure the fonts used when generating the performance test report.</li>

	<li>Configure the fonts used when generating a performance test report.</li>

	<li>Select <b>OK</b>.</li>

	<li>Click <b>OK</b> to save the preferences.</li>

<p>Generate the performance test report:</p>

<p>Generate a performance test report:</p>

  <li>Right-click on a performance test suite in the Test Navigator and select <strong>Report... </strong> from the context menu.</li>

  <li>Right-click on a performance test suite in the Test Navigator and select <b>Report... </b>.</li>

  <li>The <strong>New Report</strong> dialog opens.</li>

  <li>Select one of the performance test report types and click <b>Next </b>.</li>

  <li>Select one of the performance test report types and click on <strong>Next </strong>.</li>

  <li>Provide the parent folder and the name for the performance test report and click <b>Next</b>.</li>

  <li>Provide the parent folder and a name for the performance test report, then click on <strong>Next</strong>.</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>

[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>

 	<li>Open the <b>Window &gt; Preferences</b> dialog.</li>

 	<li>Select <b>Window</b> &gt; <b>Preferences...</b> from the file menu.</li>

	<li>Select the report <b>Test &gt; Test Report &gt; Font</b> preference page.</li>

	<li>Select the report <b>Test</> &gt; <b>Test Reports<b> &gt; <b>Fonts</b> preference page.</li>

	<li>Configure the fonts used when generating the test report.</li>

	<li>Configure the fonts used when generating a test report.</li>

	<li>Select <b>OK</b>.</li>

	<li>Click <b>OK</b> to save the preferences.</li>

<p>Generate the test report:</p>

<p>Generate a test report:</p>

  <li>Right-click on a test suite in the Test Navigator and select <strong>Report... </strong> from the context menu.</li>

  <li>Right-click on a test suite in the Test Navigator and select <b>Report... </b>.</li>

  <li>The <strong>New Report</strong> dialog opens.</li>

  <li>Select one of the test report types and click <b>Next </b>.</li>

  <li>Select one of the test report types and click on <strong>Next </strong>.</li>

  <li>Provide the parent folder and the name for the test report and click <b>Next</b>.</li>

  <li>Provide the parent folder and a name for the test report, then click on <strong>Next</strong>.</li>

  <li>Click <strong>Finish </strong> to generate the test report.</li>

  <li>Click <b>Finish </b> to generate the test report.</li>

 * Copyright (c) 2007 IBM Corporation.

 * Copyright (c) 2007, 2008 IBM Corporation.

		<topic label="Creating an artifact" href="tasks/tcreateartifact.htm"/>

		<topic label="Creating an artifact" href="tasks/tcreateartifact.htm">

		<topic label="Artifact Editor - overview" href="concepts/cartifacteditor.htm"/>

			<topic label="Editing an artifact" href="concepts/cartifacteditor.htm"/>

		<topic label="Creating a location" href="tasks/tcreatelocation.htm"/>

		</topic>

		<topic label="Location Editor - overview" href="concepts/clocationeditor.htm"/>

		<topic label="Creating a location" href="tasks/tcreatelocation.htm">

		<topic label="Creating a deployment" href="tasks/tcreatetestdeployment.htm"/>

			<topic label="Editing a location" href="concepts/clocationeditor.htm"/>

		<topic label="Deployment Editor - overview" href="concepts/cdeployeditor.htm"/>

		</topic>

		<topic label="Forming an artifact and location pairing" href="tasks/tassociateartifact.htm"/>

		<topic label="Creating a deployment" href="tasks/tcreatetestdeployment.htm">

		<topic label="Deployment ground rules" href="ref/rdeploymentGroundRules.htm"/>

			<topic label="Editing a deployment" href="concepts/cdeployeditor.htm"/>

		</topic>

[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>

  <li>Right-click on a test suite in the Test Navigator and select <strong>Report... </strong> from the context menu.</li>

  <li>Right-click on a test suite in the Test Navigator and select <b>Report... </b>.</li>

  <li>The <strong>New Report</strong> dialog opens.</li>

  <li>Select one of the BIRT test report types and click <b>Next </b>.</li>

  <li>Select one of the BIRT test report types and click on <strong>Next </strong>.</li>

  <li>Provide the parent folder and the name for the BIRT test report and click <b>Next</b>.</li>

  <li>Provide the parent folder and a name for the BIRT test report, then click on <strong>Next</strong>.</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>

<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>

	    <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>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>

   <a href="../concepts/cmanualtestoverview.htm">Manual testing with TPTP - overview</a><br/>

   <a href="../concepts/cmanualtestoverview.htm">Testing manually</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>

<p>Test workbench locations associate a target host with a test deployment.  The test suite will be executed 

A workbench location is used to specify where a TPTP JUnit Plug-in test will run.

on the target host specified in the test workbench location.</p>

</p>

<p>Create a test workbench location:</p>

	<li>

	<li>Right-click in the Test Navigator and select <b>New</b> &gt; <b>Test Element...</b>.</li>

	Select <b>File</b> &gt; <b>New</b> &gt; <b>Other</b> &gt; <b>Workbench Location</b> 

	<li>Select <b>Test Assets</b> &gt; <b>Workbench Location</b> and click <b>Next</b>.</li>

	&gt; <b>Test </b>&gt; <b>Test Assets</b>. Click  <b>Next</b>.

    <li>Provide the parent folder and the name for the test workbench location and click <b>Next</b>.</li>

	</li>

    <li>Optionally, provide a description for the test workbench location and click <b>Next</b>.</li>

	<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>, 

	In the &quot;Enter or select the parent folder&quot; field, type <i>pluginProject/src</i>. 

    or another workbench.  If another workbench is selected, enter the host name or IP address of the target host, Eclipse location (<i>&lt;Eclipse installation directory absolute path&gt;/eclipse</i>), 

	In the Name field type <i>workLOC</i>. 

    workspace location (<i>&lt;Eclipse workspace directory absolute path&gt;/eclipse</i>), operating system, windowing system, architecture, and locale for the host where the other workbench is installed.

	</li>

    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>

    <li>Click <b>Finish</b> to create the test workbench location.</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>

<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

<h2>Overview</h2>

Location name (workLOC in this example), description, the path to the workLOC file

(/pluginProject/src/workLOC.location), and the host name (localhost). </p>

<p>The <i>Property Groups</i>

<p>This tab provides an overview of the test workbench location.</p>

section provides links to&nbsp; <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&nbsp; <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>

<h3><b>Eclipse Workbench Properties Tab</b></h3>

<p>This tab contains three sections:</p>

<p align=center><img width=517 height=424

<ul>

src="../images/workbenchLocationEditor_image003.png" alt=""/></p>

	<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>&gt;</i>, <i>&lt;</i>, <i>&gt;=</i>, or <i>&lt;=</i>), and value.</p>

<p>All file paths are absolute and operating system dependent based on the target operating system.</p>

<p>&nbsp;</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

<h2>Eclipse Workbench Properties</h2>

Workbench properties. <i></i></p>

<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>,

<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>  

for which options were provided when creating the <b>Workbench Location</b>.</p>

<p>The other properties should already be familiar to

<p>All file paths are absolute and operating system dependent based on the target operating system.</p>

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>&nbsp;</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>&nbsp;</p>

<b>Related tasks</b><br />

<b>Related tasks</b><br/>

<a href="../../org.eclipse.hyades.test.doc.user/tasks/tdeploymentintro.htm">Creating a Test Deployment</a><br />

<a href="../tasks/tcreateWorkbenchLocation.htm">Creating a workbench location</a><br/>

      <topic label="Creating a workbench location" href="tasks/tcreateWorkbenchLocation.htm"/>

	  <topic label="Creating a workbench location" href="tasks/tcreateWorkbenchLocation.htm">

      <topic label="Workbench location editor" href="concepts/cworkbenchLocationEditor.htm"/>

	    <topic label="Editing a workbench location" href="concepts/cworkbenchLocationEditor.htm"/>

      <topic label="Create a deployment" href="tasks/tdeploy2.htm"/>

	  </topic>

      <topic label="Deploying a JUnit plug-in test" href="tasks/tdeploy.htm"/>