Attachment 27655 Details for Bug 110436 – Updated doc based on Paul's doc and including many fixes for existing doc

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

[patch] Updated doc based on Paul's doc and including many fixes for existing doc

test_doc_patch.txt (text/plain), 151.10 KB, created by Ruth Lee

on 2005-09-28 18:32:27 EDT

(hide)

Description:

Filename:

MIME Type:

Creator: Ruth Lee

Created: 2005-09-28 18:32:27 EDT

Size: 151.10 KB

patch

obsolete

>Index: comptest_toc.xml
>===================================================================
>RCS file: /home/tptp/test/org.eclipse.hyades.test.doc.user/comptest_toc.xml,v
>retrieving revision 1.4
>diff -u -r1.4 comptest_toc.xml
>--- comptest_toc.xml	26 Sep 2005 18:44:31 -0000	1.4
>+++ comptest_toc.xml	28 Sep 2005 22:23:08 -0000
>@@ -45,14 +45,18 @@
> <topic label="Reports on JUnit tests" href="junit/tptpJUnitTest_analysisReport.htm"/>
> <anchor id="test_junit"/>
> </topic>
>- <topic label="Manual testing with TPTP" href="mtest/tptpManualTest_intro.htm">
>- <topic label="Building a manual test" href="mtest/tptpManualTest_building.htm"/>
>- <topic label="Editing a manual test" href="mtest/tptpManualTest_editor.htm"/>
>- <topic label="Running a manual test" href="mtest/tptpManualTest_run.htm"/>
>- <topic label="Analyzing manual test results" href="mtest/tptpManualTest_analysis.htm"/>
>- <topic label="Example manual test deployment" href="mtest/tptpManualTestDeployExample.htm"/>
>+ <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"/>
>- <anchor id="reference"/>
>+ <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>
>\ No newline at end of file
>Index: concepts/cmanualtestoverview.htm
>===================================================================
>RCS file: /home/tptp/test/org.eclipse.hyades.test.doc.user/concepts/cmanualtestoverview.htm,v
>retrieving revision 1.2
>diff -u -r1.2 cmanualtestoverview.htm
>--- concepts/cmanualtestoverview.htm	19 Sep 2005 14:34:43 -0000	1.2
>+++ concepts/cmanualtestoverview.htm	28 Sep 2005 22:23:08 -0000
>@@ -10,7 +10,7 @@
> <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" />
>+<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" />
>@@ -24,11 +24,11 @@
> 
> <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</title>
>+<title>Manual testing with TPTP - overview</title>
> </head>
> <body id="manualtestoverview"><a name="manualtestoverview"></a>
> 
>-<h1 class="topictitle1">Manual testing with TPTP</h1>
>+<h1 class="topictitle1">Manual testing with TPTP - overview</h1>
> <div>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.
>Index: images/addartifact.gif
>===================================================================
>RCS file: images/addartifact.gif
>diff -N images/addartifact.gif
>Binary files /tmp/cvs.M0Moac and /dev/null differ
>Index: images/addinvocationmanual.gif
>===================================================================
>RCS file: images/addinvocationmanual.gif
>diff -N images/addinvocationmanual.gif
>Binary files /tmp/cvs.36DJ6R and /dev/null differ
>Index: images/addlocation.gif
>===================================================================
>RCS file: images/addlocation.gif
>diff -N images/addlocation.gif
>Binary files /tmp/cvs.EpHm3x and /dev/null differ
>Index: images/addlocation2.gif
>===================================================================
>RCS file: images/addlocation2.gif
>diff -N images/addlocation2.gif
>Binary files /tmp/cvs.3wQh0d and /dev/null differ
>Index: images/addlocation3.gif
>===================================================================
>RCS file: images/addlocation3.gif
>diff -N images/addlocation3.gif
>Binary files /tmp/cvs.DUnqXT and /dev/null differ
>Index: images/addlocation4.gif
>===================================================================
>RCS file: images/addlocation4.gif
>diff -N images/addlocation4.gif
>Binary files /tmp/cvs.sGALUz and /dev/null differ
>Index: images/arrow.gif
>===================================================================
>RCS file: images/arrow.gif
>diff -N images/arrow.gif
>Binary files /tmp/cvs.mipvSf and /dev/null differ
>Index: images/config.gif
>===================================================================
>RCS file: images/config.gif
>diff -N images/config.gif
>Binary files /tmp/cvs.NDFGQV and /dev/null differ
>Index: images/dpedit1.gif
>===================================================================
>RCS file: images/dpedit1.gif
>diff -N images/dpedit1.gif
>Binary files /tmp/cvs.gxXCPB and /dev/null differ
>Index: images/ieSecurityAlert.gif
>===================================================================
>RCS file: images/ieSecurityAlert.gif
>diff -N images/ieSecurityAlert.gif
>Binary files /tmp/cvs.yJvpQh and /dev/null differ
>Index: images/manualDeploy.gif
>===================================================================
>RCS file: images/manualDeploy.gif
>diff -N images/manualDeploy.gif
>Binary files /tmp/cvs.GS4xSX and /dev/null differ
>Index: images/manualconfig.gif
>===================================================================
>RCS file: images/manualconfig.gif
>diff -N images/manualconfig.gif
>Binary files /tmp/cvs.ZVD2UD and /dev/null differ
>Index: images/manualconfig2.gif
>===================================================================
>RCS file: images/manualconfig2.gif
>diff -N images/manualconfig2.gif
>Binary files /tmp/cvs.RxhLXj and /dev/null differ
>Index: images/manualconfig3.gif
>===================================================================
>RCS file: images/manualconfig3.gif
>diff -N images/manualconfig3.gif
>Binary files /tmp/cvs.RnaK0Z and /dev/null differ
>Index: images/manualtestcases.gif
>===================================================================
>RCS file: images/manualtestcases.gif
>diff -N images/manualtestcases.gif
>Binary files /tmp/cvs.vCj03F and /dev/null differ
>Index: images/manualtestremote.gif
>===================================================================
>RCS file: images/manualtestremote.gif
>diff -N images/manualtestremote.gif
>Binary files /tmp/cvs.HroE7l and /dev/null differ
>Index: images/manualtestresults.gif
>===================================================================
>RCS file: images/manualtestresults.gif
>diff -N images/manualtestresults.gif
>Binary files /tmp/cvs.W6bwb2 and /dev/null differ
>Index: images/manualtestresults2.gif
>===================================================================
>RCS file: images/manualtestresults2.gif
>diff -N images/manualtestresults2.gif
>Binary files /tmp/cvs.HJjCfI and /dev/null differ
>Index: images/manualtestresults3.gif
>===================================================================
>RCS file: images/manualtestresults3.gif
>diff -N images/manualtestresults3.gif
>Binary files /tmp/cvs.ZQHWjo and /dev/null differ
>Index: images/manualtestsuite.gif
>===================================================================
>RCS file: images/manualtestsuite.gif
>diff -N images/manualtestsuite.gif
>Binary files /tmp/cvs.S0kwo4 and /dev/null differ
>Index: images/modPerspective.gif
>===================================================================
>RCS file: images/modPerspective.gif
>diff -N images/modPerspective.gif
>Binary files /tmp/cvs.NHcmtK and /dev/null differ
>Index: images/nameTestFile.gif
>===================================================================
>RCS file: images/nameTestFile.gif
>diff -N images/nameTestFile.gif
>Binary files /tmp/cvs.4AQxyq and /dev/null differ
>Index: images/newartifact.gif
>===================================================================
>RCS file: images/newartifact.gif
>diff -N images/newartifact.gif
>Binary files /tmp/cvs.yzy5D6 and /dev/null differ
>Index: images/newartifact2.gif
>===================================================================
>RCS file: images/newartifact2.gif
>diff -N images/newartifact2.gif
>Binary files /tmp/cvs.HbkSJM and /dev/null differ
>Index: images/newartifact3.gif
>===================================================================
>RCS file: images/newartifact3.gif
>diff -N images/newartifact3.gif
>Binary files /tmp/cvs.dvGSPs and /dev/null differ
>Index: images/newdeployment.gif
>===================================================================
>RCS file: images/newdeployment.gif
>diff -N images/newdeployment.gif
>Binary files /tmp/cvs.3ij7V8 and /dev/null differ
>Index: images/newdeployment2.gif
>===================================================================
>RCS file: images/newdeployment2.gif
>diff -N images/newdeployment2.gif
>Binary files /tmp/cvs.3kZA2O and /dev/null differ
>Index: images/newdeployment3.gif
>===================================================================
>RCS file: images/newdeployment3.gif
>diff -N images/newdeployment3.gif
>Binary files /tmp/cvs.pn4j9u and /dev/null differ
>Index: images/newdeployment5.gif
>===================================================================
>RCS file: images/newdeployment5.gif
>diff -N images/newdeployment5.gif
>Binary files /tmp/cvs.gIoigb and /dev/null differ
>Index: images/newdeployment6.gif
>===================================================================
>RCS file: images/newdeployment6.gif
>diff -N images/newdeployment6.gif
>Binary files /tmp/cvs.tPcwnR and /dev/null differ
>Index: images/newdeployment7.gif
>===================================================================
>RCS file: images/newdeployment7.gif
>diff -N images/newdeployment7.gif
>Binary files /tmp/cvs.BxhZux and /dev/null differ
>Index: images/newdeployment8.gif
>===================================================================
>RCS file: images/newdeployment8.gif
>diff -N images/newdeployment8.gif
>Binary files /tmp/cvs.h4rHCd and /dev/null differ
>Index: images/newmanualtest.gif
>===================================================================
>RCS file: images/newmanualtest.gif
>diff -N images/newmanualtest.gif
>Binary files /tmp/cvs.cCeSKT and /dev/null differ
>Index: images/newmanualtest2.gif
>===================================================================
>RCS file: images/newmanualtest2.gif
>diff -N images/newmanualtest2.gif
>Binary files /tmp/cvs.En2kTz and /dev/null differ
>Index: images/newmanualtest3.gif
>===================================================================
>RCS file: images/newmanualtest3.gif
>diff -N images/newmanualtest3.gif
>Binary files /tmp/cvs.kLh31f and /dev/null differ
>Index: images/newwizard.gif
>===================================================================
>RCS file: images/newwizard.gif
>diff -N images/newwizard.gif
>Binary files /tmp/cvs.0yM0aW and /dev/null differ
>Index: images/ngibmcpy.gif
>===================================================================
>RCS file: images/ngibmcpy.gif
>diff -N images/ngibmcpy.gif
>Binary files /tmp/cvs.qn3InC and /dev/null differ
>Index: images/perspectiveMan.gif
>===================================================================
>RCS file: images/perspectiveMan.gif
>diff -N images/perspectiveMan.gif
>Binary files /tmp/cvs.GPOQAi and /dev/null differ
>Index: images/perspectives2.gif
>===================================================================
>RCS file: images/perspectives2.gif
>diff -N images/perspectives2.gif
>Binary files /tmp/cvs.6GEhOY and /dev/null differ
>Index: images/runFromWhere.gif
>===================================================================
>RCS file: images/runFromWhere.gif
>diff -N images/runFromWhere.gif
>Binary files /tmp/cvs.YyDJ2E and /dev/null differ
>Index: images_manualtest/DeployExample_files/image001.png
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image001.png
>diff -N images_manualtest/DeployExample_files/image001.png
>Binary files /tmp/cvs.Ax8dIl and /dev/null differ
>Index: images_manualtest/DeployExample_files/image002.jpg
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image002.jpg
>diff -N images_manualtest/DeployExample_files/image002.jpg
>Binary files /tmp/cvs.mNjYn2 and /dev/null differ
>Index: images_manualtest/DeployExample_files/image003.png
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image003.png
>diff -N images_manualtest/DeployExample_files/image003.png
>Binary files /tmp/cvs.FNvr4I and /dev/null differ
>Index: images_manualtest/DeployExample_files/image004.jpg
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image004.jpg
>diff -N images_manualtest/DeployExample_files/image004.jpg
>Binary files /tmp/cvs.k93aLp and /dev/null differ
>Index: images_manualtest/DeployExample_files/image005.png
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image005.png
>diff -N images_manualtest/DeployExample_files/image005.png
>Binary files /tmp/cvs.qcybs6 and /dev/null differ
>Index: images_manualtest/DeployExample_files/image006.jpg
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image006.jpg
>diff -N images_manualtest/DeployExample_files/image006.jpg
>Binary files /tmp/cvs.kJgq9M and /dev/null differ
>Index: images_manualtest/DeployExample_files/image007.png
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image007.png
>diff -N images_manualtest/DeployExample_files/image007.png
>Binary files /tmp/cvs.JDfWQt and /dev/null differ
>Index: images_manualtest/DeployExample_files/image008.jpg
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image008.jpg
>diff -N images_manualtest/DeployExample_files/image008.jpg
>Binary files /tmp/cvs.fXtGya and /dev/null differ
>Index: images_manualtest/DeployExample_files/image009.png
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image009.png
>diff -N images_manualtest/DeployExample_files/image009.png
>Binary files /tmp/cvs.zl6DgR and /dev/null differ
>Index: images_manualtest/DeployExample_files/image010.jpg
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image010.jpg
>diff -N images_manualtest/DeployExample_files/image010.jpg
>Binary files /tmp/cvs.RyWPYx and /dev/null differ
>Index: images_manualtest/DeployExample_files/image011.png
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image011.png
>diff -N images_manualtest/DeployExample_files/image011.png
>Binary files /tmp/cvs.mDbgHe and /dev/null differ
>Index: images_manualtest/DeployExample_files/image012.jpg
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image012.jpg
>diff -N images_manualtest/DeployExample_files/image012.jpg
>Binary files /tmp/cvs.xcKSpV and /dev/null differ
>Index: images_manualtest/DeployExample_files/image013.png
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image013.png
>diff -N images_manualtest/DeployExample_files/image013.png
>Binary files /tmp/cvs.jSjQ8B and /dev/null differ
>Index: images_manualtest/DeployExample_files/image014.jpg
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image014.jpg
>diff -N images_manualtest/DeployExample_files/image014.jpg
>Binary files /tmp/cvs.vzh1Ri and /dev/null differ
>Index: images_manualtest/DeployExample_files/image015.png
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image015.png
>diff -N images_manualtest/DeployExample_files/image015.png
>Binary files /tmp/cvs.icErBZ and /dev/null differ
>Index: images_manualtest/DeployExample_files/image016.jpg
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image016.jpg
>diff -N images_manualtest/DeployExample_files/image016.jpg
>Binary files /tmp/cvs.OGq4kG and /dev/null differ
>Index: images_manualtest/DeployExample_files/image017.png
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image017.png
>diff -N images_manualtest/DeployExample_files/image017.png
>Binary files /tmp/cvs.hLjU4m and /dev/null differ
>Index: images_manualtest/DeployExample_files/image018.jpg
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image018.jpg
>diff -N images_manualtest/DeployExample_files/image018.jpg
>Binary files /tmp/cvs.WzJYO3 and /dev/null differ
>Index: images_manualtest/DeployExample_files/image019.png
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image019.png
>diff -N images_manualtest/DeployExample_files/image019.png
>Binary files /tmp/cvs.xomhzK and /dev/null differ
>Index: images_manualtest/DeployExample_files/image020.jpg
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image020.jpg
>diff -N images_manualtest/DeployExample_files/image020.jpg
>Binary files /tmp/cvs.c1iNjr and /dev/null differ
>Index: images_manualtest/DeployExample_files/image021.png
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image021.png
>diff -N images_manualtest/DeployExample_files/image021.png
>Binary files /tmp/cvs.THBv47 and /dev/null differ
>Index: images_manualtest/DeployExample_files/image022.jpg
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image022.jpg
>diff -N images_manualtest/DeployExample_files/image022.jpg
>Binary files /tmp/cvs.vkrrPO and /dev/null differ
>Index: images_manualtest/DeployExample_files/image023.png
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image023.png
>diff -N images_manualtest/DeployExample_files/image023.png
>Binary files /tmp/cvs.1OrBAv and /dev/null differ
>Index: images_manualtest/DeployExample_files/image024.jpg
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image024.jpg
>diff -N images_manualtest/DeployExample_files/image024.jpg
>Binary files /tmp/cvs.deJZlc and /dev/null differ
>Index: images_manualtest/DeployExample_files/image025.png
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image025.png
>diff -N images_manualtest/DeployExample_files/image025.png
>Binary files /tmp/cvs.oXgE7S and /dev/null differ
>Index: images_manualtest/DeployExample_files/image026.jpg
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image026.jpg
>diff -N images_manualtest/DeployExample_files/image026.jpg
>Binary files /tmp/cvs.nV1zTz and /dev/null differ
>Index: images_manualtest/DeployExample_files/image027.png
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image027.png
>diff -N images_manualtest/DeployExample_files/image027.png
>Binary files /tmp/cvs.Js6JFg and /dev/null differ
>Index: images_manualtest/DeployExample_files/image028.jpg
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image028.jpg
>diff -N images_manualtest/DeployExample_files/image028.jpg
>Binary files /tmp/cvs.Alq6rX and /dev/null differ
>Index: images_manualtest/DeployExample_files/image029.png
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image029.png
>diff -N images_manualtest/DeployExample_files/image029.png
>Binary files /tmp/cvs.r4aHeE and /dev/null differ
>Index: images_manualtest/DeployExample_files/image030.jpg
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image030.jpg
>diff -N images_manualtest/DeployExample_files/image030.jpg
>Binary files /tmp/cvs.qvWF1k and /dev/null differ
>Index: images_manualtest/DeployExample_files/image031.png
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image031.png
>diff -N images_manualtest/DeployExample_files/image031.png
>Binary files /tmp/cvs.kqEYO1 and /dev/null differ
>Index: images_manualtest/DeployExample_files/image032.jpg
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image032.jpg
>diff -N images_manualtest/DeployExample_files/image032.jpg
>Binary files /tmp/cvs.YnmzCI and /dev/null differ
>Index: images_manualtest/DeployExample_files/image033.png
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image033.png
>diff -N images_manualtest/DeployExample_files/image033.png
>Binary files /tmp/cvs.7Ggsqp and /dev/null differ
>Index: images_manualtest/DeployExample_files/image034.jpg
>===================================================================
>RCS file: images_manualtest/DeployExample_files/image034.jpg
>diff -N images_manualtest/DeployExample_files/image034.jpg
>Binary files /tmp/cvs.NojBe6 and /dev/null differ
>Index: images_manualtest/analysis_files/image001.png
>===================================================================
>RCS file: images_manualtest/analysis_files/image001.png
>diff -N images_manualtest/analysis_files/image001.png
>Binary files /tmp/cvs.Gud62M and /dev/null differ
>Index: images_manualtest/analysis_files/image002.jpg
>===================================================================
>RCS file: images_manualtest/analysis_files/image002.jpg
>diff -N images_manualtest/analysis_files/image002.jpg
>Binary files /tmp/cvs.4AqORt and /dev/null differ
>Index: images_manualtest/analysis_files/image003.png
>===================================================================
>RCS file: images_manualtest/analysis_files/image003.png
>diff -N images_manualtest/analysis_files/image003.png
>Binary files /tmp/cvs.wa7MGa and /dev/null differ
>Index: images_manualtest/analysis_files/image004.jpg
>===================================================================
>RCS file: images_manualtest/analysis_files/image004.jpg
>diff -N images_manualtest/analysis_files/image004.jpg
>Binary files /tmp/cvs.Lq6ZvR and /dev/null differ
>Index: images_manualtest/analysis_files/image005.png
>===================================================================
>RCS file: images_manualtest/analysis_files/image005.png
>diff -N images_manualtest/analysis_files/image005.png
>Binary files /tmp/cvs.cxwqly and /dev/null differ
>Index: images_manualtest/analysis_files/image006.jpg
>===================================================================
>RCS file: images_manualtest/analysis_files/image006.jpg
>diff -N images_manualtest/analysis_files/image006.jpg
>Binary files /tmp/cvs.Hqm3af and /dev/null differ
>Index: images_manualtest/analysis_files/image007.png
>===================================================================
>RCS file: images_manualtest/analysis_files/image007.png
>diff -N images_manualtest/analysis_files/image007.png
>Binary files /tmp/cvs.IGoS0V and /dev/null differ
>Index: images_manualtest/analysis_files/image008.jpg
>===================================================================
>RCS file: images_manualtest/analysis_files/image008.jpg
>diff -N images_manualtest/analysis_files/image008.jpg
>Binary files /tmp/cvs.3RUXQC and /dev/null differ
>Index: images_manualtest/analysis_files/image009.png
>===================================================================
>RCS file: images_manualtest/analysis_files/image009.png
>diff -N images_manualtest/analysis_files/image009.png
>Binary files /tmp/cvs.yaRfHj and /dev/null differ
>Index: images_manualtest/analysis_files/image010.jpg
>===================================================================
>RCS file: images_manualtest/analysis_files/image010.jpg
>diff -N images_manualtest/analysis_files/image010.jpg
>Binary files /tmp/cvs.aZMKx0 and /dev/null differ
>Index: images_manualtest/analysis_files/image011.png
>===================================================================
>RCS file: images_manualtest/analysis_files/image011.png
>diff -N images_manualtest/analysis_files/image011.png
>Binary files /tmp/cvs.NqRwoH and /dev/null differ
>Index: images_manualtest/analysis_files/image012.jpg
>===================================================================
>RCS file: images_manualtest/analysis_files/image012.jpg
>diff -N images_manualtest/analysis_files/image012.jpg
>Binary files /tmp/cvs.I9jvfo and /dev/null differ
>Index: images_manualtest/analysis_files/image013.png
>===================================================================
>RCS file: images_manualtest/analysis_files/image013.png
>diff -N images_manualtest/analysis_files/image013.png
>Binary files /tmp/cvs.pibG64 and /dev/null differ
>Index: images_manualtest/analysis_files/image014.jpg
>===================================================================
>RCS file: images_manualtest/analysis_files/image014.jpg
>diff -N images_manualtest/analysis_files/image014.jpg
>Binary files /tmp/cvs.OiI3XL and /dev/null differ
>Index: images_manualtest/analysis_files/image015.png
>===================================================================
>RCS file: images_manualtest/analysis_files/image015.png
>diff -N images_manualtest/analysis_files/image015.png
>Binary files /tmp/cvs.I6pEPs and /dev/null differ
>Index: images_manualtest/analysis_files/image016.jpg
>===================================================================
>RCS file: images_manualtest/analysis_files/image016.jpg
>diff -N images_manualtest/analysis_files/image016.jpg
>Binary files /tmp/cvs.aVErH9 and /dev/null differ
>Index: images_manualtest/analysis_files/image017.png
>===================================================================
>RCS file: images_manualtest/analysis_files/image017.png
>diff -N images_manualtest/analysis_files/image017.png
>Binary files /tmp/cvs.Q2grzQ and /dev/null differ
>Index: images_manualtest/analysis_files/image018.jpg
>===================================================================
>RCS file: images_manualtest/analysis_files/image018.jpg
>diff -N images_manualtest/analysis_files/image018.jpg
>Binary files /tmp/cvs.qWgDrx and /dev/null differ
>Index: images_manualtest/building_files/image001.png
>===================================================================
>RCS file: images_manualtest/building_files/image001.png
>diff -N images_manualtest/building_files/image001.png
>Binary files /tmp/cvs.kJj9je and /dev/null differ
>Index: images_manualtest/building_files/image002.jpg
>===================================================================
>RCS file: images_manualtest/building_files/image002.jpg
>diff -N images_manualtest/building_files/image002.jpg
>Binary files /tmp/cvs.9lKRcV and /dev/null differ
>Index: images_manualtest/building_files/image003.png
>===================================================================
>RCS file: images_manualtest/building_files/image003.png
>diff -N images_manualtest/building_files/image003.png
>Binary files /tmp/cvs.WNvN5B and /dev/null differ
>Index: images_manualtest/building_files/image004.jpg
>===================================================================
>RCS file: images_manualtest/building_files/image004.jpg
>diff -N images_manualtest/building_files/image004.jpg
>Binary files /tmp/cvs.1CpXYi and /dev/null differ
>Index: images_manualtest/building_files/image005.png
>===================================================================
>RCS file: images_manualtest/building_files/image005.png
>diff -N images_manualtest/building_files/image005.png
>Binary files /tmp/cvs.htDlSZ and /dev/null differ
>Index: images_manualtest/building_files/image006.jpg
>===================================================================
>RCS file: images_manualtest/building_files/image006.jpg
>diff -N images_manualtest/building_files/image006.jpg
>Binary files /tmp/cvs.4BD4LG and /dev/null differ
>Index: images_manualtest/building_files/image007.png
>===================================================================
>RCS file: images_manualtest/building_files/image007.png
>diff -N images_manualtest/building_files/image007.png
>Binary files /tmp/cvs.C5xAGn and /dev/null differ
>Index: images_manualtest/building_files/image008.jpg
>===================================================================
>RCS file: images_manualtest/building_files/image008.jpg
>diff -N images_manualtest/building_files/image008.jpg
>Binary files /tmp/cvs.py4kB4 and /dev/null differ
>Index: images_manualtest/building_files/image009.png
>===================================================================
>RCS file: images_manualtest/building_files/image009.png
>diff -N images_manualtest/building_files/image009.png
>Binary files /tmp/cvs.OEKjwL and /dev/null differ
>Index: images_manualtest/building_files/image010.jpg
>===================================================================
>RCS file: images_manualtest/building_files/image010.jpg
>diff -N images_manualtest/building_files/image010.jpg
>Binary files /tmp/cvs.aAJwrs and /dev/null differ
>Index: images_manualtest/editor_files/image001.png
>===================================================================
>RCS file: images_manualtest/editor_files/image001.png
>diff -N images_manualtest/editor_files/image001.png
>Binary files /tmp/cvs.bi18m9 and /dev/null differ
>Index: images_manualtest/editor_files/image002.jpg
>===================================================================
>RCS file: images_manualtest/editor_files/image002.jpg
>diff -N images_manualtest/editor_files/image002.jpg
>Binary files /tmp/cvs.CWXajQ and /dev/null differ
>Index: images_manualtest/editor_files/image003.png
>===================================================================
>RCS file: images_manualtest/editor_files/image003.png
>diff -N images_manualtest/editor_files/image003.png
>Binary files /tmp/cvs.AlJufx and /dev/null differ
>Index: images_manualtest/editor_files/image004.jpg
>===================================================================
>RCS file: images_manualtest/editor_files/image004.jpg
>diff -N images_manualtest/editor_files/image004.jpg
>Binary files /tmp/cvs.Zcw5be and /dev/null differ
>Index: images_manualtest/editor_files/image005.png
>===================================================================
>RCS file: images_manualtest/editor_files/image005.png
>diff -N images_manualtest/editor_files/image005.png
>Binary files /tmp/cvs.D2yW8U and /dev/null differ
>Index: images_manualtest/editor_files/image006.jpg
>===================================================================
>RCS file: images_manualtest/editor_files/image006.jpg
>diff -N images_manualtest/editor_files/image006.jpg
>Binary files /tmp/cvs.yhla6B and /dev/null differ
>Index: images_manualtest/editor_files/image007.png
>===================================================================
>RCS file: images_manualtest/editor_files/image007.png
>diff -N images_manualtest/editor_files/image007.png
>Binary files /tmp/cvs.FoFA3i and /dev/null differ
>Index: images_manualtest/editor_files/image008.jpg
>===================================================================
>RCS file: images_manualtest/editor_files/image008.jpg
>diff -N images_manualtest/editor_files/image008.jpg
>Binary files /tmp/cvs.puZi1Z and /dev/null differ
>Index: images_manualtest/editor_files/image009.png
>===================================================================
>RCS file: images_manualtest/editor_files/image009.png
>diff -N images_manualtest/editor_files/image009.png
>Binary files /tmp/cvs.GBHdZG and /dev/null differ
>Index: images_manualtest/editor_files/image010.jpg
>===================================================================
>RCS file: images_manualtest/editor_files/image010.jpg
>diff -N images_manualtest/editor_files/image010.jpg
>Binary files /tmp/cvs.WWOkXn and /dev/null differ
>Index: images_manualtest/editor_files/image011.png
>===================================================================
>RCS file: images_manualtest/editor_files/image011.png
>diff -N images_manualtest/editor_files/image011.png
>Binary files /tmp/cvs.CkhEV4 and /dev/null differ
>Index: images_manualtest/editor_files/image012.jpg
>===================================================================
>RCS file: images_manualtest/editor_files/image012.jpg
>diff -N images_manualtest/editor_files/image012.jpg
>Binary files /tmp/cvs.ay39TL and /dev/null differ
>Index: images_manualtest/editor_files/image013.png
>===================================================================
>RCS file: images_manualtest/editor_files/image013.png
>diff -N images_manualtest/editor_files/image013.png
>Binary files /tmp/cvs.bHqSSs and /dev/null differ
>Index: images_manualtest/editor_files/image014.jpg
>===================================================================
>RCS file: images_manualtest/editor_files/image014.jpg
>diff -N images_manualtest/editor_files/image014.jpg
>Binary files /tmp/cvs.Xp9NR9 and /dev/null differ
>Index: images_manualtest/editor_files/image015.png
>===================================================================
>RCS file: images_manualtest/editor_files/image015.png
>diff -N images_manualtest/editor_files/image015.png
>Binary files /tmp/cvs.k6gWQQ and /dev/null differ
>Index: images_manualtest/editor_files/image016.jpg
>===================================================================
>RCS file: images_manualtest/editor_files/image016.jpg
>diff -N images_manualtest/editor_files/image016.jpg
>Binary files /tmp/cvs.cpLgQx and /dev/null differ
>Index: images_manualtest/run_files/image001.png
>===================================================================
>RCS file: images_manualtest/run_files/image001.png
>diff -N images_manualtest/run_files/image001.png
>Binary files /tmp/cvs.oZhWPe and /dev/null differ
>Index: images_manualtest/run_files/image002.jpg
>===================================================================
>RCS file: images_manualtest/run_files/image002.jpg
>diff -N images_manualtest/run_files/image002.jpg
>Binary files /tmp/cvs.hmjOPV and /dev/null differ
>Index: images_manualtest/run_files/image003.png
>===================================================================
>RCS file: images_manualtest/run_files/image003.png
>diff -N images_manualtest/run_files/image003.png
>Binary files /tmp/cvs.zavTPC and /dev/null differ
>Index: images_manualtest/run_files/image004.jpg
>===================================================================
>RCS file: images_manualtest/run_files/image004.jpg
>diff -N images_manualtest/run_files/image004.jpg
>Binary files /tmp/cvs.arTVQj and /dev/null differ
>Index: images_manualtest/run_files/image005.gif
>===================================================================
>RCS file: images_manualtest/run_files/image005.gif
>diff -N images_manualtest/run_files/image005.gif
>Binary files /tmp/cvs.nT8KS0 and /dev/null differ
>Index: images_manualtest/run_files/image006.png
>===================================================================
>RCS file: images_manualtest/run_files/image006.png
>diff -N images_manualtest/run_files/image006.png
>Binary files /tmp/cvs.LknOUH and /dev/null differ
>Index: images_manualtest/run_files/image007.jpg
>===================================================================
>RCS file: images_manualtest/run_files/image007.jpg
>diff -N images_manualtest/run_files/image007.jpg
>Binary files /tmp/cvs.jrd4Wo and /dev/null differ
>Index: images_manualtest/run_files/image008.png
>===================================================================
>RCS file: images_manualtest/run_files/image008.png
>diff -N images_manualtest/run_files/image008.png
>Binary files /tmp/cvs.9L8xZ5 and /dev/null differ
>Index: images_manualtest/run_files/image009.jpg
>===================================================================
>RCS file: images_manualtest/run_files/image009.jpg
>diff -N images_manualtest/run_files/image009.jpg
>Binary files /tmp/cvs.TQof2M and /dev/null differ
>Index: images_manualtest/run_files/image010.png
>===================================================================
>RCS file: images_manualtest/run_files/image010.png
>diff -N images_manualtest/run_files/image010.png
>Binary files /tmp/cvs.kmWa5t and /dev/null differ
>Index: images_manualtest/run_files/image011.jpg
>===================================================================
>RCS file: images_manualtest/run_files/image011.jpg
>diff -N images_manualtest/run_files/image011.jpg
>Binary files /tmp/cvs.36Nk8a and /dev/null differ
>Index: images_manualtest/run_files/image012.png
>===================================================================
>RCS file: images_manualtest/run_files/image012.png
>diff -N images_manualtest/run_files/image012.png
>Binary files /tmp/cvs.aPVIbS and /dev/null differ
>Index: images_manualtest/run_files/image013.jpg
>===================================================================
>RCS file: images_manualtest/run_files/image013.jpg
>diff -N images_manualtest/run_files/image013.jpg
>Binary files /tmp/cvs.L0jmfz and /dev/null differ
>Index: mtest/tptpManualTestDeployExample.htm
>===================================================================
>RCS file: mtest/tptpManualTestDeployExample.htm
>diff -N mtest/tptpManualTestDeployExample.htm
>--- mtest/tptpManualTestDeployExample.htm	19 Sep 2005 14:34:43 -0000	1.3
>+++ /dev/null	1 Jan 1970 00:00:00 -0000
>@@ -1,295 +0,0 @@
>-<?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>
>-
>-</style>
>-</head>
>-
>-<body link=blue vlink=purple>
>-
>-<div>
>-
>-<div>
>-
>-<h1>TPTP Manual Test
>-Deployment</h1>
>-
>-</div>
>-
>-<h2>Introduction</h2>
>-
>-By default, a Manual Test is deployed on the machine that
>-it is created on (localhost). To change this so that it will run on a different
>-machine, it is necessary to create a
>-specific deployment.
>-
>-&nbsp;
>-
>-<h2>Test Deployment, Artifacts, Locations</h2>
>-
>-In the basic Manual Test tutorial we saw that test artifacts
>-are objects like test suites and data pools; 
>-test locations identify the computer where the test suite is to
>-be run; and a test deployment definition typically consists of a pair
>-comprising a test artifact and a location. TPTP interprets the pairing and
>-deploys the test artifacts on the computer specified. 
>-
>-Test deployments need only specify a location i.e. test
>-artifacts are not necessary. Such deployments may be 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 then deploys the test suite to the
>-computer specified in the deployment definition and runs the test suite on that
>-computer.
>-
>-<h2>Deployment</h2>
>-
>-To establish a deployment for the manual test suite,
>-right-click on the test suite, then
>-select New/Other, then Test/Test Assets/Deployment:
>-
>-&nbsp;
>-
>-
>-
>-&nbsp;
>-
>-Now click on Next and
>-name the deployment exampleManualTestDeploy in the next dialog:
>-
>-
>-
>-&nbsp;
>-
>-Click on Next again to (optionally) describe the
>-deployment:
>-
>-&nbsp;
>-
>-
>-
>-&nbsp;
>-
>-Selecting Next once more brings up the Add Artifact
>-Association dialog. 
>-
>-
>-
>-&nbsp;
>-
>-Select 'Create a new resource' and click on Next.
>-
>-&nbsp;
>-
>-
>-
>-&nbsp;
>-
>-Identify the parent folder and name the artifact (exampleManualTestArtifact).
>-Click on next to move on to the dialog that allows you to describe the
>-artifact:
>-
>-
>-
>-&nbsp;
>-
>-Clicking on Next allows the actual test element to be
>-associated with the artifact to be specified:
>-
>-
>-
>-&nbsp;
>-
>-Click on Finish. The next dialog defines the
>-artifact(s) to be added to the deployment:
>-
>-&nbsp;
>-
>-
>-
>-We then go through an identical procedure in respect of
>-location; firstly naming and locating the location:
>-
>-
>-
>-&nbsp;
>-
>-Click on Next to bring up the location description
>-dialog:
>-
>- 
>-
>-
>-
>-&nbsp;
>-
>-Clicking Finish results in the Select Resource
>-dialog appearing:
>-
>-
>-
>-&nbsp;
>-
>-And selecting Finish at this point produces the
>-artifact to location mapping dialog:
>-
>-
>-
>-&nbsp;
>-
>-Select the artifact and location entities and click on the
>-down-arrow to create the requisite pairing; then click on Finish.
>-
>-<h2>Viewing and Editing Deployments</h2>
>-
>-Once the artifact(s), locations(s), and deployments have been created, they can be viewed/edited
>-at any time by double-clicking on their respective definition files. 
>-
>-<h3>Artifacts</h3>
>-
>-For example, double-clicking on the newly created artifact
>-brings up the Artifact editor view:
>-
>-&nbsp;
>-
>-
>-
>-&nbsp;
>-
>-The Test Assets tab shows the assets associated with the
>-artifact and allows them to be modified:
>-
>-
>-
>-&nbsp;
>-
>-<h3>Locations</h3>
>-
>-Similarly, double-clicking on the location file displays
>-the Location editor view:
>-
>-
>-
>-To alter the machine that the test will run on replace
>-'localhost' in the the Host name field
>-by the name of the requisite machine.
>-
>-<h3>Deployments</h3>
>-
>-Double-clicking on the deploy_statcon_test file displays
>-the Deployment editor view:
>-
>-&nbsp;
>-
>-
>-
>-&nbsp;
>-
>-Switching to the Pairs tab allows artifacts/locations to
>-be added and new pairings created:
>-
>-
>-
>-&nbsp;
>-
>-(C) Copyright IBM Corporation 2000, 2005. All Rights
>-Reserved.
>-
>-&nbsp;
>-
>-</div>
>-
>-</body>
>-
>-</html>
>Index: mtest/tptpManualTest_analysis.htm
>===================================================================
>RCS file: mtest/tptpManualTest_analysis.htm
>diff -N mtest/tptpManualTest_analysis.htm
>--- mtest/tptpManualTest_analysis.htm	19 Sep 2005 14:34:43 -0000	1.3
>+++ /dev/null	1 Jan 1970 00:00:00 -0000
>@@ -1,229 +0,0 @@
>-<?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>
>-
>-</style>
>-</head>
>-
>-<body link=blue vlink=purple>
>-
>-<div>
>-
>-<h2>Analysis </h2>
>-
>-The results are placed in Test Log files of type .execution
>-in the project folder. Double-clicking on the exampleManualTest_x.execution
>-file (or right-clicking on it and selecting Open) brings up the Execution
>-view, below, with the Overview tab selected by default.
>-
>-
>-
>- 
>-
>-<h3>Overview Tab</h3>
>-
>-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: 
>-
>-/manualTests/exampleManualTest_x.execution 
>-
>-in this case.
>-
>-The link Go to first fail switches to the Events
>-tab and position the Test Log at the first recorded failure in the
>-test.
>-
>-The Summary section gives: the Type (Manual Test),
>-the File (/manualTests/exampleManualTest), the Host name
>-(localhost) the Verdict on the test ('error' in the above example), and
>-the Start/Finish times of the manual test. The verdict is drawn from: pass; fail;inconclusive;error;
>-where the latter indicates an error within the manual test itself rather than an
>-error in the software being tested.
>-
>-<h3>Events Tab</h3>
>-
>-Select the Events tab to see the test suite
>-execution record:
>-
>- 
>-
>-
>-&nbsp;
>-
>-The left-hand (Events) pane contains a graphical,
>-tree-structure representation of the Test Log, and the right-hand (Common
>-Properties) pane contains information about the particular node that is
>-selected within the Test Log.
>-
>-The execution tree-structure is a chronological
>-sequence of event nodes:
>-
>-
>-
>-&nbsp;
>-
>-With the following interpretation:
>-
>-<div align=center>
>-
>-<table border=1 cellspacing=0 cellpadding=0>
>- <tr>
>- <td width=103 valign=top>
>- Node
>- Type
>- </td>
>- <td width=384 valign=top>
>- Meaning
>- </td>
>- </tr>
>- <tr>
>- <td width=103 valign=top>
>- start
>- </td>
>- <td width=384 valign=top>
>- Indicates
>- the start of some process (e.g. invocation); provides time:
>- &nbsp;
>- 
>- </td>
>- </tr>
>- <tr>
>- <td width=103 valign=top>
>- stop
>- </td>
>- <td width=384 valign=top>
>- Indicates
>- the end of some process (e.g. invocation); provides time. Exactly as for start
>- node except that the node type is stop.
>- </td>
>- </tr>
>- <tr>
>- <td width=103 valign=top>
>- invocation
>- </td>
>- <td width=384 valign=top>
>- Corresponds
>- to a test case invocation; expands to show underlying node structure:
>- &nbsp;
>- 
>- &nbsp;
>- In which
>- the start/stop nodes are as above while the pass node indicates that the
>- particular invocation involved passed the tester's criteria.
>- &nbsp;
>- The
>- invocation outcome node (coded as pass, failed, error, inconclusive) lies between
>- the start/stop nodes:
>- 
>- 
>- &nbsp;
>- </td>
>- </tr>
>- <tr>
>- <td width=103 valign=top>
>- message
>- </td>
>- <td width=384 valign=top>
>- Provides
>- information about a stage in the manual test; normally one at the beginning
>- and end of a test.
>- &nbsp;
>- 
>- </td>
>- </tr>
>-</table>
>-
>-</div>
>-
>-&nbsp;
>-
>-The Previous fail and Next fail
>-buttons move the focus within the history backwards (chronologically) and
>-forwards (chronologically) respectively to the next failure node.
>-
>-Click on an event node in the Events pane to get
>-information about that event in the right-hand pane.
>-
>-In the case below, an  event node has been selected and the
>-information displayed as follows:
>-
>-
>-
>-&nbsp;
>-
>-(C) Copyright IBM Corporation 2000, 2005. All Rights
>-Reserved.
>-
>-</div>
>-
>-</body>
>-
>-</html>
>Index: mtest/tptpManualTest_building.htm
>===================================================================
>RCS file: mtest/tptpManualTest_building.htm
>diff -N mtest/tptpManualTest_building.htm
>--- mtest/tptpManualTest_building.htm	19 Sep 2005 14:34:43 -0000	1.3
>+++ /dev/null	1 Jan 1970 00:00:00 -0000
>@@ -1,119 +0,0 @@
>-<?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>
>-
>-</style>
>-</head>
>-
>-<body link=blue vlink=purple>
>-
>-<div>
>-
>-<h2>Building a Manual Test</h2>
>-
>-<h3>Create a new manual test suite</h3>
>-
>-Right-click in the Navigator view and select New/Other:
>-
>-&nbsp;
>-
>-
>-
>-&nbsp;
>-
>-Then select Test/TPTP Manual Test from the
>-resulting New dialog:
>-
>-&nbsp;
>-
>-
>-
>-&nbsp;
>-
>-Now click on Next and name the the manual test in (exampleManualTest):
>-
>-&nbsp;
>-
>-
>-
>-&nbsp;
>-
>-Then click on Next and (optionally) provide a
>-description for the manual test suite and click on Finish:
>-
>-
>-
>-&nbsp;
>-
>-A manual test testsuite file (exampleManualTest.testsuite)
>-will be created and becomes visible in the Navigator view:
>-
>-&nbsp;
>-
>-
>-
>-&nbsp;
>-
>-(C) Copyright IBM Corporation 2000, 2005. All Rights
>-Reserved.
>-
>-</div>
>-
>-</body>
>-
>-</html>
>Index: mtest/tptpManualTest_editor.htm
>===================================================================
>RCS file: mtest/tptpManualTest_editor.htm
>diff -N mtest/tptpManualTest_editor.htm
>--- mtest/tptpManualTest_editor.htm	19 Sep 2005 14:34:43 -0000	1.3
>+++ /dev/null	1 Jan 1970 00:00:00 -0000
>@@ -1,223 +0,0 @@
>-<?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>
>-
>-</style>
>-</head>
>-
>-<body link=blue vlink=purple>
>-
>-<div>
>-
>-<h2>TPTP Manual Test Suite Editor</h2>
>-
>-We now need to utilise the TPTP Manual TestSuite Editor. Either
>-double-click on the exampleManualTest.testsuite file or
>-right-click on it and select Open from the resultant popup menu. Either
>-way, the TPTP Manual Test editor is invoked:
>-
>-<h3>&nbsp;</h3>
>-
>-
>-
>-There are are 3 tab controls located at the bottom of the
>-editor pane: Overview, Test Cases, and Behavior. We now
>-look at each of these in turn:
>-
>-<h3>Overview Tab</h3>
>-
>-The Overview Tab contains:
>-
>-the Name of the manual test; 
>-
>-a description (optional) of it; 
>-
>-a test type (TPTP Manual Test); and 
>-
>-the path referencing the file containing the Test Suite
>-(/manualTests/exampleManualTest.testsuite).
>-
>-If there are any existing TestCases, their names will be
>-displayed in the right-hand pane of the editor.
>-
>-To switch to the Test Cases view, either select the Test
>-Cases tab or click on the More... button.
>-
>-<h3>Test Cases Tab</h3>
>-
>-The Test Cases section lists the individual tests
>-that will make up the test suite. 
>-
>-
>-
>-To alter a test case name, select the test case (in
>-the left-hand pane) then edit the Name textbox. To alter a test case description,
>-select the test case then edit the Description textbox. Use the
>-Add and Remove
>-buttons to add test cases and to remove existing cases. Use the Up and Down buttons to
>-change the order of cases. 
>-
>-<h3>Behavior Tab</h3>
>-
>-The behavior tab allows you to specify the frequency and
>-order in which test cases are run. This is done via invocations and loops:
>-invocations allow you to specify which test cases you wish to run, and
>-in which order; loops allow you to embed the chosen test cases within a
>-loop which can be iterated one or more times. Behaviors can contain a mixture
>-of invocations and loops.
>-
>-For our (simple) example, we want to run all of the test
>-cases within a single loop iteration. To set up a single loop:
>-
>-Select the Behavior tab, click on the Add...
>-button and select Loop:
>-
>-&nbsp;
>-
>-
>-
>-This will setup a behavior under the control of a single
>-loop. We shall add the test cases to this loop shortly.
>-
>-By default, the number of iterations of a loop is 1. This
>-can be changed via the Number of Iterations
>-box which specifies the number of loop iterations. 
>-
>-
>-
>-If Synchronous
>-is checked and more than one iteration is specified, the loop iterations
>-execute sequentially. If Synchronous is unchecked and more than one
>-iteration specified, the loop iterations execute concurrently. 
>-
>-The Up and Down buttons are
>-used to alter the relative positions of invocations and loops. The Add
>-and Remove buttons are used to add/remove selected
>-loops/invocations.
>-
>-Loops can be nested, and invocations can exist outside of
>-a loop.
>-
>-Now let's proceed to build our example Manual Test. We
>-start with the Test Cases tab:
>-
>-<h3>Test Cases Tab</h3>
>-
>-Select the Test Cases tab and click on the Add...
>-button. This will cause the test case called 'test 1' to be created:
>-
>-
>-
>-&nbsp;
>-
>-&nbsp;
>-
>-We now have to create entries, in sequence, for each of
>-our required test cases: Instruction Set A, Instruction Set B, Instruction Set
>-C, Instruction Set D, Instruction Set E, and Instruction Set F
>-
>-Replace the Name 'test 1' by 'Instruction Set A' (Simply
>-edit the Name field). You can (optionally) put some descriptive text in
>-the Description field.
>-
>-
>-
>-Now click on the Add... button again. This
>-will bring up Test Case 'test 2' by default. Replace this by 'Instruction Set
>-B'. Repeat the process for Instruction Set C, D, E and F.
>-
>-The Test Cases tab view will now look like:
>-
>-
>-
>-&nbsp;
>-
>-The Add and Remove buttons are
>-used to add and delete test cases, while the Up and Down
>-buttons are used to change the relative positions of selected test cases within
>-the overall list.
>-
>-<h3>Behavior Tab</h3>
>-
>-Now we need to associate the test cases that we've just
>-defined with the loop that we setup earlier using the Behavior Tab. Switch back 
>-to the Behavior tab, click on the Add... button,
>-select invocation, and then select all of the test cases on display
>-(use &lt;ctrl&gt;click on each):
>-
>-
>-
>-&nbsp;
>-
>-(C) Copyright IBM Corporation 2000, 2005. All Rights
>-Reserved.
>-
>-</div>
>-
>-</body>
>-
>-</html>
>Index: mtest/tptpManualTest_intro.htm
>===================================================================
>RCS file: mtest/tptpManualTest_intro.htm
>diff -N mtest/tptpManualTest_intro.htm
>--- mtest/tptpManualTest_intro.htm	19 Sep 2005 14:34:43 -0000	1.3
>+++ /dev/null	1 Jan 1970 00:00:00 -0000
>@@ -1,95 +0,0 @@
>-<?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>
>-
>-</style>
>-</head>
>-
>-<body link=blue vlink=purple>
>-
>-<div>
>-
>-<h2>TPTP Manual Test Introduction</h2>
>-
>-The Manual Test facility allows the user to build a set of
>-instructions to be followed when testing a product or product component. To
>-illustrate the process, we shall build a manual test from scratch.
>-
>-Before embarking on this, however, we explain some
>-background terminology that will crop up as we build the test.
>-
>-<h2>Terminology: Test Deployment, Artifacts, Locations</h2>
>-
>-Test artifacts are objects like test suites and
>-data pools. Test locations identify the computer where the test suite is
>-to be run. A test deployment definition typically consists of one or
>-more pairs of test artifacts and locations. Artifacts and Locations are
>-associated in pairs; TPTP interprets the pairing and deploys the test artifacts
>-on the computer specified. 
>-
>-Test deployments need only specify a location i.e. test
>-artifacts are not necessary. Such deployments may be 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 then deploys the test suite to the
>-computer specified in the deployment definition and runs the test suite on that
>-computer.
>-
>-<h2>The Example Manual Test Case</h2>
>-
>-To illustrate the process we shall use generic terminolgy
>-to describe the steps to be followed by the tester. So, our steps will be
>-identified as Instruction Set A, Instruction Set B, Instruction Set C, ... and so
>-on. When running a manual test for real, simply replace the generic terms by
>-specific ones relevant to the test being carried out. For the purposes of this
>-document, we want to represent the following set of test cases: 
>-
>-1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>-Instruction Set A
>-
>-2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>-Instruction Set B
>-
>-3.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>-Instruction Set C
>-
>-4.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>-Instruction Set D
>-
>-5.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>-Instruction Set E
>-
>-6.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>-Instruction Set F
>-
>-&nbsp;
>-
>-and we want these to be issued in sequence, one after the
>-other.
>-
>-To build the manual test we need to progress through a
>-series of stages, as follows:
>-
>-&nbsp;
>-
>-(C) Copyright IBM Corporation 2000, 2005. All Rights
>-Reserved.
>-
>-</div>
>-
>-</body>
>-
>-</html>
>Index: mtest/tptpManualTest_run.htm
>===================================================================
>RCS file: mtest/tptpManualTest_run.htm
>diff -N mtest/tptpManualTest_run.htm
>--- mtest/tptpManualTest_run.htm	19 Sep 2005 14:34:43 -0000	1.3
>+++ /dev/null	1 Jan 1970 00:00:00 -0000
>@@ -1,224 +0,0 @@
>-<?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>
>-
>-</style>
>-</head>
>-
>-<body link=blue vlink=purple>
>-
>-<div>
>-
>-<h2>Preparing to Run the Manual Test</h2>
>-
>-<h3>Test Perspective</h3>
>-
>-Switch to the Test perspective. Select Window/Open
>-Perspective/Other:
>-
>-
>-
>-Then select Test and click on OK.
>-
>-<h3>Launch the Agent Controller</h3>
>-
>-If the Agent Controller has not been launched previously,
>-launch it now.
>-
>-<h3>Running a Test</h3>
>-
>-Right-click on the exampleManualTest test suite
>-file and select Run from the popup menu. This will bring up the Run
>-dialog:
>-
>-
>-
>-&nbsp;
>-
>-&nbsp;
>-
>-&nbsp;
>-
>-Now click on New to display the configuration
>-dialog, and enter (say) test_config. Then click on exampleManualTest
>-in the 'Select Test to run' pane of the Test tab, and on local_deployment
>-in the 'Select a Deployment' pane, then click on Apply.
>-
>-&nbsp;
>-
>-
>-
>-&nbsp;
>-
>-&nbsp;
>-
>-The Test Logs tab allows you to override the log
>-defaults if you wish.
>-
>-&nbsp;
>-
>-
>-
>-&nbsp;
>-
>-Clicking on the Common tab displays:
>-
>-
>-
>-&nbsp;
>-
>-&nbsp;
>-
>-When a test configuration is run, Eclipse creates a file,
>-with a <kbd>.launch</kbd>
>-suffix, containing metadata. The various parameter settings are interpreted as
>-follows:
>-
>-<table border=1 cellspacing=0 cellpadding=0>
>- <tr>
>- <td width=115 valign=top>
>- Parameter
>- </td>
>- <td width=579 valign=top>
>- Meaning
>- </td>
>- </tr>
>- <tr>
>- <td width=115 valign=top>
>- Type of launch configuration:
>- </td>
>- <td width=579 valign=top>
>- Local: Eclipse
>- stores the .launch file in your workspace's metadata folder, which is
>- invisible to other users.
>- Shared: to allow other users accesss to the
>- .launch file. If checked, click Browse
>- then navigate to a folder in your workspace where you want to store the file
>- </td>
>- </tr>
>- <tr>
>- <td width=115 valign=top>
>- Display in favorites menu:
>- </td>
>- <td width=579 valign=top>
>- To have the test configuration appear in the Run, Debug,
>- or Profile favorites toolbar menus, check the
>- appropriate check box in the displayed list.
>- </td>
>- </tr>
>- <tr>
>- <td width=115 valign=top>
>- Launch in background
>- </td>
>- <td width=579 valign=top>
>- If checked, then Eclipse will run the test configuration
>- in the background. If the test configuration is not run in the
>- background, then nothing can be done in Eclipse until it finishes running the
>- test configuration. 
>- </td>
>- </tr>
>-</table>
>-
>-&nbsp;
>-
>-Click Apply to save the
>-settings for the configuration. 
>-
>-<h3>Run the Manual Test</h3>
>-
>-Now run the manual test by clicking on the Run button.
>-This will display the Manual TestCase runtime window:
>-
>-
>-
>-&nbsp;
>-
>-In the exampleManualTest, the first test case
>-(Instruction Set A) is automatically selected. The Name and Description
>-of the test will then be displayed in the right-hand pane. When the tester has
>-carried out the actions in the Description, they record the outcome (pass;
>-failed; returned an error; or was inconclusive) by
>-selecting an appropriate value in the Status
>-drop-down list. They can also enter notes about the test outcomes in the Info field. 
>-
>-Click Next to save the test
>-results and move to the next test. 
>-
>-When the tester has completed the set of tests, they should
>-click on the End Execution button to close the
>-manual test window: 
>-
>-&nbsp;
>-
>-
>-
>-&nbsp;
>-
>-(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
>-
>-</div>
>-
>-</body>
>-
>-</html>
>Index: tasks/tanalyzingmanualtestresults.htm
>===================================================================
>RCS file: /home/tptp/test/org.eclipse.hyades.test.doc.user/tasks/tanalyzingmanualtestresults.htm,v
>retrieving revision 1.2
>diff -u -r1.2 tanalyzingmanualtestresults.htm
>--- tasks/tanalyzingmanualtestresults.htm	19 Sep 2005 14:34:42 -0000	1.2
>+++ tasks/tanalyzingmanualtestresults.htm	28 Sep 2005 22:23:08 -0000
>@@ -1,57 +1,136 @@
>-<?xml version="1.0" encoding="UTF-8"?>
>-<!DOCTYPE html
>- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
>+<?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=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="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" />
>-
>-
>-
>-
>-<link rel="stylesheet" type="text/css" href="../css/ibmdita.css" />
>-<link rel="stylesheet" type="text/css" href="../css/swg_info_common.css" />
>+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
>+<link rel=StyleSheet href="../css/book.css" type="text/css"/>
> <title>Analyzing manual test results</title>
> </head>
>-<body id="analyzingmanualtestresults"><a name="analyzingmanualtestresults"></a>
> 
>-<h1 class="topictitle1">Analyzing manual test results</h1>
>-<div>This topic describes how to analyze results produced from running
>-manual tests.
>-After you run a manual test suite, the results appear in the Test Navigator,
>-as shown below. <img src="../images/manualtestresults.gif" /> 
>-Double-click the results entry to open the Overview tab
>-of the Execution dialog box, as shown below. <img src="../images/manualtestresults2.gif" /> 
>-<div class="p">The execution summary indicates the test suite's verdict and the length
>-of time it took to run the test suite. The verdict is one of the following:<ul><li>pass</li>
>-<li>fail</li>
>-<li>inconclusive</li>
>-<li>error (meaning that the test itself
>-contains an error)</li>
>-</ul>
>+<body>
>+
>+<div>
>+
>+<h2>Analyzing manual test results</h2>
>+
>+The results of a test run are recorded in Test Log files of type .execution
>+in the project folder. Double-click on the .execution 
>+file to launch the Execution
>+view. The Overview tab is selected by default.
>+
>+<h3>Overview Tab</h3>
>+
>+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: 
>+
>+/manualTests/exampleManualTest_x.execution
>+
>+The link Go to first fail switches to the Events
>+tab and positions the Test Log at the first recorded failure in the
>+test.
>+
>+The Summary section reports the properties of the manual test: 
>+<ol>
>+	<li>Type (Manual Test)</li>
>+	<li>File</li>
>+	<li>Host name (localhost)</li>
>+	<li>Verdict</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>
>+
>+Select the Events tab to see the test suite
>+execution record.
>+
>+The left-hand (Events) pane contains a graphical,
>+tree-structure representation of the Test Log, and the right-hand (Common
>+Properties) pane contains information about the particular node that is
>+selected within the Test Log.
>+
>+The execution tree-structure is a chronological
>+sequence of event nodes:
>+
>+<div align=center>
>+
>+<table border=1 cellspacing=0 cellpadding=0>
>+ <tr>
>+ <td width=103 valign=top>
>+ Node
>+ Type
>+ </td>
>+ <td width=384 valign=top>
>+ Meaning
>+ </td>
>+ </tr>
>+ <tr>
>+ <td width=103 valign=top>
>+ start
>+ </td>
>+ <td width=384 valign=top>
>+ Indicates
>+ the start of some process (e.g. invocation); provides time.
>+ </td>
>+ </tr>
>+ <tr>
>+ <td width=103 valign=top>
>+ stop
>+ </td>
>+ <td width=384 valign=top>
>+ Indicates
>+ the end of some process (e.g. invocation); provides time. Exactly as for start
>+ node except that the node type is stop.
>+ </td>
>+ </tr>
>+ <tr>
>+ <td width=103 valign=top>
>+ invocation
>+ </td>
>+ <td width=384 valign=top>
>+ Corresponds
>+ to a test case invocation; expands to show underlying node structure.
>+ In which
>+ the start/stop nodes are as above while the pass node indicates that the
>+ particular invocation involved passed the tester's criteria.
>+ &nbsp;
>+ The
>+ invocation outcome node (coded as pass, failed, error, inconclusive) lies between
>+ the start/stop nodes:
>+ </td>
>+ </tr>
>+ <tr>
>+ <td width=103 valign=top>
>+ message
>+ </td>
>+ <td width=384 valign=top>
>+ Provides
>+ information about a stage in the manual test; normally one at the beginning
>+ and end of a test.
>+ </td>
>+ </tr>
>+</table>
>+
> </div>
>-To view the details of the test suite execution, click the Events tab.
>-The Events tab opens, as shown below. <img src="../images/manualtestresults3.gif" /> 
>-Navigate to an event in the left pane to see details about that event in
>-the fields on the right. 
>+
>+The Previous fail and Next fail
>+buttons move the focus within the history backwards (chronologically) and
>+forwards (chronologically) respectively to the next failure node.
>+
>+Click on an event node in the Events pane to get
>+information about that event in the right-hand pane.
>+
>+(C) Copyright IBM Corporation 2000, 2005. All Rights
>+Reserved.
>+
> </div>
> 
>-<div>
>-
>-Parent topic: <a href="../concepts/cmanualtestoverview.htm" title="">Manual testing with TPTP</a> 
>-
>-</div><div class="runningfooter">(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.</div>
> </body>
>-</html>
>\ No newline at end of file
>+
>+</html>
>Index: tasks/tcreating_test_deployment.htm
>===================================================================
>RCS file: /home/tptp/test/org.eclipse.hyades.test.doc.user/tasks/tcreating_test_deployment.htm,v
>retrieving revision 1.2
>diff -u -r1.2 tcreating_test_deployment.htm
>--- tasks/tcreating_test_deployment.htm	19 Sep 2005 14:34:42 -0000	1.2
>+++ tasks/tcreating_test_deployment.htm	28 Sep 2005 22:23:08 -0000
>@@ -1,130 +1,146 @@
> <?xml version="1.0" encoding="UTF-8"?>
>-<!DOCTYPE html
>- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
>+
>+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
> <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="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" />
>-
>-
>-
>-
>-<link rel="stylesheet" type="text/css" href="../css/ibmdita.css" />
>-<link rel="stylesheet" type="text/css" href="../css/swg_info_common.css" />
>+<meta http-equiv=Content-Type content="text/html; charset=UTF-8"/>
>+<link rel=StyleSheet href="../css/book.css" type="text/css"/>
>+
>+
> <title>Creating a test deployment</title>
>+
> </head>
>-<body id="creatingatestdeployment"><a name="creatingatestdeployment"></a>
> 
>-<h1 class="topictitle1">Creating a test deployment</h1>
>-<div>This topic describes how to create a deployment for your test suite.
>-You must create a deployment before you can run a test.
>-<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>In the Test Navigator select the test suite for which you want
>-to create a deployment. Click File &gt; New &gt; Other. The New wizard
>-opens, as shown below. <img src="../images/newwizard.gif" /> </li>
>-<li>Expand the Test folder and the Test
>-Elements folder, then select Deployment.
>-Click Next. The next page of the wizard opens, as shown
>-below. <img src="../images/newdeployment.gif" /> </li>
>-<li>Navigate to the folder that will store the deployment file resource.
>-Enter a name for the file resource in the File name field.
>-Click Next. The next page of the wizard opens, as shown
>-below. <img src="../images/newdeployment2.gif" /> </li>
>-<li>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 Next.
>-The next page of the wizard opens, as shown below. <img src="../images/newdeployment3.gif" /> </li>
>-<li>To create a deployment that consists of a location only, click Next 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 Add to open the Add Artifact Association page,
>-as shown below. <img src="../images/addartifact.gif" /> </li>
>-<li>If you have previously defined one or more artifacts that you want
>-to use in this deployment, click Browse and navigate
>-to the artifact. After you select the artifact, click Finish.
>-To define a new artifact select Create a new resource and
>-click Next. The New Artifact wizard opens, as shown
>-below. <img src="../images/newartifact.gif" /> </li>
>-<li>Navigate to the folder that will store the artifact file resource.
>-Enter a name for the artifact file resource in the File name field.
>-Click Next. The next page of the wizard opens, as shown
>-below. <img src="../images/newartifact2.gif" /> </li>
>-<li>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 Next.
>-The next page of the wizard opens, as shown below. <img src="../images/newartifact3.gif" /> </li>
>-<li>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 Show
>-Folders. Click Finish. The new artifact
>-appears in the list of artifacts to be added to the deployment, as shown below. <img src="../images/newdeployment5.gif" /> To add another artifact
>-click Add and repeat the steps. When you are satisfied
>-with the list of artifacts, click Next. The next page
>-of the wizard appears, as shown below. <img src="../images/newdeployment6.gif" /> </li>
>-<li>Click Add to select a location to be associated
>-with the deployment. The Add Location Association dialog box opens, as shown
>-below. <img src="../images/addlocation.gif" /> </li>
>-<li>To select an existing location resource click Browse and
>-navigate to the location. To create a location, select Create a
>-new resource and click Next. The New Location
>-wizard opens, as shown below. <img src="../images/addlocation2.gif" /> </li>
>-<li>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 Next. The next page of the wizard appears, as
>-shown below. <img src="../images/addlocation3.gif" /> </li>
>-<li>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 Finish.
>-The new location appears in the list of locations to be added to the deployment,
>-as shown below. <img src="../images/newdeployment7.gif" /> To
>-add another location click Add and repeat the steps.
>-When you are satisfied with the list of locations to be added to the deployment,
>-click Next. The next page of the wizard opens, as shown
>-below. <img src="../images/newdeployment8.gif" /> </li>
>-<li>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 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. </li>
>-<li>From the Test Navigator, double-click the location that you created.
>-The location's Overview tab opens, as shown below. <img src="../images/addlocation4.gif" /> </li>
>-<li>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 Host name field. </li>
>-</ol>
>-</div>
>+<body>
> 
> <div>
>+
>+<h1><a name=creatingatestdeployment></a>Creating a Test Deployment</h1>
>+
>+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.
>+
>+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.
>+
>+To create a test deployment:
>+
>+<ol>
>+	<li>
>+		In
>+		the Test Navigator select the test suite for which you want to create a
>+		deployment. SelectÂ  File &gt; New &gt; Other. The New
>+		wizard opens.
>+	</li>
>+	<li>
>+Expand the Test folder and the Test Assets folder, then select Deployment.
>+Click Next. The next page of the wizard
>+opens.
>+Navigate to the folder that will store the deployment file
>+resource. Enter a name for the deployment in the name
>+field. Click Next. The next page of the
>+wizard opens: 
>+</li>
>+<li>
>+Optionally enter a brief description for the deployment. Click
>+Next. The next page of the wizard opens.
>+</li>
>+<li>
>+(To create a deployment that consists of a location only,
>+click Next and skip ahead to Step 9).
>+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.
>+</li>
>+<li>
>+If you have previously defined one or more artifacts that
>+you want to use in this deployment, click Browse
>+and navigate to the artifact. After you select the artifact, click Finish. To define a new artifact check the Create a new resource button and click Next. The New Artifact wizard opens.
>+</li>
>+<li>
>+Navigate to the folder that will store the artifact file
>+resource. Enter a name for the artifact file resource in the Name field. Click Next.
>+The next page of the wizard opens.
>+</li>
>+<li>
>+Optionally enter a description for the artifact. Click Next. The next page of the wizard opens.
>+</li>
>+<li>
>+Click the boxes next to the test asset(s) that you want to
>+include in the artifact. Click Finish. The
>+new artifact appears in the list of artifacts to be added to the deployment.
> 
>-Parent topic: <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> 
>+To add another artifact click Add and repeat the
>+steps. When you are satisfied with the list of artifacts, click Next. The next page of the wizard appears.
>+</li>
>+<li>
>+Click Add to select a
>+location to be associated with the deployment. The Add Location Association
>+dialog box opens, as above.
>+</li>
>+<li>
>+To select an existing location resource click Browse and navigate to the location. To create a
>+location, check the Create a new resource
>+button and click Next. The New Location
>+wizard opens. 
>+
>+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 Next. The next
>+page of the wizard appears.
>+</li>
>+<li>
>+Optionally
>+enter a description for the location. Click Finish.
>+The new location appears in the list of locations to be added to the
>+deployment.
>+
>+To add another location click Add and
>+repeat the steps. When you are satisfied with the list of locations to be added
>+to the deployment, click Next. The next
>+page of the wizard opens.
>+</li>
>+<li>
>+
>+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.
>+</li>
>+</ol>
>+
>+Related tasks 
>+	<a href="trunningmanualtestsuite.htm">Running a manual test</a> 
>+	<a href="tediting_manual_test.htm">Editing a manual test</a> 
>+	<a href="tanalyzingmanualtestresults.htm">Analyzing manual test results</a> 
>+
>+
>+Related reference 
>+	<a href="../ref/rtestlog.html">Test Log viewer</a> 
> 
>-</div><div class="runningfooter">(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.</div>
>+ 
>+(C) Copyright IBM Corporation 2000, 2005. All Rights
>+Reserved.
>+
>+
>+</div>
>+
> </body>
>+
> </html>
>Index: tasks/tcreatingamanualtest.htm
>===================================================================
>RCS file: /home/tptp/test/org.eclipse.hyades.test.doc.user/tasks/tcreatingamanualtest.htm,v
>retrieving revision 1.2
>diff -u -r1.2 tcreatingamanualtest.htm
>--- tasks/tcreatingamanualtest.htm	19 Sep 2005 14:34:42 -0000	1.2
>+++ tasks/tcreatingamanualtest.htm	28 Sep 2005 22:23:08 -0000
>@@ -1,60 +1,42 @@
>-<?xml version="1.0" encoding="UTF-8"?>
>-<!DOCTYPE html
>- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
>+<?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=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="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" />
>-
>-
>-
>-
>-<link rel="stylesheet" type="text/css" href="../css/ibmdita.css" />
>-<link rel="stylesheet" type="text/css" href="../css/swg_info_common.css" />
>+<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 manual test</title>
>+
> </head>
>-<body id="creating_manual_test"><a name="creating_manual_test"></a>
> 
>-<h1 class="topictitle1">Creating a manual test</h1>
>-<div>This section describes the procedure for creating a manual test
>-suite.
>-<ol><li>Click File &gt; New &gt; Other</li>
>-<li>In the New dialog box, shown below, expand
>-the Test folder, expand the Test Suite folder,
>-select Test Suite, and click Next. <img src="../images/newmanualtest.gif" /> </li>
>-<li>The New Test Suite wizard appears, as shown
>-below. <img src="../images/newmanualtest2.gif" /> 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 File name field.
>- Click Next. The next page of the wizard appears, as
>-shown below. <img src="../images/newmanualtest3.gif" /> </li>
>-<li>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 Finish to close the wizard. The Test
>-Suite 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.</li>
>-</ol>
>-</div>
>+<body>
> 
> <div>
>+
>+<h2>Creating a manual test</h2>
> 
>-Parent topic: <a href="../concepts/cmanualtestoverview.htm" title="">Manual testing with TPTP</a> 
>+This topic describes how to create a manual test suite.
>+
>+
>+<ol>
>+	<li>Click File &gt; New &gt; Other. The New dialog appears.</li>
>+	<li>Expand the Test folder, then select TPTP Manual Test.</li>
>+	<li>Click Next and name the the manual test, for example, exampleManualTest.</li>
>+	<li>Click Next and optionally provide a description for the manual test suite. Click Finish.</li>
>+	<li>A manual test testsuite file (exampleManualTest.testsuite) will be created and becomes visible in the Navigator.</li>
>+</ol>
>+
>+Related tasks 
>+<a href="tediting_manual_test.htm">Editing a manual test</a> 
>+<a href="trunningmanualtestsuite.htm">Running a manual test</a> 
> 
>-</div><div class="runningfooter">(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.</div>
>+
>+(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
>+
>+</div>
>+
> </body>
>-</html>
>\ No newline at end of file
>+
>+</html>
>Index: tasks/tediting_manual_test.htm
>===================================================================
>RCS file: /home/tptp/test/org.eclipse.hyades.test.doc.user/tasks/tediting_manual_test.htm,v
>retrieving revision 1.2
>diff -u -r1.2 tediting_manual_test.htm
>--- tasks/tediting_manual_test.htm	19 Sep 2005 14:34:42 -0000	1.2
>+++ tasks/tediting_manual_test.htm	28 Sep 2005 22:23:08 -0000
>@@ -5,15 +5,20 @@
> <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="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 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="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" />
>@@ -25,50 +30,67 @@
> <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>
>+<body id="editing_manual_test">
>+<a name="editing_manual_test"></a>
> 
> <h1 class="topictitle1">Editing a manual test</h1>
>-<div>This section describes how to edit your manual test suite.
>+<div>
>+This section describes how to edit your manual test suite.
> <div class="p">You must have created a manual test suite.</div>
>-<ol><li>In the Navigator double-click the test suite
>-entry to open the Test Suite dialog box as shown below.
>-The test suite opens in the Overview tab with the two
>-edit areas (General Information and Test
>-Cases) expanded. <img src="../images/manualtestsuite.gif" /> </li>
>-<li>The General Information 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.</li>
>-<li>The Test Cases area lists the individual
>-tests that make up the test suite. Click one of the test cases or More to
>-display the Test Cases view, as shown below. <img src="../images/manualtestcases.gif" /> To change the name or description of a test case, select
>-the test case and enter new text in the Name or Description boxes.
>-Use the Add and Remove buttons
>-to add test cases and to remove existing cases. Use the Up and Down buttons
>-to change the order of cases.</li>
>-<li>Click the Behaviors tab to display the Behaviors
>-view, as shown below. <img src="../images/manualbehaviors.gif" /> 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 above, <kbd class="userinput">test
>-1</kbd> runs inside <kbd class="userinput">Loop 1</kbd>. Use the Number
>-of Iterations box to specify how many times to execute the loop.
>-With Synchronous checked and more than one iteration
>-specified, the loop iterations execute in sequence. With Synchronous unchecked
>-and more than one iteration specified, the loop iterations execute simultaneously. </li>
>-<li>Use the Up and Down buttons
>-to change the order of invocations and loops. Use the Add and Remove 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 Add &gt; Invocation.
>-The Test Invocation dialog box, shown below, appears. <img src="../images/addinvocationmanual.gif" /> 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.</li>
>+<ol>
>+	<li>In the Test Navigator
>+	double-click the test suite entry to open the Test
>+	Suite dialog box. The test suite opens in the +		class="uicontrol">Overview tab with the two edit areas (+		class="uicontrol">General Information and +		class="uicontrol">Test Cases) expanded.</li>
>+	<li>The General Information 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.</li>
>+	<li>The Test Cases area lists the
>+	individual tests that make up the test suite. Click one of the test
>+	cases or More 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 Name or +		class="uicontrol">Description boxes. Use the +		class="uicontrol">Add and Remove
>+	buttons to add test cases and to remove existing cases. Use the +		class="uicontrol">Up and Down
>+	buttons to change the order of cases.</li>
>+	<li>Click the Behaviors 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" /> 
>+		 Use the +		class="uicontrol">Number of Iterations box to specify how many
>+	times to execute the loop. With Synchronous
>+	checked and more than one iteration specified, the loop iterations
>+	execute in sequence. With Synchronous
>+	unchecked and more than one iteration specified, the loop iterations
>+	execute simultaneously. </li>
>+	<li>Use the Up and +		class="uicontrol">Down buttons to change the order of
>+	invocations and loops. Use the Add and +		class="uicontrol">Remove 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 +		class="uicontrol">Add &gt; Invocation.
>+	The Test Invocation 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.</li>
> </ol>
> </div>
> 
>-<div>
>-
>-Parent topic: <a href="../concepts/cmanualtestoverview.htm" title="">Manual testing with TPTP</a> 
>+Related tasks 
>+<a href="tcreatingamanualtest.htm">Creating a manual test</a> 
>+<a href="trunningmanualtestsuite.htm">Running a manual test</a> 
> 
>-</div><div class="runningfooter">(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.</div>
>+
>+<div class="runningfooter">(C) Copyright IBM Corporation 2000, 2004. All
>+Rights Reserved.</div>
> </body>
>-</html>
>\ No newline at end of file
>+</html>
>Index: tasks/trunningmanualtestsuite.htm
>===================================================================
>RCS file: /home/tptp/test/org.eclipse.hyades.test.doc.user/tasks/trunningmanualtestsuite.htm,v
>retrieving revision 1.2
>diff -u -r1.2 trunningmanualtestsuite.htm
>--- tasks/trunningmanualtestsuite.htm	19 Sep 2005 14:34:42 -0000	1.2
>+++ tasks/trunningmanualtestsuite.htm	28 Sep 2005 22:23:08 -0000
>@@ -1,103 +1,32 @@
>-<?xml version="1.0" encoding="UTF-8"?>
>-<!DOCTYPE html
>- PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
>+<?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=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="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" />
>-
>-
>-
>-
>-<link rel="stylesheet" type="text/css" href="../css/ibmdita.css" />
>-<link rel="stylesheet" type="text/css" href="../css/swg_info_common.css" />
>+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"/>
>+<link rel=StyleSheet href="../css/book.css" type="text/css"/>
> <title>Running a manual test</title>
> </head>
>-<body id="runningamanualtestsuite"><a name="runningamanualtestsuite"></a>
> 
>-<h1 class="topictitle1">Running a manual test</h1>
>-<div>This topic describes how to create and run a manual test.
>-<div class="p">Before you can run a test, you must <a href="tcreating_test_deployment.htm#creatingatestdeployment">create a test deployment</a>. </div>
>-<div class="skipspace">To run a manual test:</div>
>-<ol><li class="skipspace">From the Test Navigator click Run &gt; Run. The Run dialog box opens. </li>
>-<li class="skipspace">In the Configurations pane on the left,
>-click Hyades Manual Test. <img src="../images/perspectiveMan.gif" alt=" " /> </li>
>-<li class="skipspace">Optionally, in the Perspectives tab, you can associate the Run
>-launch mode with a different workbench perspective by clicking the appropriate
>-arrow and selecting the perspective from the drop-down list.</li>
>-<li class="skipspace">To create a new configuration, click the New button
>-on the bottom left. A new test configuration, initially
>-named <kbd class="userinput">New_Configuration</kbd>, is created. Change the name
>-if you like. Alternatively, expand Hyades Manual Test and
>-click a listed configuration that you want to inspect or modify. The Run dialog
>-box opens in the Test tab. <img src="../images/manualDeploy.gif" alt=" " /> 
>-</li>
>-<li class="skipspace">In the Select Test to run pane in the middle
>-listing all projects in the workspace, navigate to the project containing
>-the test to run and click it.</li>
>-<li class="skipspace">In the Select a deployment pane on the right
>-listing all defined deployments in the workspace, click the one to use for
>-this run. To run the test using default values, or using the
>-same values that you set during the previous test run, you can click Run now
>-and stop reading.
>-</li>
>-<li class="skipspace">Click Apply to save the selections on this
>-tab.</li>
>-<li class="skipspace">Click Execution Results to display that
>-tab, as shown below. <img src="../images/manualconfig2.gif" /> </li>
>-<li class="skipspace">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 Override existing Execution Results resource.</li>
>-<li class="skipspace">In the Location box listing Java projects
>-in the workspace, click the one in which to store the test results.</li>
>-<li class="skipspace">Click Apply to save the selections on this
>-tab.</li>
>-<li class="skipspace">Click Common to display the Common tab,
>-as shown below. <img src="../images/manualconfig3.gif" /> </li>
>-<li class="skipspace">When you run a test configuration, Eclipse creates a file, with
>-a <kbd class="userinput">.launch</kbd> suffix, containing metadata. If you select Local,
>-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 Shared, click Browse,
>-and navigate to a folder in your workspace where you want to store the file. </li>
>-<li class="skipspace">To have the test configuration appear in the Run favorites
>-toolbar menu, check this item in the Display in favorites menu
>-box.</li>
>-<li class="skipspace">Select Launch in background to have Eclipse
>-run the test configuration in the background so that you can perform other
>-Eclipse tasks while the test runs. </li>
>-<li class="skipspace">Click Apply to save the settings for the
>-configuration. </li>
>-<li class="skipspace">Click Run. The Manual Remote Application
>-dialog box opens, as shown below. <img src="../images/manualtestremote.gif" /> </li>
>-<li class="skipspace">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 Status drop-down
>-list. Enter comments about the test results in the Info field. </li>
>-<li class="skipspace">Click Next to save the test results and
>-move to the next test.</li>
>-<li class="skipspace">When you finish running all tests, click End Execution to
>-close the dialog box.</li>
>+<body>
>+
>+<div>
>+
>+<h2>Running a manual test</h2>
>+This topic describes how to create and run a manual test.
>+<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>	
> </ol>
>+
>+
>+ 
>+(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
>+
> </div>
> 
>-<div>
>-
>-Parent topic: <a href="../concepts/cmanualtestoverview.htm" title="">Manual testing with TPTP</a> 
>-
>-</div><div class="runningfooter">(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.</div>
> </body>
>-</html>
>\ No newline at end of file
>+
>+</html>
>Index: tdeploy/tcreating_test_deployment_css.htm
>===================================================================
>RCS file: tdeploy/tcreating_test_deployment_css.htm
>diff -N tdeploy/tcreating_test_deployment_css.htm
>--- tdeploy/tcreating_test_deployment_css.htm	19 Sep 2005 14:34:43 -0000	1.3
>+++ /dev/null	1 Jan 1970 00:00:00 -0000
>@@ -1,280 +0,0 @@
>-<?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"/>
>-
>-
>-<title>Creating a test deployment</title>
>-<style>
>-
>-</style>
>-</head>
>-
>-<body link=blue vlink=blue>
>-
>-<div>
>-
>-<h1><a name=creatingatestdeployment></a>Creating a Test Deployment</h1>
>-
>-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.
>-
>-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.
>-
>-&nbsp;
>-
>-To create a test deployment:
>-
>-<h3>Step 1</h3>
>-
>-In
>-the Test Navigator select the test suite for which you want to create a
>-deployment. SelectÂ  File &gt; New &gt; Other. The New
>-wizard opens:
>-
>- 
>-
>-
>-<h3>Step 2</h3>
>-
>-Expand the Test folder and the Test Assets folder, then select Deployment.
>-Click Next. The next page of the wizard
>-opens: 
>-
>- 
>-
>-Navigate to the folder that will store the deployment file
>-resource. Enter a name for the deployment in the name
>-field. Click Next. The next page of the
>-wizard opens: 
>-
>-<h3>Step 3 </h3>
>-
>-
>-
>-(Optionally) enter a brief description for the deployment. Click
>-Next. The next page of the wizard opens:
>-
>-<h3>Step 4 </h3>
>-
>-
>-
>-(To create a deployment that consists of a location only,
>-click Next and skip ahead to Step 9).
>-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: 
>-
>-<h3>Step 5</h3>
>-
>-
>-
>-If you have previously defined one or more artifacts that
>-you want to use in this deployment, click Browse
>-and navigate to the artifact. After you select the artifact, click Finish. To define a new artifact check the Create a new resource button and click Next. The New Artifact wizard opens:
>-
>-<h3>Step 6</h3>
>-
>-
>-
>-Navigate to the folder that will store the artifact file
>-resource. Enter a name for the artifact file resource in the Name field. Click Next.
>-The next page of the wizard opens: 
>-
>-<h3>Step 7</h3>
>-
>-
>-
>- 
>-
>-(Optionally) enter a description for the artifact. Click Next. The next page of the wizard opens:
>-
>-<h3>Step 8</h3>
>-
>-Â  
>-
>-Click the boxes next to the test asset(s) that you want to
>-include in the artifact. Click Finish. The
>-new artifact appears in the list of artifacts to be added to the deployment:
>-
>-
>-
>- 
>- 
>-To add another artifact click Add and repeat the
>-steps. When you are satisfied with the list of artifacts, click Next. The next page of the wizard appears:
>-
>-<h3>Step 9 </h3>
>-
>-
>-
>-Click Add to select a
>-location to be associated with the deployment. The Add Location Association
>-dialog box opens, as above: 
>-
>-<h3>Step 10</h3>
>-
>-To select an existing location resource click Browse and navigate to the location. To create a
>-location, check the Create a new resource
>-button and click Next. The New Location
>-wizard opens: 
>-
>- 
>-
>-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 Next. The next
>-page of the wizard appears:
>-
>-<h3>Step 11 </h3>
>-
>-
>-
>-(Optionally)
>-enter a description for the location. Click Finish.
>-The new location appears in the list of locations to be added to the
>-deployment:
>-
>-Â 
>-
>- 
>- 
>-To add another location click Add and
>-repeat the steps. When you are satisfied with the list of locations to be added
>-to the deployment, click Next. The next
>-page of the wizard opens:
>-
>-<h3>Step 12 </h3>
>-
>-
>-
>-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.
>-
>-<h3>Viewing and Editing Artifacts, Locations, and Deployments </h3>
>-
>-To
>-view any of the entities you have created, double-click on it in the Navigator
>-View. For example, for the location sampleLocation:
>-
>-
>-
>-The
>-location's Overview tab opens, as
>-shown below.Â  The default host name for
>-the location is <kbd>localhost</kbd>.
>-If the location is for another computer, enter the name of that computer in the
>-Host name field. 
>-
>-Parent topic: <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>
>-
>-(C) Copyright IBM Corporation 2000, 2005. All Rights
>-Reserved.
>-
>-&nbsp;
>-
>-</div>
>-
>-</body>
>-
>-</html>
>Index: ref/refintro.html
>===================================================================
>RCS file: ref/refintro.html
>diff -N ref/refintro.html
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ ref/refintro.html	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,29 @@
>+<?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 
>+TPTP Tester guide 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>
>+
>+(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
>+
>+</div>
>+
>+</body>
>+
>+</html>
>Index: ref/rmanualcreate.htm
>===================================================================
>RCS file: ref/rmanualcreate.htm
>diff -N ref/rmanualcreate.htm
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ ref/rmanualcreate.htm	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,53 @@
>+<?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>
>+Eclipse provides the Common tab at the right of the Run dialog for editing various generic launch configuration properties. Select the Common 
>+tab at the right of the Run dialog to edit the following generic launch configuration properties:
>+
>+<ul>
>+	<li>When the launch configuration is saved by clicking Run at the bottom of the Run dialog, a 
>+launch configuration file (.launch) is created and saved. By default, the launch configuration file is saved in the workspace's .metadata 
>+directory. The location for the .launch file may be changed to any directory in the workspace via the Save as pane of the Common tab.</li>
>+	<li>When rerunning a launch configuration, a shortcut may be associated with one or more favorites tool bar menus in the Display in favorites menu 
>+	pane of the Common tab.</li>
>+	<li>When a launch configuration is executed by clicking Run at the bottom of the Run dialog, the Console view 
>+	is used for rendering standard output data and reading standard input data. By default, the encoding of the Console view is the encoding for the
>+	local platform. The encoding of the Console view may be changed to any valid encoding in the Console Encoding pane of the Common 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 Console 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 Standard Input and Output pane of the 
>+	Common 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 Launch
>+	in background check box at the bottom of the Common tab. .</li>
>+</ul>
>+
>+ 
>+
>+
>+Related concepts 
>+	<a href="../tasks/trunningmanualtestsuite.htm">Running a manual test</a> 
>+
>+ 
>+Related tasks 
>+ <a href="../tasks/tcreating_test_deployment.htm">Creating a test deployment</a> 
>+
>+
>+(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
>+
>+</div>
>+
>+</body>
>+
>+</html>
>Index: tasks/tcreatemanualtestconfiguration.htm
>===================================================================
>RCS file: tasks/tcreatemanualtestconfiguration.htm
>diff -N tasks/tcreatemanualtestconfiguration.htm
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ tasks/tcreatemanualtestconfiguration.htm	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,75 @@
>+<?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>
>+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.
>+
>+Open the Run dialog to create the test configuration. 
>+Right-click on a test suite file in the Test Navigator and select 
>+Run As &gt; Run from the pop-up menu. 
>+The Run dialog opens.
>+
>+Create the test configuration by selecting the Test entry from the list 
>+of launch Configurations and clicking New. The test configuration is created and 
>+by default is named New_configuration. You may edit the default name of the test configuration in the 
>+Name field at the top of the Run dialog.
>+
>+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 Test tab at the right of the Run dialog 
>+and complete the following steps:
>+
>+<ol>
>+	<li>Select the manual test to run. Navigate to and select the manual test in the 1. Select test to run pane of the Test tab.
>+	</li>
>+	<li>Select the deployment for running the manual test. Select the local_deployment deployment in the 2.
>+	Select a deployment pane of the Test tab.</li>
>+	<li>
>+	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 Test Logs tab at the
>+	right of the Run dialog and complete the following steps:
>+
>+	<ul>
>+			<li>Clear the Use defaults check box at the top of the Test Logs tab.</li>
>+			<li>Edit the default name of the generated test log in the Name field under the Use defaults check box.</li>
>+			<li>Select the Override existing test logs resource check box under the Name 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 Location pane at the bottom of the Test Logs tab.</li>
>+	</ul>
>+	</li>
>+	<li>Optionally edit the generic launch configuration properties</li>
>+	<li>Save the test configuration by clicking the Apply button at the bottom of the Run dialog.</li>
>+</ol>
>+
>+
>+
>+Related tasks 
>+ <a href="trunningmanualtestsuite.htm">Running a manual test</a> 
>+ <a href="tcreating_test_deployment.htm">Creating a test deployment</a> 
>+
>+
>+Related reference 
>+ <a href="../ref/rmanualcreate.htm">Generic launch configuration properties</a> 
>+
>+
>+(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
>+
>+</div>
>+
>+</body>
>+
>+</html>
>Index: tasks/tprereqmanualtestconfiguration.htm
>===================================================================
>RCS file: tasks/tprereqmanualtestconfiguration.htm
>diff -N tasks/tprereqmanualtestconfiguration.htm
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ tasks/tprereqmanualtestconfiguration.htm	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,46 @@
>+<?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>
>+
>+ 
>+
>+To prepare to run a manual test, complete the following steps:
>+
>+<ol>
>+	<li>Open the Test perspective. Select Window &gt; Open Perspective &gt; Other... &gt; Test &gt; OK.</li>
>+	<li>Launch the Agent Controller.</li>
>+	<li>Optionally create a test deployment.</li> 
>+</ol>
>+
>+ 
>+
>+Related concepts 
>+ <a href="../concepts/cmanualtestoverview.htm">Manual testing with TPTP - overview</a> 
>+
>+ 
>+Related tasks 
>+ <a href="trunningmanualtestsuite.htm">Running a manual test</a> 
>+ <a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/tasks/tworkwac.html">Working with the Agent Controller</a> 
>+ <a href="tcreating_test_deployment.htm">Creating a test deployment</a> 
>+
>+
>+(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
>+
>+</div>
>+
>+</body>
>+
>+</html>
>Index: tasks/trunmanualtest.htm
>===================================================================
>RCS file: tasks/trunmanualtest.htm
>diff -N tasks/trunmanualtest.htm
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ tasks/trunmanualtest.htm	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,73 @@
>+<?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>
>+
>+Run the test configuration by clicking the Run button at the bottom of the Run dialog.
>+
>+When a manual test is executed, the Manual Test View is launched on the host as specified in the test deployment associated 
>+with the execution test launch configuration. The Manual Test View is an independent Standard Widget Toolkit
>+window for executing a manual test. 
>+
>+The Manual Test View displays the manual test as a hierarchal tree at the left of the Manual Test View 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 View &gt; Expand node and View &gt; Collapse node, 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 Manual Test View. 
>+
>+
>+At any time during the execution of the manual test, the tester may record a message in the test log by selecting Action &gt; Send message.... The Manual Test View 
>+may be terminated at any time during the execution of the manual test by selecting File &gt; Exit.
>+
>+
>+When the Manual Test View initially appears, the tester may optionally capture contextual information on the execution of the manual test; for example, enter the tester's name. Select Start to begin executing the individual manual test cases in the manual test.
>+
>+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 Manual Test View. After completing the execution steps of the manual test case, 
>+input the status at the lower-right of the Manual Test View:
>+<ul>
>+	<li>verdict (pass, fail, error or inconclusive)</li>
>+	<li>reason (abort, did not complete, unknown, none or see description) </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>
>+
>+
>+To record the status and contextual information in the test log and advance to the next manual test case, select the 
>+Next button at the lower-right of the Manual Test View. At any time during the execution of the manual test, the tester may advance to the next 
>+manual test case by selecting View &gt; Select task to execute.... 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.
>+ 
>+When the manual test execution is complete, exit the Manual Test View by selecting File &gt; Exit.
>+
>+
>+
>+Related tasks 
>+<a href="tcreatingamanualtest.htm">Creating a manual test</a> 
>+<a href="trunningmanualtestsuite.htm">Running a manual test</a> 
>+<a href="tanalyzingmanualtestresults.htm">Analyzing manual test results</a> 
>+<a href="tcreating_test_deployment.htm">Creating a test deployment</a> 
>+<a href="http://www.eclipse.org/swt/">Standard Widget Toolkit</a> 
>+
>+Related reference 
>+<a href="../ref/rmanualcreate.htm">Generic launch configuration properties</a>
>+
>+
>+(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
>+
>+</div>
>+
>+</body>
>+
>+</html>

Actions: View | Diff

Attachments on bug 110436: 27475 | 27655