Attachment #27655 for bug #110436

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

View | Details | Raw Unified | Return to bug 110436
Collapse All | Expand All




      <topic label="Reports on JUnit tests" href="junit/tptpJUnitTest_analysisReport.htm"/>
      <anchor id="test_junit"/>
   </topic>
   <topic label="Manual testing with TPTP" href="concepts/cmanualtestoverview.htm">
      <topic label="Creating a manual test" href="tasks/tcreatingamanualtest.htm"/>
      <topic label="Editing a manual test" href="tasks/tediting_manual_test.htm"/>
      <topic label="Running a manual test" href="tasks/trunningmanualtestsuite.htm"/>
      <topic label="Analyzing manual test results" href="tasks/tanalyzingmanualtestresults.htm"/>
      <topic label="Generic launch configuration properties" href="ref/rmanualcreate.htm"/>
      <anchor id="test_manual"/>
   </topic>
   <anchor id="test_results"/>
   <topic label="Reference" href="ref/refintro.html">
   	  <topic label="Generic launch configuration properties" href="ref/rmanualcreate.htm"/>
   	  <topic label="Test Log viewer" href="ref/rtestlog.html"/>
      <anchor id="reference"/>
   </topic>
</toc>




<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="concept" />
<meta name="DC.Title" content="Manual testing with TPTP - overview" />
<meta name="DC.Relation" scheme="URI" content="../tasks/tcreatingamanualtest.dita" />
<meta name="DC.Relation" scheme="URI" content="../tasks/tediting_manual_test.dita" />
<meta name="DC.Relation" scheme="URI" content="../tasks/trunningmanualtestsuite.dita" />

<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="../css/ibmdita.css" />
<link rel="stylesheet" type="text/css" href="../css/swg_info_common.css" />
<title>Manual testing with TPTP - overview</title>
</head>
<body id="manualtestoverview"><a name="manualtestoverview"><!-- --></a>

<h1 class="topictitle1">Manual testing with TPTP - overview</h1>
<div><p>A manual test describes a procedure that a human tester performs to verify
whether a feature is working. The Eclipse test and performance tools platform
(TPTP) supports assisted manual testing.</p>




<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html xmlns:v="urn:schemas-microsoft-com:vml"
xmlns:o="urn:schemas-microsoft-com:office:office"
xmlns:w="urn:schemas-microsoft-com:office:word"
xmlns="http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
<link rel=StyleSheet href="../css/book.css" type="text/css"/>
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>TPTP Manual Test</title>
<style>
<!--
 




<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html xmlns:v="urn:schemas-microsoft-com:vml"
xmlns:o="urn:schemas-microsoft-com:office:office"
xmlns:w="urn:schemas-microsoft-com:office:word"
xmlns="http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
<link rel=StyleSheet href="../css/book.css" type="text/css"/>
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>TPTP Manual Test</title>
<style>
<!--
 




<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html xmlns:v="urn:schemas-microsoft-com:vml"
xmlns:o="urn:schemas-microsoft-com:office:office"
xmlns:w="urn:schemas-microsoft-com:office:word"
xmlns="http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
<link rel=StyleSheet href="../css/book.css" type="text/css"/>
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>TPTP Manual Test</title>
<style>
<!--
 




<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html xmlns:v="urn:schemas-microsoft-com:vml"
xmlns:o="urn:schemas-microsoft-com:office:office"
xmlns:w="urn:schemas-microsoft-com:office:word"
xmlns="http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
<link rel=StyleSheet href="../css/book.css" type="text/css"/>
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>TPTP Manual Test</title>
<style>
<!--
 




<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html xmlns:v="urn:schemas-microsoft-com:vml"
xmlns:o="urn:schemas-microsoft-com:office:office"
xmlns:w="urn:schemas-microsoft-com:office:word"
xmlns="http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
<link rel=StyleSheet href="../css/book.css" type="text/css"/>

<title>TPTP Manual Test</title>
<style>
<!--
 




<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html xmlns:v="urn:schemas-microsoft-com:vml"
xmlns:o="urn:schemas-microsoft-com:office:office"
xmlns:w="urn:schemas-microsoft-com:office:word"
xmlns="http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
<link rel=StyleSheet href="../css/book.css" type="text/css"/>
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>TPTP Manual Test</title>
<style>
<!--
 




<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html>

<head>
<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
<link rel=StyleSheet href="../css/book.css" type="text/css"/>
<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2004" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="topic" />
<meta name="DC.Title" content="Analyzing manual test results" />
<meta name="abstract" content="This topic describes how to analyze results produced from running manual tests." />
<meta name="description" content="This topic describes how to analyze results produced from running manual tests." />
<meta name="DC.Relation" scheme="URI" content="../concepts/cmanualtestoverview.dita" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="analyzingmanualtestresults" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="../css/ibmdita.css" />
<link rel="stylesheet" type="text/css" href="../css/swg_info_common.css" />
<title>Analyzing manual test results</title>
</head>
<body id="analyzingmanualtestresults"><a name="analyzingmanualtestresults"><!-- --></a>

<body>

<div>

<h2>Analyzing manual test results</h2>

<p>The results of a test run are recorded in Test Log files of type <b>.execution</b>
in the project folder. Double-click on the .execution 
file to launch the <b>Execution</b>
view. The <b>Overview</b> tab is selected by default.</p>

<h3>Overview Tab</h3>

<p>In the General Information section, the Overview tab
provides the Name of the manual test and its Description (if provided). It also
gives the path to the execution file, for example: </p>

<p>/manualTests/exampleManualTest_x.execution</p>

<p>The link <b>Go to first fail</b> switches to the Events
tab and positions the Test Log at the first recorded failure in the
test.</p>

The Summary section reports the properties of the manual test: 
<ol>
	<li><b>Type</b> (Manual Test)</li>
	<li><b>File</b></li>
	<li><b>Host name</b> (localhost)</li>
	<li><b>Verdict</b></li>
	<li>Start and Finish times</li>
</ol>

The verdict is either pass, fail, inconclusive, or error.
error indicates an error within the manual test itself rather than an
error in the software being tested.

<h3>Events Tab</h3>

<p>Select the <b>Events</b> tab to see the test suite
execution record.</p>

<p>The left-hand (<b>Events</b>) pane contains a graphical,
tree-structure representation of the Test Log, and the right-hand (<b>Common
Properties</b>) pane contains information about the particular node that is
selected within the Test Log.</p>

<p>The execution tree-structure is a <b>chronological</b>
sequence of event nodes:</p>

<div align=center>

<table border=1 cellspacing=0 cellpadding=0>
 <tr>
  <td width=103 valign=top>
  <p><b>Node
  Type</b></p>
  </td>
  <td width=384 valign=top>
  <p><b>Meaning</b></p>
  </td>
 </tr>
 <tr>
  <td width=103 valign=top>
  <p>start</p>
  </td>
  <td width=384 valign=top>
  <p>Indicates
  the start of some process (e.g. invocation); provides time.</p>
  </td>
 </tr>
 <tr>
  <td width=103 valign=top>
  <p>stop</p>
  </td>
  <td width=384 valign=top>
  <p>Indicates
  the end of some process (e.g. invocation); provides time. Exactly as for <b>start</b>
  node except that the node type is <b>stop</b>.</p>
  </td>
 </tr>
 <tr>
  <td width=103 valign=top>
  <p>invocation</p>
  </td>
  <td width=384 valign=top>
  <p>Corresponds
  to a test case invocation; expands to show underlying node structure.</p>
  <p>In which
  the start/stop nodes are as above while the pass node indicates that the
  particular invocation involved passed the tester's criteria.</p>
  <p>&nbsp;</p>
  <p>The
  invocation outcome node (coded as pass, failed, error, inconclusive) lies between
  the start/stop nodes:</p>
  </td>
 </tr>
 <tr>
  <td width=103 valign=top>
  <p>message</p>
  </td>
  <td width=384 valign=top>
  <p>Provides
  information about a stage in the manual test; normally one at the beginning
  and end of a test.</p>
  </td>
 </tr>
</table>

</div>

<p>The <b>Previous fail</b> and <b>Next fail</b>
buttons move the focus within the history backwards (chronologically) and
forwards (chronologically) respectively to the next failure node.</p>

<p>Click on an event node in the <b>Events</b> pane to get
information about that event in the right-hand pane.</p>

<p>(C) Copyright IBM Corporation 2000, 2005. All Rights
Reserved.</p>

</div>

<div>
<p>
<b class="parentlink">Parent topic:</b> <a href="../concepts/cmanualtestoverview.htm" title="">Manual testing with TPTP</a><br />
</p>
</div><div class="runningfooter">(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.</div>
</body>

</html>




<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html>

<head>
<meta http-equiv=Content-Type content="text/html; charset=UTF-8"/>
<link rel=StyleSheet href="../css/book.css" type="text/css"/>


<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="task" />
<meta name="DC.Title" content="Creating a test deployment" />
<meta name="abstract" content="This topic describes how to create a deployment for your test suite. You must create a deployment before you can run a test." />
<meta name="description" content="This topic describes how to create a deployment for your test suite. You must create a deployment before you can run a test." />
<meta name="DC.Relation" scheme="URI" content="../concepts/ccommontestingtasksandconcepts.dita" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="creatingatestdeployment" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="../css/ibmdita.css" />
<link rel="stylesheet" type="text/css" href="../css/swg_info_common.css" />
<title>Creating a test deployment</title>

</head>
<body id="creatingatestdeployment"><a name="creatingatestdeployment"><!-- --></a>

<body>
<div><p>This topic describes how to create a deployment for your test suite.
You must create a deployment before you can run a test.</p>
<div class="p">A test deployment definition typically consists of one or more pairs
of test artifacts and locations. Test artifacts are test suites and datapools.
A location identifies the computer where you run the test suite. Hyades reads
the pairing and deploys the test artifacts on the computer specified. You
can also create a test deployment that specifies only a location; it does
not specify test artifacts. Such a deployment is convenient when you want
to run a specific test suite on a specific computer. In this case, you do
not need to create a test artifact for the test suite. You select the test
suite and the location-only deployment, and Hyades deploys the test suite
to the computer specified in the deployment definition and runs the test suite
on that computer.</div>
<div class="skipspace">To create a test deployment:</div>
<ol><li><span>In the Test Navigator select the test suite for which you want
to create a deployment. Click <span class="menucascade"><span class="uicontrol">File</span> &gt; <span class="uicontrol">New</span> &gt; <span class="uicontrol">Other</span></span>. The <span class="uicontrol">New</span> wizard
opens, as shown below. <br /><img src="../images/newwizard.gif" /><br /></span></li>
<li><span>Expand the <span class="uicontrol">Test</span> folder and the <span class="uicontrol">Test
Elements</span> folder, then select <span class="uicontrol">Deployment</span>.
Click <span class="uicontrol">Next</span>. The next page of the wizard opens, as shown
below. <br /><img src="../images/newdeployment.gif" /><br /></span></li>
<li><span>Navigate to the folder that will store the deployment file resource.
Enter a name for the file resource in the <span class="uicontrol">File name</span> field.
Click <span class="uicontrol">Next</span>. The next page of the wizard opens, as shown
below. <br /><img src="../images/newdeployment2.gif" /><br /></span></li>
<li><span>Enter a name and brief description for the deployment. The default
name for the deployment is the name you specified for the file resource.
The name that you specify here
is the one that appears in the Test Navigator. Click <span class="uicontrol">Next</span>.
The next page of the wizard opens, as shown below. <br /><img src="../images/newdeployment3.gif" /><br /></span></li>
<li><span>To create a deployment that consists of a location only, click <span class="uicontrol">Next</span> and
skip ahead to Step 10. When you run a test with such a deployment, Hyades
deploys that test suite to the location specified in the deployment. Otherwise,
click <span class="uicontrol">Add</span> to open the <span class="uicontrol">Add Artifact Association</span> page,
as shown below. <br /><img src="../images/addartifact.gif" /><br /></span></li>
<li><span>If you have previously defined one or more artifacts that you want
to use in this deployment, click <span class="uicontrol">Browse</span> and navigate
to the artifact. After you select the artifact, click <span class="uicontrol">Finish</span>.
To define a new artifact select <span class="uicontrol">Create a new resource</span> and
click <span class="uicontrol">Next</span>. The New Artifact wizard opens, as shown
below. <br /><img src="../images/newartifact.gif" /><br /></span></li>
<li><span>Navigate to the folder that will store the artifact file resource.
Enter a name for the artifact file resource in the <span class="uicontrol">File name</span> field.
Click <span class="uicontrol">Next</span>. The next page of the wizard opens, as shown
below. <br /><img src="../images/newartifact2.gif" /><br /></span></li>
<li><span>Enter a name and description for the artifact. The default name
is the name that you specified for the artifact file resource. The name you
specify here is the one that appears in the Test Navigator. Click <span class="uicontrol">Next</span>.
The next page of the wizard opens, as shown below. <br /><img src="../images/newartifact3.gif" /><br /></span></li>
<li><span>Click the boxes next to the test assets that you want to include
in the artifact. To see the folders that the test assets belong to click <span class="uicontrol">Show
Folders</span>. Click <span class="uicontrol">Finish</span>. The new artifact
appears in the list of artifacts to be added to the deployment, as shown below. <br /><img src="../images/newdeployment5.gif" /><br />To add another artifact
click <span class="uicontrol">Add</span> and repeat the steps. When you are satisfied
with the list of artifacts, click <span class="uicontrol">Next</span>. The next page
of the wizard appears, as shown below. <br /><img src="../images/newdeployment6.gif" /><br /></span></li>
<li><span>Click <span class="uicontrol">Add</span> to select a location to be associated
with the deployment. The Add Location Association dialog box opens, as shown
below. <br /><img src="../images/addlocation.gif" /><br /></span></li>
<li><span>To select an existing location resource click <span class="uicontrol">Browse</span> and
navigate to the location. To create a location, select <span class="uicontrol">Create a
new resource</span> and click <span class="uicontrol">Next</span>. The New Location
wizard opens, as shown below. <br /><img src="../images/addlocation2.gif" /><br /></span></li>
<li><span>Navigate to the folder that will store the location resource file.
Enter a name for the location resource file in the <span class="uicontrol">File name</span> field.
Click <span class="uicontrol">Next</span>. The next page of the wizard appears, as
shown below. <br /><img src="../images/addlocation3.gif" /><br /></span></li>
<li><span>Enter a name and brief description for the location. The default
name is the name that you specified for the location resource file. The name
you specify here is the name that appears in the Test Navigator. Click <span class="uicontrol">Finish</span>.
The new location appears in the list of locations to be added to the deployment,
as shown below. <br /><img src="../images/newdeployment7.gif" /><br />To
add another location click <span class="uicontrol">Add</span> and repeat the steps.
When you are satisfied with the list of locations to be added to the deployment,
click <span class="uicontrol">Next</span>. The next page of the wizard opens, as shown
below. <br /><img src="../images/newdeployment8.gif" /><br /></span></li>
<li><span>The left pane lists test artifacts and the right pane lists locations.
Create one or more pairs of test artifacts and locations by selecting one
from each pane and clicking <img src="../images/arrow.gif" />. By creating
pairs of artifacts and locations you are specifying which test artifacts should
be deployed to which computers when the test is run. If you are creating a
location-only deployment, the test artifacts pane will be empty. To remove
a pair, select it from the list and click <span class="uicontrol">Remove</span>. To
move a pair up in the list, select the pair and click <span class="uicontrol">Up</span>.
When you are satisfied with the list of pairs, click <span class="uicontrol">Finish</span>. </span></li>
<li><span>From the Test Navigator, double-click the location that you created.
The location's <span class="uicontrol">Overview</span> tab opens, as shown below. <br /><img src="../images/addlocation4.gif" /><br /></span></li>
<li><span>The default host name for the location is <kbd class="userinput">localhost</kbd>.
If the location is for another computer, enter the name of that computer in
the <span class="uicontrol">Host name</span> field. </span></li>
</ol>
</div>

<div>

<h1><a name=creatingatestdeployment></a>Creating a Test Deployment</h1>

<p>This topic describes how to create a deployment for your test suite. Unless
you make use of the default deployment to run your test locally, you must
create a deployment before you can run a test.</p>

<p>A test deployment definition typically consists of one or
more pairs of test artifacts and locations. Test artifacts are test suites and
datapools. A location identifies the computer where you run the test suite.
TPTP reads the pairing and deploys the test artifacts on the computer specified.
You can also create a test deployment that specifies only a location; it does
not specify test artifacts. Such a deployment is convenient when you want to
run a specific test suite on a specific computer. In this case, you do not need
to create a test artifact for the test suite. You select the test suite and the
location-only deployment, and TPTP deploys the test suite to the computer
specified in the deployment definition and runs the test suite on that
computer.</p>

<p>To create a test deployment:</p>

<ol>
	<li>
		<p>In
		the Test Navigator select the test suite for which you want to create a
		deployment. Select  <b>File</b><b> &gt; </b><b>New</b><b> &gt; </b><b>Other</b>. The New
		wizard opens.</p>
	</li>
	<li>
<p>Expand the Test folder and the Test Assets folder, then select Deployment.
Click <b>Next</b>. The next page of the wizard
opens.</p>
<p>Navigate to the folder that will store the deployment file
resource. Enter a name for the deployment in the name
field. Click <b>Next</b>. The next page of the
wizard opens: </p>
</li>
<li>
<p>Optionally enter a brief description for the deployment. Click
<b>Next</b>. The next page of the wizard opens.</p>
</li>
<li>
<p>(To create a deployment that consists of a location only,
click <b>Next</b> and skip ahead to <b>Step 9</b>).
When you run a test with such a deployment, TPTP deploys the test suite to the
location specified in the deployment. Otherwise, click Add
to open the Add Artifact Association page.</p>
</li>
<li>
<p>If you have previously defined one or more artifacts that
you want to use in this deployment, click <b>Browse</b>
and navigate to the artifact. After you select the artifact, click <b>Finish</b>. To define a new artifact check the <b>Create a new resource</b> button and click <b>Next</b>. The New Artifact wizard opens.</p>
</li>
<li>
<p>Navigate to the folder that will store the artifact file
resource. Enter a name for the artifact file resource in the Name field. Click <b>Next</b>.
The next page of the wizard opens.</p>
</li>
<li>
<p>Optionally enter a description for the artifact. Click <b>Next</b>. The next page of the wizard opens.</p>
</li>
<li>
<p>Click the boxes next to the test asset(s) that you want to
include in the artifact. Click <b>Finish</b>. The
new artifact appears in the list of artifacts to be added to the deployment.</p>
<p>
To add another artifact click Add and repeat the
steps. When you are satisfied with the list of artifacts, click <b>Next</b>. The next page of the wizard appears.</p>
</li>
<li>
<p>Click <b>Add</b> to select a
location to be associated with the deployment. The <b>Add Location Association</b>
dialog box opens, as above.</p>
</li>
<li>
<p>To select an existing location resource click <b>Browse</b> and navigate to the location. To create a
location, check the <b>Create a new resource</b>
button and click <b>Next</b>. The New Location
wizard opens. </p>

<p>Navigate to the folder that will store the location resource
file. Enter a name for the location resource file in the File
name field. Click <b>Next</b>. The next
page of the wizard appears.</p>
</li>
<li>
<p>Optionally
enter a description for the location. Click <b>Finish</b>.
The new location appears in the list of locations to be added to the
deployment.</p>
<p>
To add another location click <b>Add</b> and
repeat the steps. When you are satisfied with the list of locations to be added
to the deployment, click <b>Next</b>. The next
page of the wizard opens.</p>
</li>
<li>

<p>The
left-pane lists test artifacts and the right-pane lists locations. Create one
or more pairs of test artifacts and locations by selecting one from each pane
and clicking the down-arrow. By creating pairs of artifacts and locations you
are specifying which test artifacts should be deployed to which computers when
the test is run. If you are creating a location-only deployment, the test artifacts
pane will be empty. To remove a pair, select it from the list and click Remove. To move a pair up in the list, select the pair
and click Up. When you are satisfied with the list
of pairs, click Finish.</p>
</li>
</ol>

<p><strong>Related tasks</strong><br/>
	<a href="trunningmanualtestsuite.htm">Running a manual test</a><br/>
	<a href="tediting_manual_test.htm">Editing a manual test</a><br/>
	<a href="tanalyzingmanualtestresults.htm">Analyzing manual test results</a><br/>
</p>

<p><strong>Related reference</strong><br/>
	<a href="../ref/rtestlog.html">Test Log viewer</a><br/>
</p>
 
<p>(C) Copyright IBM Corporation 2000, 2005. All Rights
Reserved.</p>


</div>

</body>

</html>




<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html>

<head>
<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
<link rel=StyleSheet href="../css/book.css" type="text/css"/>

<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="task" />
<meta name="DC.Title" content="Creating a manual test" />
<meta name="abstract" content="This section describes the procedure for creating a manual test suite." />
<meta name="description" content="This section describes the procedure for creating a manual test suite." />
<meta name="DC.Relation" scheme="URI" content="../concepts/cmanualtestoverview.dita" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="creating_manual_test" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="../css/ibmdita.css" />
<link rel="stylesheet" type="text/css" href="../css/swg_info_common.css" />
<title>Creating a manual test</title>

</head>
<body id="creating_manual_test"><a name="creating_manual_test"><!-- --></a>

<body>
<div><p>This section describes the procedure for creating a manual test
suite.</p>
<ol><li><span>Click <span class="menucascade"><span class="uicontrol">File</span> &gt; <span class="uicontrol">New</span> &gt; <span class="uicontrol">Other</span></span></span></li>
<li><span>In the <span class="uicontrol">New</span> dialog box, shown below, expand
the <span class="uicontrol">Test</span> folder, expand the <span class="uicontrol">Test Suite</span> folder,
select <span class="uicontrol">Test Suite</span>, and click <span class="uicontrol">Next</span>. <br /><img src="../images/newmanualtest.gif" /><br /></span></li>
<li><span>The <span class="uicontrol">New Test Suite</span> wizard appears, as shown
below. <br /><img src="../images/newmanualtest2.gif" /><br />Navigate
to the folder that will contain the test suite.  Enter a name for the file
resource that will store the test suite in the <span class="uicontrol">File name</span> field.
 Click <span class="uicontrol">Next</span>. The next page of the wizard appears, as
shown below. <br /><img src="../images/newmanualtest3.gif" /><br /></span></li>
<li><span>Specify the name of the test suite definition and enter a description
of the test suite.  By default, the name of the test suite definition is the
same name that you specified for the file resource without the <kbd class="userinput">.testsuite</kbd> suffix.
The name that you specify here is the name that appears in the Test Navigator.
Click <span class="uicontrol">Finish</span> to close the wizard. The <span class="uicontrol">Test
Suite</span> dialog box opens and you can now edit the definition by
adding test methods and specifying behaviors that control how the methods
should be run.</span></li>
</ol>
</div>

<div>

<h2>Creating a manual test</h2>
<p>
This topic describes how to create a manual test suite.
</p>

<ol>
	<li>Click <b>File &gt; New &gt; Other</b>. The <b>New</b> dialog appears.</li>
	<li>Expand the <b>Test</b> folder, then select <b>TPTP Manual Test</b>.</li>
	<li>Click <b>Next</b> and name the the manual test, for example, <em id="CodeName">exampleManualTest</em>.</li>
	<li>Click <b>Next</b> and optionally provide a description for the manual test suite. Click <b>Finish</b>.</li>
	<li>A manual test testsuite file (<em id="CodeName">exampleManualTest.testsuite</em>) will be created and becomes visible in the Navigator.</li>
</ol>

<p><strong>Related tasks</strong><br />
<a href="tediting_manual_test.htm">Editing a manual test</a><br/>
<a href="trunningmanualtestsuite.htm">Running a manual test</a><br />
</p>

<p>(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.</p>

</div>

</body>

</html>




<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2004" />
<meta name="DC.rights.owner"
	content="(C) Copyright IBM Corporation 2004" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label"
	content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="task" />
<meta name="DC.Title" content="Editing a manual test" />
<meta name="abstract"
	content="This section describes how to edit your manual test suite." />
<meta name="description"
	content="This section describes how to edit your manual test suite." />
<meta name="DC.Relation" scheme="URI"
	content="../concepts/cmanualtestoverview.dita" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="editing_manual_test" />
<meta name="DC.Language" content="en-us" />

<link rel="stylesheet" type="text/css" href="../css/swg_info_common.css" />
<title>Editing a manual test</title>
</head>
<body id="editing_manual_test">
<a name="editing_manual_test"><!-- --></a>

<h1 class="topictitle1">Editing a manual test</h1>
<div>
<p>This section describes how to edit your manual test suite.</p>
<div class="p">You must have created a manual test suite.</div>
<ol>
	<li><span>In the <span class="uicontrol">Test Navigator</span>
	double-click the test suite entry to open the <span class="uicontrol">Test
	Suite </span> dialog box. The test suite opens in the <span
		class="uicontrol">Overview</span> tab with the two edit areas (<span
		class="uicontrol">General Information</span> and <span
		class="uicontrol">Test Cases</span>) expanded.</span></li>
	<li><span>The <span class="uicontrol">General Information</span> area
	displays the test suite's name, an optional description, test type, and
	name of the file containing the test suite. You can edit information
	appearing in boxes.</span></li>
	<li>The <span class="uicontrol">Test Cases</span> area lists the
	individual tests that make up the test suite. Click one of the test
	cases or <span class="uicontrol">More</span> to display the Test Cases
	view. To change the name or description of a test case, select the test
	case and enter new text in the <span class="uicontrol">Name</span> or <span
		class="uicontrol">Description</span> boxes. Use the <span
		class="uicontrol">Add</span> and <span class="uicontrol">Remove</span>
	buttons to add test cases and to remove existing cases. Use the <span
		class="uicontrol">Up</span> and <span class="uicontrol">Down</span>
	buttons to change the order of cases.</li>
	<li><span>Click the <span class="uicontrol">Behaviors</span> tab to
	display the Behaviors view. Behaviors let you control the order in
	which test cases are run; you do this by specifying invocations and
	loops. For example, in the figure shown below, <kbd class="userinput">test
	1</kbd> runs inside <kbd class="userinput">Loop 1</kbd>.<img
		src="../images/manualbehaviors.gif" /> 
		<br/>Use the <span
		class="uicontrol">Number of Iterations</span> box to specify how many
	times to execute the loop. With <span class="uicontrol">Synchronous</span>
	checked and more than one iteration specified, the loop iterations
	execute in sequence. With <span class="uicontrol">Synchronous</span>
	unchecked and more than one iteration specified, the loop iterations
	execute simultaneously. </span></li>
	<li><span>Use the <span class="uicontrol">Up</span> and <span
		class="uicontrol">Down</span> buttons to change the order of
	invocations and loops. Use the <span class="uicontrol">Add</span> and <span
		class="uicontrol">Remove</span> buttons to add and remove loops and
	invocations. After you create a loop you can add an invocation to it by
	right-clicking the loop and selecting <span class="menucascade"><span
		class="uicontrol">Add</span> &gt; <span class="uicontrol">Invocation</span></span>.
	The <span class="uicontrol">Test Invocation</span> dialog box appears.
	The top pane lists test cases in the test suite. The bottom pane lets
	you navigate to test cases in other test suites in your workspace. You
	can nest loops and create invocations that are outside of any loop.</span></li>
</ol>
</div>

<p><strong>Related tasks</strong><br />
<a href="tcreatingamanualtest.htm">Creating a manual test</a><br />
<a href="trunningmanualtestsuite.htm">Running a manual test</a><br />
</p>

<div class="runningfooter">(C) Copyright IBM Corporation 2000, 2004. All
Rights Reserved.</div>
</body>
</html>




<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html>

<head>
<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
<link rel=StyleSheet href="../css/book.css" type="text/css"/>
<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2004" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="task" />
<meta name="DC.Title" content="Running a manual test" />
<meta name="abstract" content="This topic describes how to create and run a manual test." />
<meta name="description" content="This topic describes how to create and run a manual test." />
<meta name="DC.Relation" scheme="URI" content="../concepts/cmanualtestoverview.dita" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="runningamanualtestsuite" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="../css/ibmdita.css" />
<link rel="stylesheet" type="text/css" href="../css/swg_info_common.css" />
<title>Running a manual test</title>
</head>
<body id="runningamanualtestsuite"><a name="runningamanualtestsuite"><!-- --></a>

<body>

<div>

<h2>Running a manual test</h2>
<p>This topic describes how to create and run a manual test.</p>
<ol>
	<li><a href="tprereqmanualtestconfiguration.htm">Preparing to run a manual test</a></li>	
	<li><a href="tcreatemanualtestconfiguration.htm">Creating a test configuration</a></li>	
	<li><a href="trunmanualtest.htm">Running the test configuration</a></li>	
<li class="skipspace"><span>To create a new configuration, click the <span class="uicontrol">New</span> button
on the bottom left. </span> <p>A new test configuration, initially
named <kbd class="userinput">New_Configuration</kbd>, is created. Change the name
if you like. Alternatively, expand <span class="uicontrol">Hyades Manual Test</span> and
click a listed configuration that you want to inspect or modify. The Run dialog
box opens in the Test tab.<br /><img src="../images/manualDeploy.gif" alt=" " /><br /></p>
</li>
<li class="skipspace"><span>In the <span class="uicontrol">Select Test to run</span> pane in the middle
listing all projects in the workspace, navigate to the project containing
the test to run and click it.</span></li>
<li class="skipspace"><span>In the <span class="uicontrol">Select a deployment</span> pane on the right
listing all defined deployments in the workspace, click the one to use for
this run.</span> <p>To run the test using default values, or using the
same values that you set during the previous test run, you can click <span class="uicontrol">Run</span> now
and stop reading.</p>
</li>
<li class="skipspace"><span>Click <span class="uicontrol">Apply</span> to save the selections on this
tab.</span></li>
<li class="skipspace"><span>Click <span class="uicontrol">Execution Results</span> to display that
tab, as shown below. <br /><img src="../images/manualconfig2.gif" /><br /> </span></li>
<li class="skipspace"><span>To overwrite the test results file that was used the last time
this test was run, rather than creating a new results file, check the box
beside <span class="uicontrol">Override existing Execution Results resource</span>.</span></li>
<li class="skipspace"><span>In the <span class="uicontrol">Location</span> box listing Java projects
in the workspace, click the one in which to store the test results.</span></li>
<li class="skipspace"><span>Click <span class="uicontrol">Apply</span> to save the selections on this
tab.</span></li>
<li class="skipspace"><span>Click <span class="uicontrol">Common</span> to display the <span class="uicontrol">Common</span> tab,
as shown below. <br /><img src="../images/manualconfig3.gif" /><br /></span></li>
<li class="skipspace"><span>When you run a test configuration, Eclipse creates a file, with
a <kbd class="userinput">.launch</kbd> suffix, containing metadata. If you select <span class="uicontrol">Local</span>,
Eclipse stores this file in your workspace's metadata folder, which is not
visible to other users. If you want other users to have access to the file,
select <span class="uicontrol">Shared</span>, click <span class="uicontrol">Browse</span>,
and navigate to a folder in your workspace where you want to store the file. </span></li>
<li class="skipspace"><span>To have the test configuration appear in the <span class="uicontrol">Run</span> favorites
toolbar menu, check this item in the <span class="uicontrol">Display in favorites menu
box</span>.</span></li>
<li class="skipspace"><span>Select <span class="uicontrol">Launch in background</span> to have Eclipse
run the test configuration in the background so that you can perform other
Eclipse tasks while the test runs. </span></li>
<li class="skipspace"><span>Click <span class="uicontrol">Apply</span> to save the settings for the
configuration. </span></li>
<li class="skipspace"><span>Click <span class="uicontrol">Run</span>. The Manual Remote Application
dialog box opens, as shown below. <br /><img src="../images/manualtestremote.gif" /><br /></span></li>
<li class="skipspace"><span>Navigate to a test in the left pane. The name and description of
the test appears in the right pane. After you perform the steps specified
in the test's description, indicate whether the test passed, failed, returned
an error, or was inconclusive by selecting a value in the <span class="uicontrol">Status</span> drop-down
list. Enter comments about the test results in the <span class="uicontrol">Info</span> field. </span></li>
<li class="skipspace"><span>Click <span class="uicontrol">Next</span> to save the test results and
move to the next test.</span></li>
<li class="skipspace"><span>When you finish running all tests, click <span class="uicontrol">End Execution</span> to
close the dialog box.</span></li>
</ol>


 
<p>(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.</p>

</div>

<div>
<p>
<b class="parentlink">Parent topic:</b> <a href="../concepts/cmanualtestoverview.htm" title="">Manual testing with TPTP</a><br />
</p>
</div><div class="runningfooter">(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.</div>
</body>

</html>




<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html xmlns:v="urn:schemas-microsoft-com:vml"
xmlns:o="urn:schemas-microsoft-com:office:office"
xmlns:w="urn:schemas-microsoft-com:office:word"
xmlns="http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=Content-Type content="text/html; charset=UTF-8"/>
<link rel=StyleSheet href="../css/book.css" type="text/css"/>

<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>Creating a test deployment</title>
<style>
<!--




<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html>

<head>
<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
<link rel=StyleSheet href="../css/book.css" type="text/css"/>
<title>Reference</title>
</head>

<body>
<div>
<h2>Reference</h2>
This section explains some of the subjects introduced in the 
<i>TPTP Tester guide</i> in detail.

<ul>
	<li><a href="rmanualcreate.htm">Generic launch configuration properties</a></li>
	<li><a href="rtestlog.html">Test Log viewer</a></li>
</ul>

<p>(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.</p>

</div>

</body>

</html>




<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html>

<head>
<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
<link rel=StyleSheet href="../css/book.css" type="text/css"/>
<title>Generic launch configuration properties</title>
</head>

<body>

<div>
<h2>Generic launch configuration properties</h2>
<p>Eclipse provides the <b>Common</b> tab at the right of the <b>Run</b> dialog for editing various generic launch configuration properties.  Select the <b>Common</b> 
tab at the right of the <b>Run</b> dialog to edit the following generic launch configuration properties:</p>

<ul>
	<li>When the launch configuration is saved by clicking <b>Run</b>  at the bottom of the <b>Run</b> dialog, a 
launch configuration file (<i>.launch</i>) is created and saved.  By default, the launch configuration file is saved in the workspace's <i>.metadata</i> 
directory.  The location for the .launch file may be changed to any directory in the workspace via the <b>Save as</b> pane of the <b>Common</b> tab.</li>
	<li>When rerunning a launch configuration, a shortcut may be associated with one or more favorites tool bar menus in the <b>Display in favorites menu</b> 
	pane of the <b>Common</b> tab.</li>
	<li>When a launch configuration is executed by clicking <b>Run</b>  at the bottom of the <b>Run</b> dialog, the <b>Console</b> view 
	is used for rendering standard output data and reading standard input data.  By default, the encoding of the <b>Console</b> view is the encoding for the
	local platform.  The encoding of the <b>Console</b> view may be changed to any valid encoding in the <b>Console Encoding</b> pane of the <b>Common</b> tab.</li>
	<li>When a launch configuration is executed, the standard output and standard input might display output data and read input data, respectively.  By default, the <b>Console</b> view is used for both the standard output and standard input.  
	The standard input may be disabled and the standard output may be changed to write or append to a local file in the <b>Standard Input and Output</b> pane of the 
	<b>Common</b> tab.</li>
	<li>When a launch configuration is executed, by default Eclipse will run the launch configuration 
	in the background so that the user may continue interacting with Eclipse.  To restrict the user from interacting with Eclipse until the execution has terminated, clear the <b>Launch
	in background</b> check box at the bottom of the <b>Common</b> tab. .</li>
</ul>

<br/>


<p><strong>Related concepts</strong><br/>
	<a href="../tasks/trunningmanualtestsuite.htm">Running a manual test</a><br/>
</p>
 
<p><strong>Related tasks</strong><br/>
   <a href="../tasks/tcreating_test_deployment.htm">Creating a test deployment</a><br/>
</p>

<p>(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.</p>

</div>

</body>

</html>




<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html>

<head>
<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
<link rel=StyleSheet href="../css/book.css" type="text/css"/>
<title>Creating a test launch configuration</title>
</head>

<body>

<div>
<h2>Creating a test configuration</h2>
<p>A new test configuration is required to run a manual test. 
When the test configuration is executed, a test log captures the 
launch of the manual test.</p>

<p>Open the <b>Run</b> dialog to create the test configuration.  
Right-click on a test suite file in the Test Navigator and select 
<b>Run As</b> &gt; <b>Run</b> from the pop-up menu.  
The <b>Run</b> dialog opens.</p>

<p>Create the test configuration by selecting the <b>Test</b> entry from the list 
of launch <b>Configurations</b> and clicking <b>New</b>.  The test configuration is created and 
by default is named New_configuration.  You may edit the default name of the test configuration in the 
<b>Name</b> field at the top of the <b>Run</b> dialog.</p>

<p>The test configuration requires an association to the manual test and its 
deployment.  Select the manual test 
and its deployment for the test configuration.  Select the <b>Test</b> tab at the right of the <b>Run</b> dialog 
and complete the following steps:</p>

<ol>
	<li>Select the manual test to run. Navigate to and select the manual test in the <b>1. Select test to run</b> pane of the <b>Test</b> tab.
	</li>
	<li>Select the deployment for running the manual test. Select the <i>local_deployment</i> deployment in the <b>2.
	Select a deployment</b> pane of the <b>Test</b> tab.</li>
	<li>
	<p>Optionally, you may override the default settings
	for the generated test log. By default, the test log's name is the same as the manual test  and it is saved in the same location
	as the manual test.  Select the <b>Test Logs</b> tab at the
	right of the <b>Run</b> dialog and complete the following steps:</p>

	<ul>
			<li>Clear the <b>Use defaults</b> check box at the top of the <b>Test Logs</b> tab.</li>
			<li>Edit the default name of the generated test log in the <b>Name</b> field under the <b>Use defaults</b> check box.</li>
			<li>Select the <b>Override existing test logs resource</b> check box under the <b>Name</b> field to override an existing test log with the same name in the same location.  
			If the check box is cleared, the generated test log will be uniquely named.</li>
			<li>Edit the default location of the generated test log in the <b>Location</b> pane at the bottom of the <b>Test Logs</b> tab.</li>
	</ul>
	</li>
	<li>Optionally edit the generic launch configuration properties</li>
	<li>Save the test configuration by clicking the <b>Apply</b> button at the bottom of the <b>Run</b> dialog.</li>
</ol>

<p></p>

<p><strong>Related tasks</strong><br/>
   <a href="trunningmanualtestsuite.htm">Running a manual test</a><br/>
   <a href="tcreating_test_deployment.htm">Creating a test deployment</a><br/>
</p>

<p><strong>Related reference</strong><br/>
   <a href="../ref/rmanualcreate.htm">Generic launch configuration properties</a><br/>
</p>

<p>(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.</p>

</div>

</body>

</html>




<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html>

<head>
<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
<link rel=StyleSheet href="../css/book.css" type="text/css"/>
<title>Preparing to run a manual test</title>
</head>

<body>

<div>

<h2>Preparing to run a manual test</h2>

<br/>

<p>To prepare to run a manual test, complete the following steps:</p>

<ol>
	<li>Open the <b>Test</b> perspective. Select <b>Window</b> &gt; <b>Open Perspective</b> &gt; <b>Other...</b> &gt; <b>Test</b> &gt; <b>OK</b>.</li>
	<li>Launch the Agent Controller.</li>
	<li>Optionally create a test deployment.</li> 
</ol>

<br/>

<p><strong>Related concepts</strong><br/>
   <a href="../concepts/cmanualtestoverview.htm">Manual testing with TPTP - overview</a><br/>
</p>
 
<p><strong>Related tasks</strong><br/>
   <a href="trunningmanualtestsuite.htm">Running a manual test</a><br/>
   <a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/tasks/tworkwac.html">Working with the Agent Controller</a><br/>
   <a href="tcreating_test_deployment.htm">Creating a test deployment</a><br/>
</p>

<p>(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.</p>

</div>

</body>

</html>




<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html>

<head>
<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
<link rel=StyleSheet href="../css/book.css" type="text/css"/>
<title>Running the test configuration</title>
</head>

<body>

<div>

<h2>Running the test configuration</h2>

<p>Run the test configuration by clicking the <b>Run</b> button at the bottom of the <b>Run</b> dialog.</p>

<p>When a manual test is executed, the <b>Manual Test View</b> is launched on the host as specified in the test deployment associated 
with the execution test launch configuration.  The <b>Manual Test View</b> is an independent Standard Widget Toolkit
window for executing a manual test.  </p>

<p>The <b>Manual Test View</b> displays the manual test as a hierarchal tree at the left of the <b>Manual Test View</b> for viewing and navigation.    The executed manual test is displayed at the root with loops and referenced manual tests 
as branches of the manual test tree.  Any manual test or loop node in the tree may be expanded and collapsed by selecting the node in the manual test tree and
selecting <b>View &gt; Expand node</b> and <b>View &gt; Collapse node</b>, respectively.  Individual manual test cases are displayed as leaves of the manual test tree.  
Selecting a node in the tree will display the details of that node at the right of the <b>Manual Test View</b>.</p> 

<p>
At any time during the execution of the manual test, the tester may record a message in the test log by selecting <b>Action &gt; Send message...</b>.  The <b>Manual Test View</b> 
may be terminated at any time during the execution of the manual test by selecting <b>File &gt; Exit</b>.
</p>

<p>When the <b>Manual Test View</b> initially appears, the tester may optionally capture contextual information on the execution of the manual test; for example, enter the tester's name.  Select <b>Start</b> to begin executing the individual manual test cases in the manual test.</p>

The first manual test case of the manual test is automatically selected.  The execution 
steps for the manual test case are displayed at the upper-right of the <b>Manual Test View</b>.  After completing the execution steps of the manual test case, 
input the status  at the lower-right of the <b>Manual Test View</b>:
<ul>
	<li>verdict (<b>pass</b>, <b>fail</b>, <b>error</b> or <b>inconclusive</b>)</li>
	<li>reason (<b>abort</b>, <b>did not complete</b>, <b>unknown</b>, <b>none</b> or <b>see description</b>) </li>
	<li>optional contextual information (for example, defect number for failures)</li>
	<li>attachments (for example, screen captures of a failure state or error message)</li>
</ul>

<p>
To record the status and contextual information in the test log and advance to the next manual test case, select the 
<b>Next</b> button at the lower-right of the <b>Manual Test View</b>.  At any time during the execution of the manual test, the tester may advance to the next 
manual test case by selecting <b>View &gt; Select task to execute...</b>.  Testers may execute the same manual test case multiple times by navigating to the manual
test case in the test tree and recording a new status, reason and optional contextual information and attachments.</p>
  
<p>When the manual test execution is complete, exit the <b>Manual Test View</b> by selecting <b>File &gt; Exit</b>.</p>



<p><strong>Related tasks</strong><br />
<a href="tcreatingamanualtest.htm">Creating a manual test</a><br/>
<a href="trunningmanualtestsuite.htm">Running a manual test</a><br />
<a href="tanalyzingmanualtestresults.htm">Analyzing manual test results</a><br/>
<a href="tcreating_test_deployment.htm">Creating a test deployment</a><br />
<a href="http://www.eclipse.org/swt/">Standard Widget Toolkit</a><br/>
</p>
<p><strong>Related reference</strong><br />
<a href="../ref/rmanualcreate.htm">Generic launch configuration properties</a></p>


<p>(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.</p>

</div>

</body>

</html>

Return to bug 110436

Lines 45-58 Link Here

(-)comptest_toc.xml (-7 / +11 lines)
45	<topic label="Reports on JUnit tests" href="junit/tptpJUnitTest_analysisReport.htm"/>	45	<topic label="Reports on JUnit tests" href="junit/tptpJUnitTest_analysisReport.htm"/>
46	<anchor id="test_junit"/>	46	<anchor id="test_junit"/>
47	</topic>	47	</topic>
48	<topic label="Manual testing with TPTP" href="mtest/tptpManualTest_intro.htm">	48	<topic label="Manual testing with TPTP" href="concepts/cmanualtestoverview.htm">
49	<topic label="Building a manual test" href="mtest/tptpManualTest_building.htm"/>	49	<topic label="Creating a manual test" href="tasks/tcreatingamanualtest.htm"/>
50	<topic label="Editing a manual test" href="mtest/tptpManualTest_editor.htm"/>	50	<topic label="Editing a manual test" href="tasks/tediting_manual_test.htm"/>
51	<topic label="Running a manual test" href="mtest/tptpManualTest_run.htm"/>	51	<topic label="Running a manual test" href="tasks/trunningmanualtestsuite.htm"/>
52	<topic label="Analyzing manual test results" href="mtest/tptpManualTest_analysis.htm"/>	52	<topic label="Analyzing manual test results" href="tasks/tanalyzingmanualtestresults.htm"/>
53	<topic label="Example manual test deployment" href="mtest/tptpManualTestDeployExample.htm"/>	53	<topic label="Generic launch configuration properties" href="ref/rmanualcreate.htm"/>
54	<anchor id="test_manual"/>	54	<anchor id="test_manual"/>
55	</topic>	55	</topic>
56	<anchor id="test_results"/>	56	<anchor id="test_results"/>
57	<anchor id="reference"/>	57	<topic label="Reference" href="ref/refintro.html">
		58	<topic label="Generic launch configuration properties" href="ref/rmanualcreate.htm"/>
		59	<topic label="Test Log viewer" href="ref/rtestlog.html"/>
		60	<anchor id="reference"/>
		61	</topic>
58	</toc>	62	</toc>

Added Link Here

(-)tasks/trunmanualtest.htm (+73 lines)
1	<?xml version="1.0" encoding="ISO-8859-1"?>
2
3	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
4	<html>
5
6	<head>
7	<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
8	<link rel=StyleSheet href="../css/book.css" type="text/css"/>
9	<title>Running the test configuration</title>
10	</head>
11
12	<body>
13
14	<div>
15
16	<h2>Running the test configuration</h2>
17
18	<p>Run the test configuration by clicking the <b>Run</b> button at the bottom of the <b>Run</b> dialog.</p>
19
20	<p>When a manual test is executed, the <b>Manual Test View</b> is launched on the host as specified in the test deployment associated
21	with the execution test launch configuration. The <b>Manual Test View</b> is an independent Standard Widget Toolkit
22	window for executing a manual test. </p>
23
24	<p>The <b>Manual Test View</b> displays the manual test as a hierarchal tree at the left of the <b>Manual Test View</b> for viewing and navigation. The executed manual test is displayed at the root with loops and referenced manual tests
25	as branches of the manual test tree. Any manual test or loop node in the tree may be expanded and collapsed by selecting the node in the manual test tree and
26	selecting <b>View > Expand node</b> and <b>View > Collapse node</b>, respectively. Individual manual test cases are displayed as leaves of the manual test tree.
27	Selecting a node in the tree will display the details of that node at the right of the <b>Manual Test View</b>.</p>
28
29	<p>
30	At any time during the execution of the manual test, the tester may record a message in the test log by selecting <b>Action > Send message...</b>. The <b>Manual Test View</b>
31	may be terminated at any time during the execution of the manual test by selecting <b>File > Exit</b>.
32	</p>
33
34	<p>When the <b>Manual Test View</b> initially appears, the tester may optionally capture contextual information on the execution of the manual test; for example, enter the tester's name. Select <b>Start</b> to begin executing the individual manual test cases in the manual test.</p>
35
36	The first manual test case of the manual test is automatically selected. The execution
37	steps for the manual test case are displayed at the upper-right of the <b>Manual Test View</b>. After completing the execution steps of the manual test case,
38	input the status at the lower-right of the <b>Manual Test View</b>:
39	<ul>
40	<li>verdict (<b>pass</b>, <b>fail</b>, <b>error</b> or <b>inconclusive</b>)</li>
41	<li>reason (<b>abort</b>, <b>did not complete</b>, <b>unknown</b>, <b>none</b> or <b>see description</b>) </li>
42	<li>optional contextual information (for example, defect number for failures)</li>
43	<li>attachments (for example, screen captures of a failure state or error message)</li>
44	</ul>
45
46	<p>
47	To record the status and contextual information in the test log and advance to the next manual test case, select the
48	<b>Next</b> button at the lower-right of the <b>Manual Test View</b>. At any time during the execution of the manual test, the tester may advance to the next
49	manual test case by selecting <b>View > Select task to execute...</b>. Testers may execute the same manual test case multiple times by navigating to the manual
50	test case in the test tree and recording a new status, reason and optional contextual information and attachments.</p>
51
52	<p>When the manual test execution is complete, exit the <b>Manual Test View</b> by selecting <b>File > Exit</b>.</p>
53
54
55
56	<p><strong>Related tasks</strong><br />
57	<a href="tcreatingamanualtest.htm">Creating a manual test</a><br/>
58	<a href="trunningmanualtestsuite.htm">Running a manual test</a><br />
59	<a href="tanalyzingmanualtestresults.htm">Analyzing manual test results</a><br/>
60	<a href="tcreating_test_deployment.htm">Creating a test deployment</a><br />
61	<a href="http://www.eclipse.org/swt/">Standard Widget Toolkit</a><br/>
62	</p>
63	<p><strong>Related reference</strong><br />
64	<a href="../ref/rmanualcreate.htm">Generic launch configuration properties</a></p>
65
66
67	<p>(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.</p>
68
69	</div>
70
71	</body>
72
73	</html>

Lines 10-16 Link Here

(-)concepts/cmanualtestoverview.htm (-3 / +3 lines)
10	<meta name="Robots" content="index,follow" />	10	<meta name="Robots" content="index,follow" />
11	<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />	11	<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
12	<meta name="DC.Type" content="concept" />	12	<meta name="DC.Type" content="concept" />
13	<meta name="DC.Title" content="Manual testing with TPTP" />	13	<meta name="DC.Title" content="Manual testing with TPTP - overview" />
14	<meta name="DC.Relation" scheme="URI" content="../tasks/tcreatingamanualtest.dita" />	14	<meta name="DC.Relation" scheme="URI" content="../tasks/tcreatingamanualtest.dita" />
15	<meta name="DC.Relation" scheme="URI" content="../tasks/tediting_manual_test.dita" />	15	<meta name="DC.Relation" scheme="URI" content="../tasks/tediting_manual_test.dita" />
16	<meta name="DC.Relation" scheme="URI" content="../tasks/trunningmanualtestsuite.dita" />	16	<meta name="DC.Relation" scheme="URI" content="../tasks/trunningmanualtestsuite.dita" />
Lines 24-34 Link Here
24	<!-- GSA ADP Schedule Contract with IBM Corp. -->	24	<!-- GSA ADP Schedule Contract with IBM Corp. -->
25	<link rel="stylesheet" type="text/css" href="../css/ibmdita.css" />	25	<link rel="stylesheet" type="text/css" href="../css/ibmdita.css" />
26	<link rel="stylesheet" type="text/css" href="../css/swg_info_common.css" />	26	<link rel="stylesheet" type="text/css" href="../css/swg_info_common.css" />
27	<title>Manual testing with TPTP</title>	27	<title>Manual testing with TPTP - overview</title>
28	</head>	28	</head>
29	<body id="manualtestoverview"><a name="manualtestoverview"><!-- --></a>	29	<body id="manualtestoverview"><a name="manualtestoverview"><!-- --></a>
30		30
31	<h1 class="topictitle1">Manual testing with TPTP</h1>	31	<h1 class="topictitle1">Manual testing with TPTP - overview</h1>
32	<div><p>A manual test describes a procedure that a human tester performs to verify	32	<div><p>A manual test describes a procedure that a human tester performs to verify
33	whether a feature is working. The Eclipse test and performance tools platform	33	whether a feature is working. The Eclipse test and performance tools platform
34	(TPTP) supports assisted manual testing.</p>	34	(TPTP) supports assisted manual testing.</p>

Removed Link Here

(-)mtest/tptpManualTestDeployExample.htm (-23 lines)
1	<?xml version="1.0" encoding="ISO-8859-1"?>
2
3	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
4	<html xmlns:v="urn:schemas-microsoft-com:vml"
5	xmlns:o="urn:schemas-microsoft-com:office:office"
6	xmlns:w="urn:schemas-microsoft-com:office:word"
7	xmlns="http://www.w3.org/TR/REC-html40">
8
9	<head>
10	<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
11	<link rel=StyleSheet href="../css/book.css" type="text/css"/>
12	<!--[if !mso]>
13	<style>
14	v\:* {behavior:url(#default#VML);}
15	o\:* {behavior:url(#default#VML);}
16	w\:* {behavior:url(#default#VML);}
17	.shape {behavior:url(#default#VML);}
18	</style>
19	<![endif]-->
20	<title>TPTP Manual Test</title>
21	<style>
22	<!--
23

Removed Link Here

(-)mtest/tptpManualTest_analysis.htm (-23 lines)
1	<?xml version="1.0" encoding="ISO-8859-1"?>
2
3	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
4	<html xmlns:v="urn:schemas-microsoft-com:vml"
5	xmlns:o="urn:schemas-microsoft-com:office:office"
6	xmlns:w="urn:schemas-microsoft-com:office:word"
7	xmlns="http://www.w3.org/TR/REC-html40">
8
9	<head>
10	<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
11	<link rel=StyleSheet href="../css/book.css" type="text/css"/>
12	<!--[if !mso]>
13	<style>
14	v\:* {behavior:url(#default#VML);}
15	o\:* {behavior:url(#default#VML);}
16	w\:* {behavior:url(#default#VML);}
17	.shape {behavior:url(#default#VML);}
18	</style>
19	<![endif]-->
20	<title>TPTP Manual Test</title>
21	<style>
22	<!--
23

Removed Link Here

(-)mtest/tptpManualTest_building.htm (-23 lines)
1	<?xml version="1.0" encoding="ISO-8859-1"?>
2
3	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
4	<html xmlns:v="urn:schemas-microsoft-com:vml"
5	xmlns:o="urn:schemas-microsoft-com:office:office"
6	xmlns:w="urn:schemas-microsoft-com:office:word"
7	xmlns="http://www.w3.org/TR/REC-html40">
8
9	<head>
10	<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
11	<link rel=StyleSheet href="../css/book.css" type="text/css"/>
12	<!--[if !mso]>
13	<style>
14	v\:* {behavior:url(#default#VML);}
15	o\:* {behavior:url(#default#VML);}
16	w\:* {behavior:url(#default#VML);}
17	.shape {behavior:url(#default#VML);}
18	</style>
19	<![endif]-->
20	<title>TPTP Manual Test</title>
21	<style>
22	<!--
23

Removed Link Here

(-)mtest/tptpManualTest_editor.htm (-23 lines)
1	<?xml version="1.0" encoding="ISO-8859-1"?>
2
3	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
4	<html xmlns:v="urn:schemas-microsoft-com:vml"
5	xmlns:o="urn:schemas-microsoft-com:office:office"
6	xmlns:w="urn:schemas-microsoft-com:office:word"
7	xmlns="http://www.w3.org/TR/REC-html40">
8
9	<head>
10	<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
11	<link rel=StyleSheet href="../css/book.css" type="text/css"/>
12	<!--[if !mso]>
13	<style>
14	v\:* {behavior:url(#default#VML);}
15	o\:* {behavior:url(#default#VML);}
16	w\:* {behavior:url(#default#VML);}
17	.shape {behavior:url(#default#VML);}
18	</style>
19	<![endif]-->
20	<title>TPTP Manual Test</title>
21	<style>
22	<!--
23

Removed Link Here

(-)mtest/tptpManualTest_intro.htm (-16 lines)
1	<?xml version="1.0" encoding="ISO-8859-1"?>
2
3	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
4	<html xmlns:v="urn:schemas-microsoft-com:vml"
5	xmlns:o="urn:schemas-microsoft-com:office:office"
6	xmlns:w="urn:schemas-microsoft-com:office:word"
7	xmlns="http://www.w3.org/TR/REC-html40">
8
9	<head>
10	<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
11	<link rel=StyleSheet href="../css/book.css" type="text/css"/>
12
13	<title>TPTP Manual Test</title>
14	<style>
15	<!--
16

Removed Link Here

(-)mtest/tptpManualTest_run.htm (-23 lines)
1	<?xml version="1.0" encoding="ISO-8859-1"?>
2
3	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
4	<html xmlns:v="urn:schemas-microsoft-com:vml"
5	xmlns:o="urn:schemas-microsoft-com:office:office"
6	xmlns:w="urn:schemas-microsoft-com:office:word"
7	xmlns="http://www.w3.org/TR/REC-html40">
8
9	<head>
10	<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
11	<link rel=StyleSheet href="../css/book.css" type="text/css"/>
12	<!--[if !mso]>
13	<style>
14	v\:* {behavior:url(#default#VML);}
15	o\:* {behavior:url(#default#VML);}
16	w\:* {behavior:url(#default#VML);}
17	.shape {behavior:url(#default#VML);}
18	</style>
19	<![endif]-->
20	<title>TPTP Manual Test</title>
21	<style>
22	<!--
23

Lines 1-57 Link Here

(-)tasks/tanalyzingmanualtestresults.htm (-48 / +127 lines)
1	<?xml version="1.0" encoding="UTF-8"?>	1	<?xml version="1.0" encoding="ISO-8859-1"?>
2	<!DOCTYPE html	2
3	PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">	3	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
4	<html>	4	<html>
		5
5	<head>	6	<head>
6	<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />	7	<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
7	<meta name="copyright" content="(C) Copyright IBM Corporation 2004" />	8	<link rel=StyleSheet href="../css/book.css" type="text/css"/>
8	<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2004" />
9	<meta name="security" content="public" />
10	<meta name="Robots" content="index,follow" />
11	<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
12	<meta name="DC.Type" content="topic" />
13	<meta name="DC.Title" content="Analyzing manual test results" />
14	<meta name="abstract" content="This topic describes how to analyze results produced from running manual tests." />
15	<meta name="description" content="This topic describes how to analyze results produced from running manual tests." />
16	<meta name="DC.Relation" scheme="URI" content="../concepts/cmanualtestoverview.dita" />
17	<meta name="DC.Format" content="XHTML" />
18	<meta name="DC.Identifier" content="analyzingmanualtestresults" />
19	<meta name="DC.Language" content="en-us" />
20	<!-- All rights reserved. Licensed Materials Property of IBM -->
21	<!-- US Government Users Restricted Rights -->
22	<!-- Use, duplication or disclosure restricted by -->
23	<!-- GSA ADP Schedule Contract with IBM Corp. -->
24	<link rel="stylesheet" type="text/css" href="../css/ibmdita.css" />
25	<link rel="stylesheet" type="text/css" href="../css/swg_info_common.css" />
26	<title>Analyzing manual test results</title>	9	<title>Analyzing manual test results</title>
27	</head>	10	</head>
28	<body id="analyzingmanualtestresults"><a name="analyzingmanualtestresults"><!-- --></a>
29		11
30	<h1 class="topictitle1">Analyzing manual test results</h1>	12	<body>
31	<div><p>This topic describes how to analyze results produced from running	13
32	manual tests.</p>	14	<div>
33	<p>After you run a manual test suite, the results appear in the Test Navigator,	15
34	as shown below. <br /><img src="../images/manualtestresults.gif" /><br /></p>	16	<h2>Analyzing manual test results</h2>
35	<p>Double-click the results entry to open the <span class="uicontrol">Overview</span> tab	17
36	of the Execution dialog box, as shown below. <br /><img src="../images/manualtestresults2.gif" /><br /></p>	18	<p>The results of a test run are recorded in Test Log files of type <b>.execution</b>
37	<div class="p">The execution summary indicates the test suite's verdict and the length	19	in the project folder. Double-click on the .execution
38	of time it took to run the test suite. The verdict is one of the following:<ul><li><span class="uicontrol">pass</span></li>	20	file to launch the <b>Execution</b>
39	<li><span class="uicontrol">fail</span></li>	21	view. The <b>Overview</b> tab is selected by default.</p>
40	<li><span class="uicontrol">inconclusive</span></li>	22
41	<li><span class="uicontrol">error</span> (meaning that the test itself	23	<h3>Overview Tab</h3>
42	contains an error)</li>	24
43	</ul>	25	<p>In the General Information section, the Overview tab
		26	provides the Name of the manual test and its Description (if provided). It also
		27	gives the path to the execution file, for example: </p>
		28
		29	<p>/manualTests/exampleManualTest_x.execution</p>
		30
		31	<p>The link <b>Go to first fail</b> switches to the Events
		32	tab and positions the Test Log at the first recorded failure in the
		33	test.</p>
		34
		35	The Summary section reports the properties of the manual test:
		36	<ol>
		37	<li><b>Type</b> (Manual Test)</li>
		38	<li><b>File</b></li>
		39	<li><b>Host name</b> (localhost)</li>
		40	<li><b>Verdict</b></li>
		41	<li>Start and Finish times</li>
		42	</ol>
		43
		44	The verdict is either pass, fail, inconclusive, or error.
		45	error indicates an error within the manual test itself rather than an
		46	error in the software being tested.
		47
		48	<h3>Events Tab</h3>
		49
		50	<p>Select the <b>Events</b> tab to see the test suite
		51	execution record.</p>
		52
		53	<p>The left-hand (<b>Events</b>) pane contains a graphical,
		54	tree-structure representation of the Test Log, and the right-hand (<b>Common
		55	Properties</b>) pane contains information about the particular node that is
		56	selected within the Test Log.</p>
		57
		58	<p>The execution tree-structure is a <b>chronological</b>
		59	sequence of event nodes:</p>
		60
		61	<div align=center>
		62
		63	<table border=1 cellspacing=0 cellpadding=0>
		64	<tr>
		65	<td width=103 valign=top>
		66	<p><b>Node
		67	Type</b></p>
		68	</td>
		69	<td width=384 valign=top>
		70	<p><b>Meaning</b></p>
		71	</td>
		72	</tr>
		73	<tr>
		74	<td width=103 valign=top>
		75	<p>start</p>
		76	</td>
		77	<td width=384 valign=top>
		78	<p>Indicates
		79	the start of some process (e.g. invocation); provides time.</p>
		80	</td>
		81	</tr>
		82	<tr>
		83	<td width=103 valign=top>
		84	<p>stop</p>
		85	</td>
		86	<td width=384 valign=top>
		87	<p>Indicates
		88	the end of some process (e.g. invocation); provides time. Exactly as for <b>start</b>
		89	node except that the node type is <b>stop</b>.</p>
90	</td>
91	</tr>
92	<tr>
93	<td width=103 valign=top>
94	<p>invocation</p>
95	</td>
96	<td width=384 valign=top>
97	<p>Corresponds
98	to a test case invocation; expands to show underlying node structure.</p>
99	<p>In which
100	the start/stop nodes are as above while the pass node indicates that the
101	particular invocation involved passed the tester's criteria.</p>
102	<p> </p>
103	<p>The
104	invocation outcome node (coded as pass, failed, error, inconclusive) lies between
105	the start/stop nodes:</p>
106	</td>
107	</tr>
108	<tr>
109	<td width=103 valign=top>
110	<p>message</p>
111	</td>
112	<td width=384 valign=top>
113	<p>Provides
114	information about a stage in the manual test; normally one at the beginning
115	and end of a test.</p>
116	</td>
117	</tr>
118	</table>
119
44	</div>	120	</div>
45	<p>To view the details of the test suite execution, click the <span class="uicontrol">Events</span> tab.	121
46	The <span class="uicontrol">Events</span> tab opens, as shown below. <br /><img src="../images/manualtestresults3.gif" /><br /></p>	122	<p>The <b>Previous fail</b> and <b>Next fail</b>
47	<p>Navigate to an event in the left pane to see details about that event in	123	buttons move the focus within the history backwards (chronologically) and
48	the fields on the right. </p>	124	forwards (chronologically) respectively to the next failure node.</p>
		125
		126	<p>Click on an event node in the <b>Events</b> pane to get
		127	information about that event in the right-hand pane.</p>
		128
		129	<p>(C) Copyright IBM Corporation 2000, 2005. All Rights
		130	Reserved.</p>
		131
49	</div>	132	</div>
50		133
51	<div>
52	<p>
53	<b class="parentlink">Parent topic:</b> <a href="../concepts/cmanualtestoverview.htm" title="">Manual testing with TPTP</a><br />
54	</p>
55	</div><div class="runningfooter">(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.</div>
56	</body>	134	</body>
57	</html>	135
		136	</html>

Lines 1-130 Link Here

(-)tasks/tcreating_test_deployment.htm (-118 / +134 lines)
1	<?xml version="1.0" encoding="UTF-8"?>	1	<?xml version="1.0" encoding="UTF-8"?>
2	<!DOCTYPE html	2
3	PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">	3	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
4	<html>	4	<html>
		5
5	<head>	6	<head>
6	<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />	7	<meta http-equiv=Content-Type content="text/html; charset=UTF-8"/>
7	<meta name="copyright" content="(C) Copyright IBM Corporation 2004" />	8	<link rel=StyleSheet href="../css/book.css" type="text/css"/>
8	<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2004" />	9
9	<meta name="security" content="public" />	10
10	<meta name="Robots" content="index,follow" />
11	<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
12	<meta name="DC.Type" content="task" />
13	<meta name="DC.Title" content="Creating a test deployment" />
14	<meta name="abstract" content="This topic describes how to create a deployment for your test suite. You must create a deployment before you can run a test." />
15	<meta name="description" content="This topic describes how to create a deployment for your test suite. You must create a deployment before you can run a test." />
16	<meta name="DC.Relation" scheme="URI" content="../concepts/ccommontestingtasksandconcepts.dita" />
17	<meta name="DC.Format" content="XHTML" />
18	<meta name="DC.Identifier" content="creatingatestdeployment" />
19	<meta name="DC.Language" content="en-us" />
20	<!-- All rights reserved. Licensed Materials Property of IBM -->
21	<!-- US Government Users Restricted Rights -->
22	<!-- Use, duplication or disclosure restricted by -->
23	<!-- GSA ADP Schedule Contract with IBM Corp. -->
24	<link rel="stylesheet" type="text/css" href="../css/ibmdita.css" />
25	<link rel="stylesheet" type="text/css" href="../css/swg_info_common.css" />
26	<title>Creating a test deployment</title>	11	<title>Creating a test deployment</title>
		12
27	</head>	13	</head>
28	<body id="creatingatestdeployment"><a name="creatingatestdeployment"><!-- --></a>
29		14
30	<h1 class="topictitle1">Creating a test deployment</h1>	15	<body>
31	<div><p>This topic describes how to create a deployment for your test suite.
32	You must create a deployment before you can run a test.</p>
33	<div class="p">A test deployment definition typically consists of one or more pairs
34	of test artifacts and locations. Test artifacts are test suites and datapools.
35	A location identifies the computer where you run the test suite. Hyades reads
36	the pairing and deploys the test artifacts on the computer specified. You
37	can also create a test deployment that specifies only a location; it does
38	not specify test artifacts. Such a deployment is convenient when you want
39	to run a specific test suite on a specific computer. In this case, you do
40	not need to create a test artifact for the test suite. You select the test
41	suite and the location-only deployment, and Hyades deploys the test suite
42	to the computer specified in the deployment definition and runs the test suite
43	on that computer.</div>
44	<div class="skipspace">To create a test deployment:</div>
45	<ol><li><span>In the Test Navigator select the test suite for which you want
46	to create a deployment. Click <span class="menucascade"><span class="uicontrol">File</span> > <span class="uicontrol">New</span> > <span class="uicontrol">Other</span></span>. The <span class="uicontrol">New</span> wizard
47	opens, as shown below. <br /><img src="../images/newwizard.gif" /><br /></span></li>
48	<li><span>Expand the <span class="uicontrol">Test</span> folder and the <span class="uicontrol">Test
49	Elements</span> folder, then select <span class="uicontrol">Deployment</span>.
50	Click <span class="uicontrol">Next</span>. The next page of the wizard opens, as shown
51	below. <br /><img src="../images/newdeployment.gif" /><br /></span></li>
52	<li><span>Navigate to the folder that will store the deployment file resource.
53	Enter a name for the file resource in the <span class="uicontrol">File name</span> field.
54	Click <span class="uicontrol">Next</span>. The next page of the wizard opens, as shown
55	below. <br /><img src="../images/newdeployment2.gif" /><br /></span></li>
56	<li><span>Enter a name and brief description for the deployment. The default
57	name for the deployment is the name you specified for the file resource.
58	The name that you specify here
59	is the one that appears in the Test Navigator. Click <span class="uicontrol">Next</span>.
60	The next page of the wizard opens, as shown below. <br /><img src="../images/newdeployment3.gif" /><br /></span></li>
61	<li><span>To create a deployment that consists of a location only, click <span class="uicontrol">Next</span> and
62	skip ahead to Step 10. When you run a test with such a deployment, Hyades
63	deploys that test suite to the location specified in the deployment. Otherwise,
64	click <span class="uicontrol">Add</span> to open the <span class="uicontrol">Add Artifact Association</span> page,
65	as shown below. <br /><img src="../images/addartifact.gif" /><br /></span></li>
66	<li><span>If you have previously defined one or more artifacts that you want
67	to use in this deployment, click <span class="uicontrol">Browse</span> and navigate
68	to the artifact. After you select the artifact, click <span class="uicontrol">Finish</span>.
69	To define a new artifact select <span class="uicontrol">Create a new resource</span> and
70	click <span class="uicontrol">Next</span>. The New Artifact wizard opens, as shown
71	below. <br /><img src="../images/newartifact.gif" /><br /></span></li>
72	<li><span>Navigate to the folder that will store the artifact file resource.
73	Enter a name for the artifact file resource in the <span class="uicontrol">File name</span> field.
74	Click <span class="uicontrol">Next</span>. The next page of the wizard opens, as shown
75	below. <br /><img src="../images/newartifact2.gif" /><br /></span></li>
76	<li><span>Enter a name and description for the artifact. The default name
77	is the name that you specified for the artifact file resource. The name you
78	specify here is the one that appears in the Test Navigator. Click <span class="uicontrol">Next</span>.
79	The next page of the wizard opens, as shown below. <br /><img src="../images/newartifact3.gif" /><br /></span></li>
80	<li><span>Click the boxes next to the test assets that you want to include
81	in the artifact. To see the folders that the test assets belong to click <span class="uicontrol">Show
82	Folders</span>. Click <span class="uicontrol">Finish</span>. The new artifact
83	appears in the list of artifacts to be added to the deployment, as shown below. <br /><img src="../images/newdeployment5.gif" /><br />To add another artifact
84	click <span class="uicontrol">Add</span> and repeat the steps. When you are satisfied
85	with the list of artifacts, click <span class="uicontrol">Next</span>. The next page
86	of the wizard appears, as shown below. <br /><img src="../images/newdeployment6.gif" /><br /></span></li>
87	<li><span>Click <span class="uicontrol">Add</span> to select a location to be associated
88	with the deployment. The Add Location Association dialog box opens, as shown
89	below. <br /><img src="../images/addlocation.gif" /><br /></span></li>
90	<li><span>To select an existing location resource click <span class="uicontrol">Browse</span> and
91	navigate to the location. To create a location, select <span class="uicontrol">Create a
92	new resource</span> and click <span class="uicontrol">Next</span>. The New Location
93	wizard opens, as shown below. <br /><img src="../images/addlocation2.gif" /><br /></span></li>
94	<li><span>Navigate to the folder that will store the location resource file.
95	Enter a name for the location resource file in the <span class="uicontrol">File name</span> field.
96	Click <span class="uicontrol">Next</span>. The next page of the wizard appears, as
97	shown below. <br /><img src="../images/addlocation3.gif" /><br /></span></li>
98	<li><span>Enter a name and brief description for the location. The default
99	name is the name that you specified for the location resource file. The name
100	you specify here is the name that appears in the Test Navigator. Click <span class="uicontrol">Finish</span>.
101	The new location appears in the list of locations to be added to the deployment,
102	as shown below. <br /><img src="../images/newdeployment7.gif" /><br />To
103	add another location click <span class="uicontrol">Add</span> and repeat the steps.
104	When you are satisfied with the list of locations to be added to the deployment,
105	click <span class="uicontrol">Next</span>. The next page of the wizard opens, as shown
106	below. <br /><img src="../images/newdeployment8.gif" /><br /></span></li>
107	<li><span>The left pane lists test artifacts and the right pane lists locations.
108	Create one or more pairs of test artifacts and locations by selecting one
109	from each pane and clicking <img src="../images/arrow.gif" />. By creating
110	pairs of artifacts and locations you are specifying which test artifacts should
111	be deployed to which computers when the test is run. If you are creating a
112	location-only deployment, the test artifacts pane will be empty. To remove
113	a pair, select it from the list and click <span class="uicontrol">Remove</span>. To
114	move a pair up in the list, select the pair and click <span class="uicontrol">Up</span>.
115	When you are satisfied with the list of pairs, click <span class="uicontrol">Finish</span>. </span></li>
116	<li><span>From the Test Navigator, double-click the location that you created.
117	The location's <span class="uicontrol">Overview</span> tab opens, as shown below. <br /><img src="../images/addlocation4.gif" /><br /></span></li>
118	<li><span>The default host name for the location is <kbd class="userinput">localhost</kbd>.
119	If the location is for another computer, enter the name of that computer in
120	the <span class="uicontrol">Host name</span> field. </span></li>
121	</ol>
122	</div>
123		16
124	<div>	17	<div>
		18
		19	<h1><a name=creatingatestdeployment></a>Creating a Test Deployment</h1>
		20
		21	<p>This topic describes how to create a deployment for your test suite. Unless
		22	you make use of the default deployment to run your test locally, you must
		23	create a deployment before you can run a test.</p>
		24
		25	<p>A test deployment definition typically consists of one or
		26	more pairs of test artifacts and locations. Test artifacts are test suites and
		27	datapools. A location identifies the computer where you run the test suite.
		28	TPTP reads the pairing and deploys the test artifacts on the computer specified.
		29	You can also create a test deployment that specifies only a location; it does
		30	not specify test artifacts. Such a deployment is convenient when you want to
		31	run a specific test suite on a specific computer. In this case, you do not need
		32	to create a test artifact for the test suite. You select the test suite and the
		33	location-only deployment, and TPTP deploys the test suite to the computer
		34	specified in the deployment definition and runs the test suite on that
		35	computer.</p>
		36
		37	<p>To create a test deployment:</p>
		38
		39	<ol>
		40	<li>
		41	<p>In
		42	the Test Navigator select the test suite for which you want to create a
		43	deployment. Select <b>File</b><b> > </b><b>New</b><b> > </b><b>Other</b>. The New
		44	wizard opens.</p>
		45	</li>
		46	<li>
		47	<p>Expand the Test folder and the Test Assets folder, then select Deployment.
		48	Click <b>Next</b>. The next page of the wizard
		49	opens.</p>
		50	<p>Navigate to the folder that will store the deployment file
		51	resource. Enter a name for the deployment in the name
		52	field. Click <b>Next</b>. The next page of the
		53	wizard opens: </p>
		54	</li>
		55	<li>
		56	<p>Optionally enter a brief description for the deployment. Click
		57	<b>Next</b>. The next page of the wizard opens.</p>
		58	</li>
		59	<li>
		60	<p>(To create a deployment that consists of a location only,
		61	click <b>Next</b> and skip ahead to <b>Step 9</b>).
		62	When you run a test with such a deployment, TPTP deploys the test suite to the
		63	location specified in the deployment. Otherwise, click Add
		64	to open the Add Artifact Association page.</p>
		65	</li>
		66	<li>
		67	<p>If you have previously defined one or more artifacts that
		68	you want to use in this deployment, click <b>Browse</b>
		69	and navigate to the artifact. After you select the artifact, click <b>Finish</b>. To define a new artifact check the <b>Create a new resource</b> button and click <b>Next</b>. The New Artifact wizard opens.</p>
		70	</li>
		71	<li>
		72	<p>Navigate to the folder that will store the artifact file
		73	resource. Enter a name for the artifact file resource in the Name field. Click <b>Next</b>.
		74	The next page of the wizard opens.</p>
		75	</li>
		76	<li>
		77	<p>Optionally enter a description for the artifact. Click <b>Next</b>. The next page of the wizard opens.</p>
		78	</li>
		79	<li>
		80	<p>Click the boxes next to the test asset(s) that you want to
		81	include in the artifact. Click <b>Finish</b>. The
82	new artifact appears in the list of artifacts to be added to the deployment.</p>
125	<p>	83	<p>
126	<b class="parentlink">Parent topic:</b> <a href="../concepts/ccommontestingtasksandconcepts.htm" title="The Eclipse test and performance tools platform (TFTP) provides support for three types of testing:">Common testing tasks and concepts</a><br />	84	To add another artifact click Add and repeat the
		85	steps. When you are satisfied with the list of artifacts, click <b>Next</b>. The next page of the wizard appears.</p>
		86	</li>
		87	<li>
		88	<p>Click <b>Add</b> to select a
		89	location to be associated with the deployment. The <b>Add Location Association</b>
		90	dialog box opens, as above.</p>
		91	</li>
		92	<li>
		93	<p>To select an existing location resource click <b>Browse</b> and navigate to the location. To create a
		94	location, check the <b>Create a new resource</b>
		95	button and click <b>Next</b>. The New Location
		96	wizard opens. </p>
		97
		98	<p>Navigate to the folder that will store the location resource
		99	file. Enter a name for the location resource file in the File
		100	name field. Click <b>Next</b>. The next
		101	page of the wizard appears.</p>
		102	</li>
		103	<li>
		104	<p>Optionally
		105	enter a description for the location. Click <b>Finish</b>.
		106	The new location appears in the list of locations to be added to the
		107	deployment.</p>
		108	<p>
		109	To add another location click <b>Add</b> and
		110	repeat the steps. When you are satisfied with the list of locations to be added
		111	to the deployment, click <b>Next</b>. The next
		112	page of the wizard opens.</p>
		113	</li>
		114	<li>
		115
		116	<p>The
		117	left-pane lists test artifacts and the right-pane lists locations. Create one
		118	or more pairs of test artifacts and locations by selecting one from each pane
		119	and clicking the down-arrow. By creating pairs of artifacts and locations you
		120	are specifying which test artifacts should be deployed to which computers when
		121	the test is run. If you are creating a location-only deployment, the test artifacts
		122	pane will be empty. To remove a pair, select it from the list and click Remove. To move a pair up in the list, select the pair
		123	and click Up. When you are satisfied with the list
		124	of pairs, click Finish.</p>
		125	</li>
		126	</ol>
		127
		128	<p><strong>Related tasks</strong><br/>
		129	<a href="trunningmanualtestsuite.htm">Running a manual test</a><br/>
		130	<a href="tediting_manual_test.htm">Editing a manual test</a><br/>
		131	<a href="tanalyzingmanualtestresults.htm">Analyzing manual test results</a><br/>
		132	</p>
		133
		134	<p><strong>Related reference</strong><br/>
		135	<a href="../ref/rtestlog.html">Test Log viewer</a><br/>
127	</p>	136	</p>
128	</div><div class="runningfooter">(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.</div>	137
		138	<p>(C) Copyright IBM Corporation 2000, 2005. All Rights
		139	Reserved.</p>
		140
		141
		142	</div>
		143
129	</body>	144	</body>
		145
130	</html>	146	</html>

Lines 1-60 Link Here

(-)tasks/tcreatingamanualtest.htm (-50 / +32 lines)
1	<?xml version="1.0" encoding="UTF-8"?>	1	<?xml version="1.0" encoding="ISO-8859-1"?>
2	<!DOCTYPE html	2
3	PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">	3	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
4	<html>	4	<html>
		5
5	<head>	6	<head>
6	<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />	7	<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
7	<meta name="copyright" content="(C) Copyright IBM Corporation 2004" />	8	<link rel=StyleSheet href="../css/book.css" type="text/css"/>
8	<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2004" />	9
9	<meta name="security" content="public" />
10	<meta name="Robots" content="index,follow" />
11	<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
12	<meta name="DC.Type" content="task" />
13	<meta name="DC.Title" content="Creating a manual test" />
14	<meta name="abstract" content="This section describes the procedure for creating a manual test suite." />
15	<meta name="description" content="This section describes the procedure for creating a manual test suite." />
16	<meta name="DC.Relation" scheme="URI" content="../concepts/cmanualtestoverview.dita" />
17	<meta name="DC.Format" content="XHTML" />
18	<meta name="DC.Identifier" content="creating_manual_test" />
19	<meta name="DC.Language" content="en-us" />
20	<!-- All rights reserved. Licensed Materials Property of IBM -->
21	<!-- US Government Users Restricted Rights -->
22	<!-- Use, duplication or disclosure restricted by -->
23	<!-- GSA ADP Schedule Contract with IBM Corp. -->
24	<link rel="stylesheet" type="text/css" href="../css/ibmdita.css" />
25	<link rel="stylesheet" type="text/css" href="../css/swg_info_common.css" />
26	<title>Creating a manual test</title>	10	<title>Creating a manual test</title>
		11
27	</head>	12	</head>
28	<body id="creating_manual_test"><a name="creating_manual_test"><!-- --></a>
29		13
30	<h1 class="topictitle1">Creating a manual test</h1>	14	<body>
31	<div><p>This section describes the procedure for creating a manual test
32	suite.</p>
33	<ol><li><span>Click <span class="menucascade"><span class="uicontrol">File</span> > <span class="uicontrol">New</span> > <span class="uicontrol">Other</span></span></span></li>
34	<li><span>In the <span class="uicontrol">New</span> dialog box, shown below, expand
35	the <span class="uicontrol">Test</span> folder, expand the <span class="uicontrol">Test Suite</span> folder,
36	select <span class="uicontrol">Test Suite</span>, and click <span class="uicontrol">Next</span>. <br /><img src="../images/newmanualtest.gif" /><br /></span></li>
37	<li><span>The <span class="uicontrol">New Test Suite</span> wizard appears, as shown
38	below. <br /><img src="../images/newmanualtest2.gif" /><br />Navigate
39	to the folder that will contain the test suite. Enter a name for the file
40	resource that will store the test suite in the <span class="uicontrol">File name</span> field.
41	Click <span class="uicontrol">Next</span>. The next page of the wizard appears, as
42	shown below. <br /><img src="../images/newmanualtest3.gif" /><br /></span></li>
43	<li><span>Specify the name of the test suite definition and enter a description
44	of the test suite. By default, the name of the test suite definition is the
45	same name that you specified for the file resource without the <kbd class="userinput">.testsuite</kbd> suffix.
46	The name that you specify here is the name that appears in the Test Navigator.
47	Click <span class="uicontrol">Finish</span> to close the wizard. The <span class="uicontrol">Test
48	Suite</span> dialog box opens and you can now edit the definition by
49	adding test methods and specifying behaviors that control how the methods
50	should be run.</span></li>
51	</ol>
52	</div>
53		15
54	<div>	16	<div>
		17
		18	<h2>Creating a manual test</h2>
55	<p>	19	<p>
56	<b class="parentlink">Parent topic:</b> <a href="../concepts/cmanualtestoverview.htm" title="">Manual testing with TPTP</a><br />	20	This topic describes how to create a manual test suite.
		21	</p>
		22
		23	<ol>
		24	<li>Click <b>File > New > Other</b>. The <b>New</b> dialog appears.</li>
		25	<li>Expand the <b>Test</b> folder, then select <b>TPTP Manual Test</b>.</li>
		26	<li>Click <b>Next</b> and name the the manual test, for example, <em id="CodeName">exampleManualTest</em>.</li>
		27	<li>Click <b>Next</b> and optionally provide a description for the manual test suite. Click <b>Finish</b>.</li>
		28	<li>A manual test testsuite file (<em id="CodeName">exampleManualTest.testsuite</em>) will be created and becomes visible in the Navigator.</li>
		29	</ol>
		30
		31	<p><strong>Related tasks</strong><br />
		32	<a href="tediting_manual_test.htm">Editing a manual test</a><br/>
		33	<a href="trunningmanualtestsuite.htm">Running a manual test</a><br />
57	</p>	34	</p>
58	</div><div class="runningfooter">(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.</div>	35
		36	<p>(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.</p>
		37
		38	</div>
		39
59	</body>	40	</body>
60	</html>	41
		42	</html>

Lines 5-19 Link Here

(-)tasks/tediting_manual_test.htm (-44 / +66 lines)
5	<head>	5	<head>
6	<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />	6	<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
7	<meta name="copyright" content="(C) Copyright IBM Corporation 2004" />	7	<meta name="copyright" content="(C) Copyright IBM Corporation 2004" />
8	<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2004" />	8	<meta name="DC.rights.owner"
		9	content="(C) Copyright IBM Corporation 2004" />
9	<meta name="security" content="public" />	10	<meta name="security" content="public" />
10	<meta name="Robots" content="index,follow" />	11	<meta name="Robots" content="index,follow" />
11	<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />	12	<meta http-equiv="PICS-Label"
		13	content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
12	<meta name="DC.Type" content="task" />	14	<meta name="DC.Type" content="task" />
13	<meta name="DC.Title" content="Editing a manual test" />	15	<meta name="DC.Title" content="Editing a manual test" />
14	<meta name="abstract" content="This section describes how to edit your manual test suite." />	16	<meta name="abstract"
15	<meta name="description" content="This section describes how to edit your manual test suite." />	17	content="This section describes how to edit your manual test suite." />
16	<meta name="DC.Relation" scheme="URI" content="../concepts/cmanualtestoverview.dita" />	18	<meta name="description"
		19	content="This section describes how to edit your manual test suite." />
		20	<meta name="DC.Relation" scheme="URI"
		21	content="../concepts/cmanualtestoverview.dita" />
17	<meta name="DC.Format" content="XHTML" />	22	<meta name="DC.Format" content="XHTML" />
18	<meta name="DC.Identifier" content="editing_manual_test" />	23	<meta name="DC.Identifier" content="editing_manual_test" />
19	<meta name="DC.Language" content="en-us" />	24	<meta name="DC.Language" content="en-us" />
Lines 25-74 Link Here
25	<link rel="stylesheet" type="text/css" href="../css/swg_info_common.css" />	30	<link rel="stylesheet" type="text/css" href="../css/swg_info_common.css" />
26	<title>Editing a manual test</title>	31	<title>Editing a manual test</title>
27	</head>	32	</head>
28	<body id="editing_manual_test"><a name="editing_manual_test"><!-- --></a>	33	<body id="editing_manual_test">
		34	<a name="editing_manual_test"><!-- --></a>
29		35
30	<h1 class="topictitle1">Editing a manual test</h1>	36	<h1 class="topictitle1">Editing a manual test</h1>
31	<div><p>This section describes how to edit your manual test suite.</p>	37	<div>
		38	<p>This section describes how to edit your manual test suite.</p>
32	<div class="p">You must have created a manual test suite.</div>	39	<div class="p">You must have created a manual test suite.</div>
33	<ol><li><span>In the <span class="uicontrol">Navigator</span> double-click the test suite	40	<ol>
34	entry to open the <span class="uicontrol">Test Suite </span> dialog box as shown below.	41	<li><span>In the <span class="uicontrol">Test Navigator</span>
35	The test suite opens in the <span class="uicontrol">Overview</span> tab with the two	42	double-click the test suite entry to open the <span class="uicontrol">Test
36	edit areas (<span class="uicontrol">General Information</span> and <span class="uicontrol">Test	43	Suite </span> dialog box. The test suite opens in the <span
37	Cases</span>) expanded. <br /><img src="../images/manualtestsuite.gif" /><br /></span></li>	44	class="uicontrol">Overview</span> tab with the two edit areas (<span
38	<li><span>The <span class="uicontrol">General Information</span> area displays the	45	class="uicontrol">General Information</span> and <span
39	test suite's name, an optional description, test type, and name of the file	46	class="uicontrol">Test Cases</span>) expanded.</span></li>
40	containing the test suite. You can edit information appearing in boxes.</span></li>	47	<li><span>The <span class="uicontrol">General Information</span> area
41	<li><span>The <span class="uicontrol">Test Cases</span> area lists the individual	48	displays the test suite's name, an optional description, test type, and
42	tests that make up the test suite. Click one of the test cases or <span class="uicontrol">More</span> to	49	name of the file containing the test suite. You can edit information
43	display the Test Cases view, as shown below. <br /><img src="../images/manualtestcases.gif" /><br />To change the name or description of a test case, select	50	appearing in boxes.</span></li>
44	the test case and enter new text in the <span class="uicontrol">Name</span> or <span class="uicontrol">Description</span> boxes.	51	<li>The <span class="uicontrol">Test Cases</span> area lists the
45	Use the <span class="uicontrol">Add</span> and <span class="uicontrol">Remove</span> buttons	52	individual tests that make up the test suite. Click one of the test
46	to add test cases and to remove existing cases. Use the <span class="uicontrol">Up</span> and <span class="uicontrol">Down</span> buttons	53	cases or <span class="uicontrol">More</span> to display the Test Cases
47	to change the order of cases.</span></li>	54	view. To change the name or description of a test case, select the test
48	<li><span>Click the <span class="uicontrol">Behaviors</span> tab to display the Behaviors	55	case and enter new text in the <span class="uicontrol">Name</span> or <span
49	view, as shown below. <br /><img src="../images/manualbehaviors.gif" /><br />Behaviors	56	class="uicontrol">Description</span> boxes. Use the <span
50	let you control the order in which test cases are run; you do this by specifying	57	class="uicontrol">Add</span> and <span class="uicontrol">Remove</span>
51	invocations and loops. For example, in the figure shown above, <kbd class="userinput">test	58	buttons to add test cases and to remove existing cases. Use the <span
52	1</kbd> runs inside <kbd class="userinput">Loop 1</kbd>. Use the <span class="uicontrol">Number	59	class="uicontrol">Up</span> and <span class="uicontrol">Down</span>
53	of Iterations</span> box to specify how many times to execute the loop.	60	buttons to change the order of cases.</li>
54	With <span class="uicontrol">Synchronous</span> checked and more than one iteration	61	<li><span>Click the <span class="uicontrol">Behaviors</span> tab to
55	specified, the loop iterations execute in sequence. With <span class="uicontrol">Synchronous</span> unchecked	62	display the Behaviors view. Behaviors let you control the order in
56	and more than one iteration specified, the loop iterations execute simultaneously. </span></li>	63	which test cases are run; you do this by specifying invocations and
57	<li><span>Use the <span class="uicontrol">Up</span> and <span class="uicontrol">Down</span> buttons	64	loops. For example, in the figure shown below, <kbd class="userinput">test
58	to change the order of invocations and loops. Use the <span class="uicontrol">Add</span> and <span class="uicontrol">Remove</span> buttons	65	1</kbd> runs inside <kbd class="userinput">Loop 1</kbd>.<img
59	to add and remove loops and invocations. After you create a loop you can add	66	src="../images/manualbehaviors.gif" />
60	an invocation to it by right-clicking the loop and selecting <span class="menucascade"><span class="uicontrol">Add</span> > <span class="uicontrol">Invocation</span></span>.	67	<br/>Use the <span
61	The <span class="uicontrol">Test Invocation</span> dialog box, shown below, appears. <br /><img src="../images/addinvocationmanual.gif" /><br />The top pane lists	68	class="uicontrol">Number of Iterations</span> box to specify how many
62	test cases in the test suite. The bottom pane lets you navigate to test cases	69	times to execute the loop. With <span class="uicontrol">Synchronous</span>
63	in other test suites in your workspace. You can nest loops and create invocations	70	checked and more than one iteration specified, the loop iterations
64	that are outside of any loop.</span></li>	71	execute in sequence. With <span class="uicontrol">Synchronous</span>
		72	unchecked and more than one iteration specified, the loop iterations
		73	execute simultaneously. </span></li>
		74	<li><span>Use the <span class="uicontrol">Up</span> and <span
		75	class="uicontrol">Down</span> buttons to change the order of
		76	invocations and loops. Use the <span class="uicontrol">Add</span> and <span
		77	class="uicontrol">Remove</span> buttons to add and remove loops and
		78	invocations. After you create a loop you can add an invocation to it by
		79	right-clicking the loop and selecting <span class="menucascade"><span
		80	class="uicontrol">Add</span> > <span class="uicontrol">Invocation</span></span>.
		81	The <span class="uicontrol">Test Invocation</span> dialog box appears.
		82	The top pane lists test cases in the test suite. The bottom pane lets
		83	you navigate to test cases in other test suites in your workspace. You
		84	can nest loops and create invocations that are outside of any loop.</span></li>
65	</ol>	85	</ol>
66	</div>	86	</div>
67		87
68	<div>	88	<p><strong>Related tasks</strong><br />
69	<p>	89	<a href="tcreatingamanualtest.htm">Creating a manual test</a><br />
70	<b class="parentlink">Parent topic:</b> <a href="../concepts/cmanualtestoverview.htm" title="">Manual testing with TPTP</a><br />	90	<a href="trunningmanualtestsuite.htm">Running a manual test</a><br />
71	</p>	91	</p>
72	</div><div class="runningfooter">(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.</div>	92
		93	<div class="runningfooter">(C) Copyright IBM Corporation 2000, 2004. All
		94	Rights Reserved.</div>
73	</body>	95	</body>
74	</html>	96	</html>

Lines 1-103 Link Here

(-)tasks/trunningmanualtestsuite.htm (-94 / +23 lines)
1	<?xml version="1.0" encoding="UTF-8"?>	1	<?xml version="1.0" encoding="ISO-8859-1"?>
2	<!DOCTYPE html	2
3	PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">	3	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
4	<html>	4	<html>
		5
5	<head>	6	<head>
6	<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />	7	<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
7	<meta name="copyright" content="(C) Copyright IBM Corporation 2004" />	8	<link rel=StyleSheet href="../css/book.css" type="text/css"/>
8	<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2004" />
9	<meta name="security" content="public" />
10	<meta name="Robots" content="index,follow" />
11	<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
12	<meta name="DC.Type" content="task" />
13	<meta name="DC.Title" content="Running a manual test" />
14	<meta name="abstract" content="This topic describes how to create and run a manual test." />
15	<meta name="description" content="This topic describes how to create and run a manual test." />
16	<meta name="DC.Relation" scheme="URI" content="../concepts/cmanualtestoverview.dita" />
17	<meta name="DC.Format" content="XHTML" />
18	<meta name="DC.Identifier" content="runningamanualtestsuite" />
19	<meta name="DC.Language" content="en-us" />
20	<!-- All rights reserved. Licensed Materials Property of IBM -->
21	<!-- US Government Users Restricted Rights -->
22	<!-- Use, duplication or disclosure restricted by -->
23	<!-- GSA ADP Schedule Contract with IBM Corp. -->
24	<link rel="stylesheet" type="text/css" href="../css/ibmdita.css" />
25	<link rel="stylesheet" type="text/css" href="../css/swg_info_common.css" />
26	<title>Running a manual test</title>	9	<title>Running a manual test</title>
27	</head>	10	</head>
28	<body id="runningamanualtestsuite"><a name="runningamanualtestsuite"><!-- --></a>
29		11
30	<h1 class="topictitle1">Running a manual test</h1>	12	<body>
31	<div><p>This topic describes how to create and run a manual test.</p>	13
32	<div class="p">Before you can run a test, you must <a href="tcreating_test_deployment.htm#creatingatestdeployment">create a test deployment</a>. </div>	14	<div>
33	<div class="skipspace">To run a manual test:</div>	15
34	<ol><li class="skipspace"><span>From the Test Navigator click <span class="menucascade"><span class="uicontrol">Run</span> > <span class="uicontrol">Run</span></span>. The Run dialog box opens. </span></li>	16	<h2>Running a manual test</h2>
35	<li class="skipspace"><span>In the <span class="uicontrol">Configurations</span> pane on the left,	17	<p>This topic describes how to create and run a manual test.</p>
36	click <span class="uicontrol">Hyades Manual Test</span>. <br /><img src="../images/perspectiveMan.gif" alt=" " /><br /></span></li>	18	<ol>
37	<li class="skipspace"><span>Optionally, in the Perspectives tab, you can associate the Run	19	<li><a href="tprereqmanualtestconfiguration.htm">Preparing to run a manual test</a></li>
38	launch mode with a different workbench perspective by clicking the appropriate	20	<li><a href="tcreatemanualtestconfiguration.htm">Creating a test configuration</a></li>
39	arrow and selecting the perspective from the drop-down list.</span></li>	21	<li><a href="trunmanualtest.htm">Running the test configuration</a></li>
40	<li class="skipspace"><span>To create a new configuration, click the <span class="uicontrol">New</span> button
41	on the bottom left. </span> <p>A new test configuration, initially
42	named <kbd class="userinput">New_Configuration</kbd>, is created. Change the name
43	if you like. Alternatively, expand <span class="uicontrol">Hyades Manual Test</span> and
44	click a listed configuration that you want to inspect or modify. The Run dialog
45	box opens in the Test tab.<br /><img src="../images/manualDeploy.gif" alt=" " /><br /></p>
46	</li>
47	<li class="skipspace"><span>In the <span class="uicontrol">Select Test to run</span> pane in the middle
48	listing all projects in the workspace, navigate to the project containing
49	the test to run and click it.</span></li>
50	<li class="skipspace"><span>In the <span class="uicontrol">Select a deployment</span> pane on the right
51	listing all defined deployments in the workspace, click the one to use for
52	this run.</span> <p>To run the test using default values, or using the
53	same values that you set during the previous test run, you can click <span class="uicontrol">Run</span> now
54	and stop reading.</p>
55	</li>
56	<li class="skipspace"><span>Click <span class="uicontrol">Apply</span> to save the selections on this
57	tab.</span></li>
58	<li class="skipspace"><span>Click <span class="uicontrol">Execution Results</span> to display that
59	tab, as shown below. <br /><img src="../images/manualconfig2.gif" /><br /> </span></li>
60	<li class="skipspace"><span>To overwrite the test results file that was used the last time
61	this test was run, rather than creating a new results file, check the box
62	beside <span class="uicontrol">Override existing Execution Results resource</span>.</span></li>
63	<li class="skipspace"><span>In the <span class="uicontrol">Location</span> box listing Java projects
64	in the workspace, click the one in which to store the test results.</span></li>
65	<li class="skipspace"><span>Click <span class="uicontrol">Apply</span> to save the selections on this
66	tab.</span></li>
67	<li class="skipspace"><span>Click <span class="uicontrol">Common</span> to display the <span class="uicontrol">Common</span> tab,
68	as shown below. <br /><img src="../images/manualconfig3.gif" /><br /></span></li>
69	<li class="skipspace"><span>When you run a test configuration, Eclipse creates a file, with
70	a <kbd class="userinput">.launch</kbd> suffix, containing metadata. If you select <span class="uicontrol">Local</span>,
71	Eclipse stores this file in your workspace's metadata folder, which is not
72	visible to other users. If you want other users to have access to the file,
73	select <span class="uicontrol">Shared</span>, click <span class="uicontrol">Browse</span>,
74	and navigate to a folder in your workspace where you want to store the file. </span></li>
75	<li class="skipspace"><span>To have the test configuration appear in the <span class="uicontrol">Run</span> favorites
76	toolbar menu, check this item in the <span class="uicontrol">Display in favorites menu
77	box</span>.</span></li>
78	<li class="skipspace"><span>Select <span class="uicontrol">Launch in background</span> to have Eclipse
79	run the test configuration in the background so that you can perform other
80	Eclipse tasks while the test runs. </span></li>
81	<li class="skipspace"><span>Click <span class="uicontrol">Apply</span> to save the settings for the
82	configuration. </span></li>
83	<li class="skipspace"><span>Click <span class="uicontrol">Run</span>. The Manual Remote Application
84	dialog box opens, as shown below. <br /><img src="../images/manualtestremote.gif" /><br /></span></li>
85	<li class="skipspace"><span>Navigate to a test in the left pane. The name and description of
86	the test appears in the right pane. After you perform the steps specified
87	in the test's description, indicate whether the test passed, failed, returned
88	an error, or was inconclusive by selecting a value in the <span class="uicontrol">Status</span> drop-down
89	list. Enter comments about the test results in the <span class="uicontrol">Info</span> field. </span></li>
90	<li class="skipspace"><span>Click <span class="uicontrol">Next</span> to save the test results and
91	move to the next test.</span></li>
92	<li class="skipspace"><span>When you finish running all tests, click <span class="uicontrol">End Execution</span> to
93	close the dialog box.</span></li>
94	</ol>	22	</ol>
		23
		24
		25
		26	<p>(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.</p>
		27
95	</div>	28	</div>
96		29
97	<div>
98	<p>
99	<b class="parentlink">Parent topic:</b> <a href="../concepts/cmanualtestoverview.htm" title="">Manual testing with TPTP</a><br />
100	</p>
101	</div><div class="runningfooter">(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.</div>
102	</body>	30	</body>
103	</html>	31
		32	</html>

Removed Link Here

(-)tdeploy/tcreating_test_deployment_css.htm (-23 lines)
1	<?xml version="1.0" encoding="UTF-8"?>
2
3	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
4	<html xmlns:v="urn:schemas-microsoft-com:vml"
5	xmlns:o="urn:schemas-microsoft-com:office:office"
6	xmlns:w="urn:schemas-microsoft-com:office:word"
7	xmlns="http://www.w3.org/TR/REC-html40">
8
9	<head>
10	<meta http-equiv=Content-Type content="text/html; charset=UTF-8"/>
11	<link rel=StyleSheet href="../css/book.css" type="text/css"/>
12
13	<!--[if !mso]>
14	<style>
15	v\:* {behavior:url(#default#VML);}
16	o\:* {behavior:url(#default#VML);}
17	w\:* {behavior:url(#default#VML);}
18	.shape {behavior:url(#default#VML);}
19	</style>
20	<![endif]-->
21	<title>Creating a test deployment</title>
22	<style>
23	<!--

Added Link Here

(-)ref/refintro.html (+29 lines)
1	<?xml version="1.0" encoding="ISO-8859-1"?>
2
3	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
4	<html>
5
6	<head>
7	<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
8	<link rel=StyleSheet href="../css/book.css" type="text/css"/>
9	<title>Reference</title>
10	</head>
11
12	<body>
13	<div>
14	<h2>Reference</h2>
15	This section explains some of the subjects introduced in the
16	<i>TPTP Tester guide</i> in detail.
17
18	<ul>
19	<li><a href="rmanualcreate.htm">Generic launch configuration properties</a></li>
20	<li><a href="rtestlog.html">Test Log viewer</a></li>
21	</ul>
22
23	<p>(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.</p>
24
25	</div>
26
27	</body>
28
29	</html>

Added Link Here

(-)ref/rmanualcreate.htm (+53 lines)
1	<?xml version="1.0" encoding="ISO-8859-1"?>
2
3	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
4	<html>
5
6	<head>
7	<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
8	<link rel=StyleSheet href="../css/book.css" type="text/css"/>
9	<title>Generic launch configuration properties</title>
10	</head>
11
12	<body>
13
14	<div>
15	<h2>Generic launch configuration properties</h2>
16	<p>Eclipse provides the <b>Common</b> tab at the right of the <b>Run</b> dialog for editing various generic launch configuration properties. Select the <b>Common</b>
17	tab at the right of the <b>Run</b> dialog to edit the following generic launch configuration properties:</p>
18
19	<ul>
20	<li>When the launch configuration is saved by clicking <b>Run</b> at the bottom of the <b>Run</b> dialog, a
21	launch configuration file (<i>.launch</i>) is created and saved. By default, the launch configuration file is saved in the workspace's <i>.metadata</i>
22	directory. The location for the .launch file may be changed to any directory in the workspace via the <b>Save as</b> pane of the <b>Common</b> tab.</li>
23	<li>When rerunning a launch configuration, a shortcut may be associated with one or more favorites tool bar menus in the <b>Display in favorites menu</b>
24	pane of the <b>Common</b> tab.</li>
25	<li>When a launch configuration is executed by clicking <b>Run</b> at the bottom of the <b>Run</b> dialog, the <b>Console</b> view
26	is used for rendering standard output data and reading standard input data. By default, the encoding of the <b>Console</b> view is the encoding for the
27	local platform. The encoding of the <b>Console</b> view may be changed to any valid encoding in the <b>Console Encoding</b> pane of the <b>Common</b> tab.</li>
28	<li>When a launch configuration is executed, the standard output and standard input might display output data and read input data, respectively. By default, the <b>Console</b> view is used for both the standard output and standard input.
29	The standard input may be disabled and the standard output may be changed to write or append to a local file in the <b>Standard Input and Output</b> pane of the
30	<b>Common</b> tab.</li>
31	<li>When a launch configuration is executed, by default Eclipse will run the launch configuration
32	in the background so that the user may continue interacting with Eclipse. To restrict the user from interacting with Eclipse until the execution has terminated, clear the <b>Launch
33	in background</b> check box at the bottom of the <b>Common</b> tab. .</li>
34	</ul>
35
36	<br/>
37
38
39	<p><strong>Related concepts</strong><br/>
40	<a href="../tasks/trunningmanualtestsuite.htm">Running a manual test</a><br/>
41	</p>
42
43	<p><strong>Related tasks</strong><br/>
44	<a href="../tasks/tcreating_test_deployment.htm">Creating a test deployment</a><br/>
45	</p>
46
47	<p>(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.</p>
48
49	</div>
50
51	</body>
52
53	</html>

Added Link Here

(-)tasks/tcreatemanualtestconfiguration.htm (+75 lines)
1	<?xml version="1.0" encoding="ISO-8859-1"?>
2
3	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
4	<html>
5
6	<head>
7	<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
8	<link rel=StyleSheet href="../css/book.css" type="text/css"/>
9	<title>Creating a test launch configuration</title>
10	</head>
11
12	<body>
13
14	<div>
15	<h2>Creating a test configuration</h2>
16	<p>A new test configuration is required to run a manual test.
17	When the test configuration is executed, a test log captures the
18	launch of the manual test.</p>
19
20	<p>Open the <b>Run</b> dialog to create the test configuration.
21	Right-click on a test suite file in the Test Navigator and select
22	<b>Run As</b> > <b>Run</b> from the pop-up menu.
23	The <b>Run</b> dialog opens.</p>
24
25	<p>Create the test configuration by selecting the <b>Test</b> entry from the list
26	of launch <b>Configurations</b> and clicking <b>New</b>. The test configuration is created and
27	by default is named New_configuration. You may edit the default name of the test configuration in the
28	<b>Name</b> field at the top of the <b>Run</b> dialog.</p>
29
30	<p>The test configuration requires an association to the manual test and its
31	deployment. Select the manual test
32	and its deployment for the test configuration. Select the <b>Test</b> tab at the right of the <b>Run</b> dialog
33	and complete the following steps:</p>
34
35	<ol>
36	<li>Select the manual test to run. Navigate to and select the manual test in the <b>1. Select test to run</b> pane of the <b>Test</b> tab.
37	</li>
38	<li>Select the deployment for running the manual test. Select the <i>local_deployment</i> deployment in the <b>2.
39	Select a deployment</b> pane of the <b>Test</b> tab.</li>
40	<li>
41	<p>Optionally, you may override the default settings
42	for the generated test log. By default, the test log's name is the same as the manual test and it is saved in the same location
43	as the manual test. Select the <b>Test Logs</b> tab at the
44	right of the <b>Run</b> dialog and complete the following steps:</p>
45
46	<ul>
47	<li>Clear the <b>Use defaults</b> check box at the top of the <b>Test Logs</b> tab.</li>
48	<li>Edit the default name of the generated test log in the <b>Name</b> field under the <b>Use defaults</b> check box.</li>
49	<li>Select the <b>Override existing test logs resource</b> check box under the <b>Name</b> field to override an existing test log with the same name in the same location.
50	If the check box is cleared, the generated test log will be uniquely named.</li>
51	<li>Edit the default location of the generated test log in the <b>Location</b> pane at the bottom of the <b>Test Logs</b> tab.</li>
52	</ul>
53	</li>
54	<li>Optionally edit the generic launch configuration properties</li>
55	<li>Save the test configuration by clicking the <b>Apply</b> button at the bottom of the <b>Run</b> dialog.</li>
56	</ol>
57
58	<p></p>
59
60	<p><strong>Related tasks</strong><br/>
61	<a href="trunningmanualtestsuite.htm">Running a manual test</a><br/>
62	<a href="tcreating_test_deployment.htm">Creating a test deployment</a><br/>
63	</p>
64
65	<p><strong>Related reference</strong><br/>
66	<a href="../ref/rmanualcreate.htm">Generic launch configuration properties</a><br/>
67	</p>
68
69	<p>(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.</p>
70
71	</div>
72
73	</body>
74
75	</html>

Added Link Here

(-)tasks/tprereqmanualtestconfiguration.htm (+46 lines)
1	<?xml version="1.0" encoding="ISO-8859-1"?>
2
3	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
4	<html>
5
6	<head>
7	<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
8	<link rel=StyleSheet href="../css/book.css" type="text/css"/>
9	<title>Preparing to run a manual test</title>
10	</head>
11
12	<body>
13
14	<div>
15
16	<h2>Preparing to run a manual test</h2>
17
18	<br/>
19
20	<p>To prepare to run a manual test, complete the following steps:</p>
21
22	<ol>
23	<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>
24	<li>Launch the Agent Controller.</li>
25	<li>Optionally create a test deployment.</li>
26	</ol>
27
28	<br/>
29
30	<p><strong>Related concepts</strong><br/>
31	<a href="../concepts/cmanualtestoverview.htm">Manual testing with TPTP - overview</a><br/>
32	</p>
33
34	<p><strong>Related tasks</strong><br/>
35	<a href="trunningmanualtestsuite.htm">Running a manual test</a><br/>
36	<a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/tasks/tworkwac.html">Working with the Agent Controller</a><br/>
37	<a href="tcreating_test_deployment.htm">Creating a test deployment</a><br/>
38	</p>
39
40	<p>(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.</p>
41
42	</div>
43
44	</body>
45
46	</html>