Download
Getting Started
Members
Projects
Community
Marketplace
Events
Planet Eclipse
Newsletter
Videos
Participate
Report a Bug
Forums
Mailing Lists
Wiki
IRC
How to Contribute
Working Groups
Automotive
Internet of Things
LocationTech
Long-Term Support
PolarSys
Science
OpenMDM
More
Community
Marketplace
Events
Planet Eclipse
Newsletter
Videos
Participate
Report a Bug
Forums
Mailing Lists
Wiki
IRC
How to Contribute
Working Groups
Automotive
Internet of Things
LocationTech
Long-Term Support
PolarSys
Science
OpenMDM
Toggle navigation
Bugzilla – Attachment 27655 Details for
Bug 110436
WI7: Provide product documentation updates for new Manual Test Client.
Home
|
New
|
Browse
|
Search
|
[?]
|
Reports
|
Requests
|
Help
|
Log In
[x]
|
Terms of Use
|
Copyright Agent
Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read
this important communication.
[patch]
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:
Updated doc based on Paul's doc and including many fixes for existing doc
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 @@ > <!-- GSA ADP Schedule Contract with IBM Corp. --> > <link rel="stylesheet" type="text/css" href="../css/ibmdita.css" /> > <link rel="stylesheet" type="text/css" href="../css/swg_info_common.css" /> >-<title>Manual testing with TPTP</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><p>A manual test describes a procedure that a human tester performs to verify > whether a feature is working. The Eclipse test and performance tools platform > (TPTP) supports assisted manual testing.</p> >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"/> >-<!--[if !mso]> >-<style> >-v\:* {behavior:url(#default#VML);} >-o\:* {behavior:url(#default#VML);} >-w\:* {behavior:url(#default#VML);} >-.shape {behavior:url(#default#VML);} >-</style> >-<![endif]--> >-<title>TPTP Manual Test</title> >-<style> >-<!-- >- >---> >-</style> >-</head> >- >-<body link=blue vlink=purple> >- >-<div> >- >-<div> >- >-<h1>TPTP Manual Test >-Deployment</h1> >- >-</div> >- >-<h2>Introduction</h2> >- >-<p>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.</p> >- >-<p> </p> >- >-<h2>Test Deployment, Artifacts, Locations</h2> >- >-<p>In the basic Manual Test tutorial we saw that test <b>artifacts</b> >-are objects like test suites and data pools; >-test <b>location</b>s identify the computer where the test suite is to >-be run; and a test <b>deployment</b> 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. </p> >- >-<p>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.</p> >- >-<h2>Deployment</h2> >- >-<p>To establish a deployment for the manual test suite, >-right-click on the test suite, then >-select <b>New/Other</b>, then <b>Test/Test Assets/Deployment</b>:</p> >- >-<p> </p> >- >-<p align=center><!--[if gte vml 1]><v:shapetype >- id="_x0000_t75" coordsize="21600,21600" o:spt="75" o:preferrelative="t" >- path="m@4@5l@4@11@9@11@9@5xe" filled="f" stroked="f"> >- <v:stroke joinstyle="miter"/> >- <v:formulas> >- <v:f eqn="if lineDrawn pixelLineWidth 0"/> >- <v:f eqn="sum @0 1 0"/> >- <v:f eqn="sum 0 0 @1"/> >- <v:f eqn="prod @2 1 2"/> >- <v:f eqn="prod @3 21600 pixelWidth"/> >- <v:f eqn="prod @3 21600 pixelHeight"/> >- <v:f eqn="sum @0 0 1"/> >- <v:f eqn="prod @6 1 2"/> >- <v:f eqn="prod @7 21600 pixelWidth"/> >- <v:f eqn="sum @8 21600 0"/> >- <v:f eqn="prod @7 21600 pixelHeight"/> >- <v:f eqn="sum @10 21600 0"/> >- </v:formulas> >- <v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect"/> >- <o:lock v:ext="edit" aspectratio="t"/> >-</v:shapetype><v:shape id="_x0000_i1025" type="#_x0000_t75" style='width:375pt; >- height:274.5pt'> >- <v:imagedata src="../images_manualtest/DeployExample_files/image001.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p align=center> </p> >- >-<p>Now click on <b>Next</b> and >-name the deployment <b>exampleManualTestDeploy</b> in the next dialog:</p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1026" type="#_x0000_t75" style='width:375pt;height:264.75pt'> >- <v:imagedata src="../images_manualtest/DeployExample_files/image003.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p> </p> >- >-<p>Click on <b>Next</b> again to (optionally) describe the >-deployment:</p> >- >-<p> </p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1027" type="#_x0000_t75" style='width:375pt;height:204.75pt'> >- <v:imagedata src="../images_manualtest/DeployExample_files/image005.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p> </p> >- >-<p>Selecting <b>Next</b> once more brings up the <b>Add</b> <b>Artifact >-Association</b> dialog. </p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1028" type="#_x0000_t75" style='width:328.5pt;height:239.25pt'> >- <v:imagedata src="../images_manualtest/DeployExample_files/image007.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p> </p> >- >-<p>Select 'Create a new resource' and click on <b>Next</b>.</p> >- >-<p> </p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1029" type="#_x0000_t75" style='width:328.5pt;height:276.75pt'> >- <v:imagedata src="../images_manualtest/DeployExample_files/image009.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p align=center> </p> >- >-<p>Identify the parent folder and name the artifact (<b>exampleManualTestArtifact</b>). >-Click on next to move on to the dialog that allows you to describe the >-artifact:</p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1030" type="#_x0000_t75" style='width:314.25pt;height:189.75pt'> >- <v:imagedata src="../images_manualtest/DeployExample_files/image011.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p> </p> >- >-<p>Clicking on Next allows the actual test element to be >-associated with the artifact to be specified:</p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1031" type="#_x0000_t75" style='width:314.25pt;height:228.75pt'> >- <v:imagedata src="../images_manualtest/DeployExample_files/image013.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p align=center> </p> >- >-<p>Click on <b>Finish</b>. The next dialog defines the >-artifact(s) to be added to the deployment:</p> >- >-<p> </p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1032" type="#_x0000_t75" style='width:354.75pt;height:219.75pt'> >- <v:imagedata src="../images_manualtest/DeployExample_files/image015.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p>We then go through an identical procedure in respect of >-location; firstly naming and locating the location:</p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1033" type="#_x0000_t75" style='width:328.5pt;height:300pt'> >- <v:imagedata src="../images_manualtest/DeployExample_files/image017.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p> </p> >- >-<p>Click on <b>Next </b>to bring up the location description >-dialog:</p> >- >-<p> </p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1034" type="#_x0000_t75" style='width:328.5pt;height:198pt'> >- <v:imagedata src="../images_manualtest/DeployExample_files/image019.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p> </p> >- >-<p>Clicking <b>Finish</b> results in the <b>Select Resource</b> >-dialog appearing:</p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1035" type="#_x0000_t75" style='width:328.5pt;height:228pt'> >- <v:imagedata src="../images_manualtest/DeployExample_files/image021.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p> </p> >- >-<p>And selecting <b>Finish</b> at this point produces the >-artifact to location mapping dialog:</p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1036" type="#_x0000_t75" style='width:375pt;height:233.25pt'> >- <v:imagedata src="../images_manualtest/DeployExample_files/image023.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p> </p> >- >-<p>Select the artifact and location entities and click on the >-down-arrow to create the requisite pairing; then click on <b>Finish</b>.</p> >- >-<h2>Viewing and Editing Deployments</h2> >- >-<p>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. </p> >- >-<h3>Artifacts</h3> >- >-<p>For example, double-clicking on the newly created artifact >-brings up the Artifact editor view:</p> >- >-<p> </p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1037" type="#_x0000_t75" style='width:473.25pt;height:270.75pt'> >- <v:imagedata src="../images_manualtest/DeployExample_files/image025.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p> </p> >- >-<p>The Test Assets tab shows the assets associated with the >-artifact and allows them to be modified:</p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1038" type="#_x0000_t75" style='width:221.25pt;height:2in'> >- <v:imagedata src="../images_manualtest/DeployExample_files/image027.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p> </p> >- >-<h3>Locations</h3> >- >-<p>Similarly, double-clicking on the location file displays >-the Location editor view:</p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1039" type="#_x0000_t75" style='width:509.25pt;height:303.75pt'> >- <v:imagedata src="../images_manualtest/DeployExample_files/image029.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p>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.</p> >- >-<h3>Deployments</h3> >- >-<p>Double-clicking on the deploy_statcon_test file displays >-the Deployment editor view:</p> >- >-<p> </p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1040" type="#_x0000_t75" style='width:509.25pt;height:299.25pt'> >- <v:imagedata src="../images_manualtest/DeployExample_files/image031.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p> </p> >- >-<p>Switching to the Pairs tab allows artifacts/locations to >-be added and new pairings created:</p> >- >-<p><!--[if gte vml 1]><v:shape id="_x0000_i1041" type="#_x0000_t75" >- style='width:509.25pt;height:299.25pt'> >- <v:imagedata src="../images_manualtest/DeployExample_files/image033.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p> </p> >- >-<p>(C) Copyright IBM Corporation 2000, 2005. All Rights >-Reserved.</p> >- >-<p> </p> >- >-</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"/> >-<!--[if !mso]> >-<style> >-v\:* {behavior:url(#default#VML);} >-o\:* {behavior:url(#default#VML);} >-w\:* {behavior:url(#default#VML);} >-.shape {behavior:url(#default#VML);} >-</style> >-<![endif]--> >-<title>TPTP Manual Test</title> >-<style> >-<!-- >- >---> >-</style> >-</head> >- >-<body link=blue vlink=purple> >- >-<div> >- >-<h2>Analysis </h2> >- >-<p>The results are placed in Test Log files of type <b>.execution</b> >-in the project folder. Double-clicking on the <b>exampleManualTest_x.execution</b> >-file (or right-clicking on it and selecting <b>Open</b>) brings up the <b>Execution</b> >-view, below, with the <b>Overview</b> tab selected by default.</p> >- >-<p align=center><!--[if gte vml 1]><v:shapetype id="_x0000_t75" >- coordsize="21600,21600" o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe" >- filled="f" stroked="f"> >- <v:stroke joinstyle="miter"/> >- <v:formulas> >- <v:f eqn="if lineDrawn pixelLineWidth 0"/> >- <v:f eqn="sum @0 1 0"/> >- <v:f eqn="sum 0 0 @1"/> >- <v:f eqn="prod @2 1 2"/> >- <v:f eqn="prod @3 21600 pixelWidth"/> >- <v:f eqn="prod @3 21600 pixelHeight"/> >- <v:f eqn="sum @0 0 1"/> >- <v:f eqn="prod @6 1 2"/> >- <v:f eqn="prod @7 21600 pixelWidth"/> >- <v:f eqn="sum @8 21600 0"/> >- <v:f eqn="prod @7 21600 pixelHeight"/> >- <v:f eqn="sum @10 21600 0"/> >- </v:formulas> >- <v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect"/> >- <o:lock v:ext="edit" aspectratio="t"/> >-</v:shapetype><v:shape id="_x0000_i1025" type="#_x0000_t75" style='width:460.5pt; >- height:222pt'> >- <v:imagedata src="../images_manualtest/analysis_files/image001.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p><br/><br/></p> >- >-<h3>Overview Tab</h3> >- >-<p>In the General Information section, the Overview tab >-provides the Name of the manual test and its Description (if provided). It also >-gives the path to the execution file: </p> >- >-<p>/manualTests/exampleManualTest_x.execution </p> >- >-<p>in this case.</p> >- >-<p>The link <u>Go to first fail</u> switches to the Events >-tab and position the Test Log at the first recorded failure in the >-test.</p> >- >-<p>The Summary section gives: the <b>Type</b> (Manual Test), >-the <b>File</b> (/manualTests/exampleManualTest), the <b>Host name</b> >-(localhost) the <b>Verdict</b> 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.</p> >- >-<h3>Events Tab</h3> >- >-<p>Select the <b>Events</b> tab to see the test suite >-execution record:</p> >- >-<p align=center><br/> >-<!--[if gte vml 1]><v:shape id="_x0000_i1026" type="#_x0000_t75" style='width:462pt; >- height:224.25pt'> >- <v:imagedata src="../images_manualtest/analysis_files/image003.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p> </p> >- >-<p>The left-hand (<b>Events</b>) pane contains a graphical, >-tree-structure representation of the Test Log, and the right-hand (<b>Common >-Properties</b>) pane contains information about the particular node that is >-selected within the Test Log.</p> >- >-<p>The execution tree-structure is a <b>chronological</b> >-sequence of event nodes:</p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1027" type="#_x0000_t75" style='width:81.75pt;height:162pt'> >- <v:imagedata src="../images_manualtest/analysis_files/image005.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p> </p> >- >-<p>With the following interpretation:</p> >- >-<div align=center> >- >-<table border=1 cellspacing=0 cellpadding=0> >- <tr> >- <td width=103 valign=top> >- <p><b>Node >- Type</b></p> >- </td> >- <td width=384 valign=top> >- <p><b>Meaning</b></p> >- </td> >- </tr> >- <tr> >- <td width=103 valign=top> >- <p>start</p> >- </td> >- <td width=384 valign=top> >- <p>Indicates >- the start of some process (e.g. invocation); provides time:</p> >- <p> </p> >- <p><!--[if gte vml 1]><v:shape >- id="_x0000_i1028" type="#_x0000_t75" style='width:130.5pt;height:141pt'> >- <v:imagedata src="../images_manualtest/analysis_files/image007.png" o:title=""/> >- </v:shape><![endif]--></p> >- </td> >- </tr> >- <tr> >- <td width=103 valign=top> >- <p>stop</p> >- </td> >- <td width=384 valign=top> >- <p>Indicates >- the end of some process (e.g. invocation); provides time. Exactly as for <b>start</b> >- node except that the node type is <b>stop</b>.</p> >- </td> >- </tr> >- <tr> >- <td width=103 valign=top> >- <p>invocation</p> >- </td> >- <td width=384 valign=top> >- <p>Corresponds >- to a test case invocation; expands to show underlying node structure:</p> >- <p> </p> >- <p align=center><!--[if gte vml 1]><v:shape id="_x0000_i1029" >- type="#_x0000_t75" style='width:111pt;height:63pt'> >- <v:imagedata src="../images_manualtest/analysis_files/image009.png" o:title=""/> >- </v:shape><![endif]--></p> >- <p> </p> >- <p>In which >- the start/stop nodes are as above while the pass node indicates that the >- particular invocation involved passed the tester's criteria.</p> >- <p> </p> >- <p>The >- invocation outcome node (coded as pass, failed, error, inconclusive) lies between >- the start/stop nodes:</p> >- <p> </p> >- <p><!--[if gte vml 1]><v:shape >- id="_x0000_i1030" type="#_x0000_t75" style='width:127.5pt;height:198pt'> >- <v:imagedata src="../images_manualtest/analysis_files/image011.png" o:title=""/> >- </v:shape><![endif]--></p> >- <p> </p> >- </td> >- </tr> >- <tr> >- <td width=103 valign=top> >- <p>message</p> >- </td> >- <td width=384 valign=top> >- <p>Provides >- information about a stage in the manual test; normally one at the beginning >- and end of a test.</p> >- <p> </p> >- <p><!--[if gte vml 1]><v:shape >- id="_x0000_i1031" type="#_x0000_t75" style='width:126pt;height:138pt'> >- <v:imagedata src="../images_manualtest/analysis_files/image013.png" o:title=""/> >- </v:shape><![endif]--></p> >- </td> >- </tr> >-</table> >- >-</div> >- >-<p> </p> >- >-<p>The <b><u>P</u>revious fail</b> and <b><u>N</u>ext fail</b> >-buttons move the focus within the history backwards (chronologically) and >-forwards (chronologically) respectively to the next failure node.</p> >- >-<p>Click on an event node in the <b>Events</b> pane to get >-information about that event in the right-hand pane.</p> >- >-<p>In the case below, an <!--[if gte vml 1]><v:shape id="_x0000_i1032" >- type="#_x0000_t75" style='width:45.75pt;height:12pt'> >- <v:imagedata src="../images_manualtest/analysis_files/image015.png" o:title=""/> >-</v:shape><![endif]--> event node has been selected and the >-information displayed as follows:</p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1033" type="#_x0000_t75" style='width:140.25pt;height:198.75pt'> >- <v:imagedata src="../images_manualtest/analysis_files/image017.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p> </p> >- >-<p>(C) Copyright IBM Corporation 2000, 2005. All Rights >-Reserved.</p> >- >-</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"/> >-<!--[if !mso]> >-<style> >-v\:* {behavior:url(#default#VML);} >-o\:* {behavior:url(#default#VML);} >-w\:* {behavior:url(#default#VML);} >-.shape {behavior:url(#default#VML);} >-</style> >-<![endif]--> >-<title>TPTP Manual Test</title> >-<style> >-<!-- >- >---> >-</style> >-</head> >- >-<body link=blue vlink=purple> >- >-<div> >- >-<h2>Building a Manual Test</h2> >- >-<h3>Create a new manual test suite</h3> >- >-<p>Right-click in the Navigator view and select <b>New/Other</b>:</p> >- >-<p> </p> >- >-<p align=center><!--[if gte vml 1]><v:shapetype >- id="_x0000_t75" coordsize="21600,21600" o:spt="75" o:preferrelative="t" >- path="m@4@5l@4@11@9@11@9@5xe" filled="f" stroked="f"> >- <v:stroke joinstyle="miter"/> >- <v:formulas> >- <v:f eqn="if lineDrawn pixelLineWidth 0"/> >- <v:f eqn="sum @0 1 0"/> >- <v:f eqn="sum 0 0 @1"/> >- <v:f eqn="prod @2 1 2"/> >- <v:f eqn="prod @3 21600 pixelWidth"/> >- <v:f eqn="prod @3 21600 pixelHeight"/> >- <v:f eqn="sum @0 0 1"/> >- <v:f eqn="prod @6 1 2"/> >- <v:f eqn="prod @7 21600 pixelWidth"/> >- <v:f eqn="sum @8 21600 0"/> >- <v:f eqn="prod @7 21600 pixelHeight"/> >- <v:f eqn="sum @10 21600 0"/> >- </v:formulas> >- <v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect"/> >- <o:lock v:ext="edit" aspectratio="t"/> >-</v:shapetype><v:shape id="_x0000_i1025" type="#_x0000_t75" style='width:246.75pt; >- height:106.5pt'> >- <v:imagedata src="../images_manualtest/building_files/image001.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p align=center> </p> >- >-<p>Then select <b>Test/TPTP Manual Test</b> from the >-resulting <b>New</b> dialog:</p> >- >-<p> </p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1026" type="#_x0000_t75" style='width:303.75pt;height:321pt'> >- <v:imagedata src="../images_manualtest/building_files/image003.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p><b> </b></p> >- >-<p>Now click on <b>Next</b> and name the the manual test in (<b>exampleManualTest</b>):</p> >- >-<p> </p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1027" type="#_x0000_t75" style='width:282.75pt;height:303.75pt'> >- <v:imagedata src="../images_manualtest/building_files/image005.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p><b> </b></p> >- >-<p>Then click on <b>Next</b> and (optionally) provide a >-description for the manual test suite and click on <b>Finish</b>:</p> >- >-<p align=center><b><!--[if gte vml 1]><v:shape >- id="_x0000_i1028" type="#_x0000_t75" style='width:272.25pt;height:207pt'> >- <v:imagedata src="../images_manualtest/building_files/image007.png" o:title=""/> >-</v:shape><![endif]--></b></p> >- >-<p> </p> >- >-<p>A manual test testsuite file (<b>exampleManualTest.testsuite</b>) >-will be created and becomes visible in the Navigator view:</p> >- >-<p> </p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1029" type="#_x0000_t75" style='width:185.25pt;height:84pt'> >- <v:imagedata src="../images_manualtest/building_files/image009.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p> </p> >- >-<p>(C) Copyright IBM Corporation 2000, 2005. All Rights >-Reserved.</p> >- >-</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"/> >-<!--[if !mso]> >-<style> >-v\:* {behavior:url(#default#VML);} >-o\:* {behavior:url(#default#VML);} >-w\:* {behavior:url(#default#VML);} >-.shape {behavior:url(#default#VML);} >-</style> >-<![endif]--> >-<title>TPTP Manual Test</title> >-<style> >-<!-- >- >---> >-</style> >-</head> >- >-<body link=blue vlink=purple> >- >-<div> >- >-<h2>TPTP Manual Test Suite Editor</h2> >- >-<p>We now need to utilise the TPTP Manual TestSuite Editor. <i>Either</i> >-double-click on the <b>exampleManualTest.testsuite</b> file <i>or</i> >-right-click on it and select <b>Open</b> from the resultant popup menu. Either >-way, the <b>TPTP Manual Test</b> editor is invoked:</p> >- >-<h3> </h3> >- >-<p align=center><!--[if gte vml 1]><v:shapetype >- id="_x0000_t75" coordsize="21600,21600" o:spt="75" o:preferrelative="t" >- path="m@4@5l@4@11@9@11@9@5xe" filled="f" stroked="f"> >- <v:stroke joinstyle="miter"/> >- <v:formulas> >- <v:f eqn="if lineDrawn pixelLineWidth 0"/> >- <v:f eqn="sum @0 1 0"/> >- <v:f eqn="sum 0 0 @1"/> >- <v:f eqn="prod @2 1 2"/> >- <v:f eqn="prod @3 21600 pixelWidth"/> >- <v:f eqn="prod @3 21600 pixelHeight"/> >- <v:f eqn="sum @0 0 1"/> >- <v:f eqn="prod @6 1 2"/> >- <v:f eqn="prod @7 21600 pixelWidth"/> >- <v:f eqn="sum @8 21600 0"/> >- <v:f eqn="prod @7 21600 pixelHeight"/> >- <v:f eqn="sum @10 21600 0"/> >- </v:formulas> >- <v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect"/> >- <o:lock v:ext="edit" aspectratio="t"/> >-</v:shapetype><v:shape id="_x0000_i1025" type="#_x0000_t75" style='width:450pt; >- height:246pt'> >- <v:imagedata src="../images_manualtest/editor_files/image001.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p>There are are 3 tab controls located at the bottom of the >-editor pane: <b>Overview</b>, <b>Test Cases</b>, and <b>Behavior</b>. We now >-look at each of these in turn:</p> >- >-<h3>Overview Tab</h3> >- >-<p>The <b>Overview Tab</b> contains:</p> >- >-<p>the <i>Name</i> of the manual test; </p> >- >-<p>a <i>description</i> (optional) of it; </p> >- >-<p>a test type (TPTP Manual Test); and </p> >- >-<p>the path referencing the file containing the Test Suite >-(/manualTests/exampleManualTest.testsuite).</p> >- >-<p>If there are any existing TestCases, their names will be >-displayed in the right-hand pane of the editor.</p> >- >-<p>To switch to the Test Cases view, either select the <b>Test >-Cases</b> tab or click on the <b><u>M</u>ore...</b> button.</p> >- >-<h3>Test Cases Tab</h3> >- >-<p>The <b>Test Cases</b> section lists the individual tests >-that will make up the test suite. </p> >- >-<p><!--[if gte vml 1]><v:shape id="_x0000_i1026" type="#_x0000_t75" >- style='width:510pt;height:252pt'> >- <v:imagedata src="../images_manualtest/editor_files/image003.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p>To alter a test case <b>name</b>, select the test case (in >-the left-hand pane) then edit the <b>Name</b> textbox. To alter a test case <b>description</b>, >-select the test case then edit the <b>Description</b> 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. </p> >- >-<h3>Behavior Tab</h3> >- >-<p>The behavior tab allows you to specify the frequency and >-order in which test cases are run. This is done via <i>invocations</i> and <i>loops</i>: >-<b>invocations </b>allow you to specify which test cases you wish to run, and >-in which order; <b>loops</b> 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.</p> >- >-<p>For our (simple) example, we want to run all of the test >-cases within a single loop iteration. To set up a single loop:</p> >- >-<p>Select the <b>Behavior</b> tab, click on the <b><u>A</u>dd...</b> >-button and select <b>Loop</b>:</p> >- >-<p> </p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1027" type="#_x0000_t75" style='width:376.5pt;height:129.75pt'> >- <v:imagedata src="../images_manualtest/editor_files/image005.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p>This will setup a behavior under the control of a single >-loop. We shall add the test cases to this loop shortly.</p> >- >-<p>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. </p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1028" type="#_x0000_t75" style='width:375pt;height:178.5pt'> >- <v:imagedata src="../images_manualtest/editor_files/image007.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p>If S<u>y</u>nchronous >-is checked and more than one iteration is specified, the loop iterations >-execute sequentially. If S<u>y</u>nchronous is unchecked and more than one >-iteration specified, the loop iterations execute concurrently. </p> >- >-<p>The <b><u>U</u>p</b> and <b><u>D</u>own</b> buttons are >-used to alter the relative positions of invocations and loops. The <b><u>A</u>dd</b> >-and <b><u>R</u>emove</b> buttons are used to add/remove selected >-loops/invocations.</p> >- >-<p>Loops can be nested, and invocations can exist outside of >-a loop.</p> >- >-<p>Now let's proceed to build our example Manual Test. We >-start with the Test Cases tab:</p> >- >-<h3>Test Cases Tab</h3> >- >-<p>Select the <b>Test Cases</b> tab and click on the <b><u>A</u>dd...</b> >-button. This will cause the test case called 'test 1' to be created:</p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1029" type="#_x0000_t75" style='width:375pt;height:132pt'> >- <v:imagedata src="../images_manualtest/editor_files/image009.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p> </p> >- >-<p> </p> >- >-<p>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</p> >- >-<p>Replace the Name 'test 1' by 'Instruction Set A' (Simply >-edit the <i>Name</i> field). You can (optionally) put some descriptive text in >-the <i>Description</i> field.</p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1030" type="#_x0000_t75" style='width:487.5pt;height:83.25pt'> >- <v:imagedata src="../images_manualtest/editor_files/image011.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p>Now click on the <b><u>A</u>dd...</b> 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.</p> >- >-<p>The <b>Test Cases</b> tab view will now look like:</p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1031" type="#_x0000_t75" style='width:484.5pt;height:100.5pt'> >- <v:imagedata src="../images_manualtest/editor_files/image013.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p> </p> >- >-<p>The <b><u>A</u>dd</b> and <b><u>R</u>emove</b> buttons are >-used to add and delete test cases, while the <b><u>U</u>p</b> and <b><u>D</u>own</b> >-buttons are used to change the relative positions of selected test cases within >-the overall list.</p> >- >-<h3>Behavior Tab</h3> >- >-<p>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 <b>Behavior</b> tab, click on the <b><u>A</u>dd...</b> button, >-select <b>invocation</b>, and then select <i>all</i> of the test cases on display >-(use <ctrl>click on each):</p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1032" type="#_x0000_t75" style='width:268.5pt;height:315.75pt'> >- <v:imagedata src="../images_manualtest/editor_files/image015.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p> </p> >- >-<p>(C) Copyright IBM Corporation 2000, 2005. All Rights >-Reserved.</p> >- >-</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> >- >-<p>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.</p> >- >-<p>Before embarking on this, however, we explain some >-background terminology that will crop up as we build the test.</p> >- >-<h2>Terminology: Test Deployment, Artifacts, Locations</h2> >- >-<p>Test <b>artifacts</b> are objects like test suites and >-data pools. Test <b>location</b>s identify the computer where the test suite is >-to be run. A test <b>deployment</b> 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. </p> >- >-<p>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.</p> >- >-<h2>The Example Manual Test Case</h2> >- >-<p>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: </p> >- >-<p>1. >-Instruction Set A</p> >- >-<p>2. >-Instruction Set B</p> >- >-<p>3. >-Instruction Set C</p> >- >-<p>4. >-Instruction Set D</p> >- >-<p>5. >-Instruction Set E</p> >- >-<p>6. >-Instruction Set F</p> >- >-<p> </p> >- >-<p>and we want these to be issued in sequence, one after the >-other.</p> >- >-<p>To build the manual test we need to progress through a >-series of stages, as follows:</p> >- >-<p><b> </b></p> >- >-<p>(C) Copyright IBM Corporation 2000, 2005. All Rights >-Reserved.</p> >- >-</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"/> >-<!--[if !mso]> >-<style> >-v\:* {behavior:url(#default#VML);} >-o\:* {behavior:url(#default#VML);} >-w\:* {behavior:url(#default#VML);} >-.shape {behavior:url(#default#VML);} >-</style> >-<![endif]--> >-<title>TPTP Manual Test</title> >-<style> >-<!-- >- >---> >-</style> >-</head> >- >-<body link=blue vlink=purple> >- >-<div> >- >-<h2>Preparing to Run the Manual Test</h2> >- >-<h3>Test Perspective</h3> >- >-<p>Switch to the <b>Test</b> perspective. Select <b>Window/Open >-Perspective/Other</b>:</p> >- >-<p align=center><!--[if gte vml 1]><v:shapetype >- id="_x0000_t75" coordsize="21600,21600" o:spt="75" o:preferrelative="t" >- path="m@4@5l@4@11@9@11@9@5xe" filled="f" stroked="f"> >- <v:stroke joinstyle="miter"/> >- <v:formulas> >- <v:f eqn="if lineDrawn pixelLineWidth 0"/> >- <v:f eqn="sum @0 1 0"/> >- <v:f eqn="sum 0 0 @1"/> >- <v:f eqn="prod @2 1 2"/> >- <v:f eqn="prod @3 21600 pixelWidth"/> >- <v:f eqn="prod @3 21600 pixelHeight"/> >- <v:f eqn="sum @0 0 1"/> >- <v:f eqn="prod @6 1 2"/> >- <v:f eqn="prod @7 21600 pixelWidth"/> >- <v:f eqn="sum @8 21600 0"/> >- <v:f eqn="prod @7 21600 pixelHeight"/> >- <v:f eqn="sum @10 21600 0"/> >- </v:formulas> >- <v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect"/> >- <o:lock v:ext="edit" aspectratio="t"/> >-</v:shapetype><v:shape id="_x0000_i1025" type="#_x0000_t75" style='width:153.75pt; >- height:224.25pt'> >- <v:imagedata src="../images_manualtest/run_files/image001.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p>Then select <b>Test</b> and click on <b>OK</b>.</p> >- >-<h3>Launch the Agent Controller</h3> >- >-<p>If the Agent Controller has not been launched previously, >-launch it now.</p> >- >-<h3>Running a Test</h3> >- >-<p>Right-click on the <b>exampleManualTest</b> test suite >-file and select <b>Run</b> from the popup menu. This will bring up the <b>Run</b> >-dialog:</p> >- >-<p><!--[if gte vml 1]><v:shape id="_x0000_i1026" type="#_x0000_t75" >- style='width:510pt;height:294pt'> >- <v:imagedata src="../images_manualtest/run_files/image003.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p> </p> >- >-<p> </p> >- >-<p align=center> </p> >- >-<p>Now click on <b>New</b> to display the configuration >-dialog, and enter (say) <b>test_config</b>. Then click on <b>exampleManualTest</b> >-in the 'Select Test to run' pane of the <b>Test</b> tab, and on <b>local_deployment</b> >-in the 'Select a Deployment' pane, then click on <b>Apply</b>.</p> >- >-<p> </p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1027" type="#_x0000_t75" style='width:282.75pt;height:122.25pt'> >- <v:imagedata src="../images_manualtest/run_files/image005.gif" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p align=center><b> </b></p> >- >-<p><b> </b></p> >- >-<p>The <b>Test Logs</b> tab allows you to override the log >-defaults if you wish.</p> >- >-<p> </p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1028" type="#_x0000_t75" style='width:244.5pt;height:127.5pt'> >- <v:imagedata src="../images_manualtest/run_files/image006.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p> </p> >- >-<p>Clicking on the <b>Common</b> tab displays:</p> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1029" type="#_x0000_t75" style='width:356.25pt;height:248.25pt'> >- <v:imagedata src="../images_manualtest/run_files/image008.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p align=center> </p> >- >-<p> </p> >- >-<p>When a test configuration is run, Eclipse creates a file, >-with a <kbd><b>.launch</b></kbd> >-suffix, containing metadata. The various parameter settings are interpreted as >-follows:</p> >- >-<table border=1 cellspacing=0 cellpadding=0> >- <tr> >- <td width=115 valign=top> >- <p><b>Parameter</b></p> >- </td> >- <td width=579 valign=top> >- <p><b>Meaning</b></p> >- </td> >- </tr> >- <tr> >- <td width=115 valign=top> >- <p>Type of launch configuration:</p> >- </td> >- <td width=579 valign=top> >- <p>Local: Eclipse >- stores the .launch file in your workspace's metadata folder, which is >- invisible to other users.</p> >- <p><b>Shared</b>: 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</p> >- </td> >- </tr> >- <tr> >- <td width=115 valign=top> >- <p>Display in favorites menu:</p> >- </td> >- <td width=579 valign=top> >- <p>To have the test configuration appear in the Run, Debug, >- or Profile favorites toolbar menus, check the >- appropriate check box in the displayed list.</p> >- </td> >- </tr> >- <tr> >- <td width=115 valign=top> >- <p>Launch in background</p> >- </td> >- <td width=579 valign=top> >- <p>If checked, then Eclipse will run the test configuration >- in the background. If the test configuration is <i>not</i> run in the >- background, then nothing can be done in Eclipse until it finishes running the >- test configuration. </p> >- </td> >- </tr> >-</table> >- >-<p> </p> >- >-<p>Click Apply to save the >-settings for the configuration. </p> >- >-<h3>Run the Manual Test</h3> >- >-<p>Now run the manual test by clicking on the <b>Run</b> button. >-This will display the <b>Manual TestCase</b> runtime window:</p> >- >-<p align=center><b><!--[if gte vml 1]><v:shape >- id="_x0000_i1030" type="#_x0000_t75" style='width:510pt;height:340.5pt'> >- <v:imagedata src="../images_manualtest/run_files/image010.png" o:title=""/> >-</v:shape><![endif]--></b></p> >- >-<p> </p> >- >-<p>In the <b>exampleManualTest</b>, the first test case >-(Instruction Set A) is automatically selected. The <b>Name</b> and <b>Description</b> >-of the test will then be displayed in the right-hand pane. When the tester has >-carried out the actions in the <b>Description</b>, they record the outcome (<b>pass</b>; >-<b>failed</b>; returned an <b>error</b>; or was <b>inconclusive</b>) by >-selecting an appropriate value in the Status >-drop-down list. They can also enter notes about the test outcomes in the Info field. </p> >- >-<p>Click Next to save the test >-results and move to the next test. </p> >- >-<p>When the tester has completed the set of tests, they should >-click on the End Execution button to close the >-manual test window: </p> >- >-<p> </p> >- >-<p><!--[if gte vml 1]><v:shape id="_x0000_i1031" type="#_x0000_t75" >- style='width:510pt;height:339.75pt'> >- <v:imagedata src="../images_manualtest/run_files/image012.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p><b> </b></p> >- >-<p>(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.</p> >- >-</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" /> >-<!-- All rights reserved. Licensed Materials Property of IBM --> >-<!-- US Government Users Restricted Rights --> >-<!-- Use, duplication or disclosure restricted by --> >-<!-- GSA ADP Schedule Contract with IBM Corp. --> >-<link rel="stylesheet" type="text/css" href="../css/ibmdita.css" /> >-<link rel="stylesheet" type="text/css" href="../css/swg_info_common.css" /> >+<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><p>This topic describes how to analyze results produced from running >-manual tests.</p> >-<p>After you run a manual test suite, the results appear in the Test Navigator, >-as shown below. <br /><img src="../images/manualtestresults.gif" /><br /></p> >-<p>Double-click the results entry to open the <span class="uicontrol">Overview</span> tab >-of the Execution dialog box, as shown below. <br /><img src="../images/manualtestresults2.gif" /><br /></p> >-<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><span class="uicontrol">pass</span></li> >-<li><span class="uicontrol">fail</span></li> >-<li><span class="uicontrol">inconclusive</span></li> >-<li><span class="uicontrol">error</span> (meaning that the test itself >-contains an error)</li> >-</ul> >+<body> >+ >+<div> >+ >+<h2>Analyzing manual test results</h2> >+ >+<p>The results of a test run are recorded in Test Log files of type <b>.execution</b> >+in the project folder. Double-click on the .execution >+file to launch the <b>Execution</b> >+view. The <b>Overview</b> tab is selected by default.</p> >+ >+<h3>Overview Tab</h3> >+ >+<p>In the General Information section, the Overview tab >+provides the Name of the manual test and its Description (if provided). It also >+gives the path to the execution file, for example: </p> >+ >+<p>/manualTests/exampleManualTest_x.execution</p> >+ >+<p>The link <b>Go to first fail</b> switches to the Events >+tab and positions the Test Log at the first recorded failure in the >+test.</p> >+ >+The Summary section reports the properties of the manual test: >+<ol> >+ <li><b>Type</b> (Manual Test)</li> >+ <li><b>File</b></li> >+ <li><b>Host name</b> (localhost)</li> >+ <li><b>Verdict</b></li> >+ <li>Start and Finish times</li> >+</ol> >+ >+The verdict is either pass, fail, inconclusive, or error. >+error indicates an error within the manual test itself rather than an >+error in the software being tested. >+ >+<h3>Events Tab</h3> >+ >+<p>Select the <b>Events</b> tab to see the test suite >+execution record.</p> >+ >+<p>The left-hand (<b>Events</b>) pane contains a graphical, >+tree-structure representation of the Test Log, and the right-hand (<b>Common >+Properties</b>) pane contains information about the particular node that is >+selected within the Test Log.</p> >+ >+<p>The execution tree-structure is a <b>chronological</b> >+sequence of event nodes:</p> >+ >+<div align=center> >+ >+<table border=1 cellspacing=0 cellpadding=0> >+ <tr> >+ <td width=103 valign=top> >+ <p><b>Node >+ Type</b></p> >+ </td> >+ <td width=384 valign=top> >+ <p><b>Meaning</b></p> >+ </td> >+ </tr> >+ <tr> >+ <td width=103 valign=top> >+ <p>start</p> >+ </td> >+ <td width=384 valign=top> >+ <p>Indicates >+ the start of some process (e.g. invocation); provides time.</p> >+ </td> >+ </tr> >+ <tr> >+ <td width=103 valign=top> >+ <p>stop</p> >+ </td> >+ <td width=384 valign=top> >+ <p>Indicates >+ the end of some process (e.g. invocation); provides time. Exactly as for <b>start</b> >+ node except that the node type is <b>stop</b>.</p> >+ </td> >+ </tr> >+ <tr> >+ <td width=103 valign=top> >+ <p>invocation</p> >+ </td> >+ <td width=384 valign=top> >+ <p>Corresponds >+ to a test case invocation; expands to show underlying node structure.</p> >+ <p>In which >+ the start/stop nodes are as above while the pass node indicates that the >+ particular invocation involved passed the tester's criteria.</p> >+ <p> </p> >+ <p>The >+ invocation outcome node (coded as pass, failed, error, inconclusive) lies between >+ the start/stop nodes:</p> >+ </td> >+ </tr> >+ <tr> >+ <td width=103 valign=top> >+ <p>message</p> >+ </td> >+ <td width=384 valign=top> >+ <p>Provides >+ information about a stage in the manual test; normally one at the beginning >+ and end of a test.</p> >+ </td> >+ </tr> >+</table> >+ > </div> >-<p>To view the details of the test suite execution, click the <span class="uicontrol">Events</span> tab. >-The <span class="uicontrol">Events</span> tab opens, as shown below. <br /><img src="../images/manualtestresults3.gif" /><br /></p> >-<p>Navigate to an event in the left pane to see details about that event in >-the fields on the right. </p> >+ >+<p>The <b>Previous fail</b> and <b>Next fail</b> >+buttons move the focus within the history backwards (chronologically) and >+forwards (chronologically) respectively to the next failure node.</p> >+ >+<p>Click on an event node in the <b>Events</b> pane to get >+information about that event in the right-hand pane.</p> >+ >+<p>(C) Copyright IBM Corporation 2000, 2005. All Rights >+Reserved.</p> >+ > </div> > >-<div> >-<p> >-<b class="parentlink">Parent topic:</b> <a href="../concepts/cmanualtestoverview.htm" title="">Manual testing with TPTP</a><br /> >-</p> >-</div><div class="runningfooter">(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.</div> > </body> >-</html> >\ 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" /> >-<!-- All rights reserved. Licensed Materials Property of IBM --> >-<!-- US Government Users Restricted Rights --> >-<!-- Use, duplication or disclosure restricted by --> >-<!-- GSA ADP Schedule Contract with IBM Corp. --> >-<link rel="stylesheet" type="text/css" href="../css/ibmdita.css" /> >-<link rel="stylesheet" type="text/css" href="../css/swg_info_common.css" /> >+<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><p>This topic describes how to create a deployment for your test suite. >-You must create a deployment before you can run a test.</p> >-<div class="p">A test deployment definition typically consists of one or more pairs >-of test artifacts and locations. Test artifacts are test suites and datapools. >-A location identifies the computer where you run the test suite. Hyades reads >-the pairing and deploys the test artifacts on the computer specified. You >-can also create a test deployment that specifies only a location; it does >-not specify test artifacts. Such a deployment is convenient when you want >-to run a specific test suite on a specific computer. In this case, you do >-not need to create a test artifact for the test suite. You select the test >-suite and the location-only deployment, and Hyades deploys the test suite >-to the computer specified in the deployment definition and runs the test suite >-on that computer.</div> >-<div class="skipspace">To create a test deployment:</div> >-<ol><li><span>In the Test Navigator select the test suite for which you want >-to create a deployment. Click <span class="menucascade"><span class="uicontrol">File</span> > <span class="uicontrol">New</span> > <span class="uicontrol">Other</span></span>. The <span class="uicontrol">New</span> wizard >-opens, as shown below. <br /><img src="../images/newwizard.gif" /><br /></span></li> >-<li><span>Expand the <span class="uicontrol">Test</span> folder and the <span class="uicontrol">Test >-Elements</span> folder, then select <span class="uicontrol">Deployment</span>. >-Click <span class="uicontrol">Next</span>. The next page of the wizard opens, as shown >-below. <br /><img src="../images/newdeployment.gif" /><br /></span></li> >-<li><span>Navigate to the folder that will store the deployment file resource. >-Enter a name for the file resource in the <span class="uicontrol">File name</span> field. >-Click <span class="uicontrol">Next</span>. The next page of the wizard opens, as shown >-below. <br /><img src="../images/newdeployment2.gif" /><br /></span></li> >-<li><span>Enter a name and brief description for the deployment. The default >-name for the deployment is the name you specified for the file resource. >-The name that you specify here >-is the one that appears in the Test Navigator. Click <span class="uicontrol">Next</span>. >-The next page of the wizard opens, as shown below. <br /><img src="../images/newdeployment3.gif" /><br /></span></li> >-<li><span>To create a deployment that consists of a location only, click <span class="uicontrol">Next</span> and >-skip ahead to Step 10. When you run a test with such a deployment, Hyades >-deploys that test suite to the location specified in the deployment. Otherwise, >-click <span class="uicontrol">Add</span> to open the <span class="uicontrol">Add Artifact Association</span> page, >-as shown below. <br /><img src="../images/addartifact.gif" /><br /></span></li> >-<li><span>If you have previously defined one or more artifacts that you want >-to use in this deployment, click <span class="uicontrol">Browse</span> and navigate >-to the artifact. After you select the artifact, click <span class="uicontrol">Finish</span>. >-To define a new artifact select <span class="uicontrol">Create a new resource</span> and >-click <span class="uicontrol">Next</span>. The New Artifact wizard opens, as shown >-below. <br /><img src="../images/newartifact.gif" /><br /></span></li> >-<li><span>Navigate to the folder that will store the artifact file resource. >-Enter a name for the artifact file resource in the <span class="uicontrol">File name</span> field. >-Click <span class="uicontrol">Next</span>. The next page of the wizard opens, as shown >-below. <br /><img src="../images/newartifact2.gif" /><br /></span></li> >-<li><span>Enter a name and description for the artifact. The default name >-is the name that you specified for the artifact file resource. The name you >-specify here is the one that appears in the Test Navigator. Click <span class="uicontrol">Next</span>. >-The next page of the wizard opens, as shown below. <br /><img src="../images/newartifact3.gif" /><br /></span></li> >-<li><span>Click the boxes next to the test assets that you want to include >-in the artifact. To see the folders that the test assets belong to click <span class="uicontrol">Show >-Folders</span>. Click <span class="uicontrol">Finish</span>. The new artifact >-appears in the list of artifacts to be added to the deployment, as shown below. <br /><img src="../images/newdeployment5.gif" /><br />To add another artifact >-click <span class="uicontrol">Add</span> and repeat the steps. When you are satisfied >-with the list of artifacts, click <span class="uicontrol">Next</span>. The next page >-of the wizard appears, as shown below. <br /><img src="../images/newdeployment6.gif" /><br /></span></li> >-<li><span>Click <span class="uicontrol">Add</span> to select a location to be associated >-with the deployment. The Add Location Association dialog box opens, as shown >-below. <br /><img src="../images/addlocation.gif" /><br /></span></li> >-<li><span>To select an existing location resource click <span class="uicontrol">Browse</span> and >-navigate to the location. To create a location, select <span class="uicontrol">Create a >-new resource</span> and click <span class="uicontrol">Next</span>. The New Location >-wizard opens, as shown below. <br /><img src="../images/addlocation2.gif" /><br /></span></li> >-<li><span>Navigate to the folder that will store the location resource file. >-Enter a name for the location resource file in the <span class="uicontrol">File name</span> field. >-Click <span class="uicontrol">Next</span>. The next page of the wizard appears, as >-shown below. <br /><img src="../images/addlocation3.gif" /><br /></span></li> >-<li><span>Enter a name and brief description for the location. The default >-name is the name that you specified for the location resource file. The name >-you specify here is the name that appears in the Test Navigator. Click <span class="uicontrol">Finish</span>. >-The new location appears in the list of locations to be added to the deployment, >-as shown below. <br /><img src="../images/newdeployment7.gif" /><br />To >-add another location click <span class="uicontrol">Add</span> and repeat the steps. >-When you are satisfied with the list of locations to be added to the deployment, >-click <span class="uicontrol">Next</span>. The next page of the wizard opens, as shown >-below. <br /><img src="../images/newdeployment8.gif" /><br /></span></li> >-<li><span>The left pane lists test artifacts and the right pane lists locations. >-Create one or more pairs of test artifacts and locations by selecting one >-from each pane and clicking <img src="../images/arrow.gif" />. By creating >-pairs of artifacts and locations you are specifying which test artifacts should >-be deployed to which computers when the test is run. If you are creating a >-location-only deployment, the test artifacts pane will be empty. To remove >-a pair, select it from the list and click <span class="uicontrol">Remove</span>. To >-move a pair up in the list, select the pair and click <span class="uicontrol">Up</span>. >-When you are satisfied with the list of pairs, click <span class="uicontrol">Finish</span>. </span></li> >-<li><span>From the Test Navigator, double-click the location that you created. >-The location's <span class="uicontrol">Overview</span> tab opens, as shown below. <br /><img src="../images/addlocation4.gif" /><br /></span></li> >-<li><span>The default host name for the location is <kbd class="userinput">localhost</kbd>. >-If the location is for another computer, enter the name of that computer in >-the <span class="uicontrol">Host name</span> field. </span></li> >-</ol> >-</div> >+<body> > > <div> >+ >+<h1><a name=creatingatestdeployment></a>Creating a Test Deployment</h1> >+ >+<p>This topic describes how to create a deployment for your test suite. Unless >+you make use of the default deployment to run your test locally, you must >+create a deployment before you can run a test.</p> >+ >+<p>A test deployment definition typically consists of one or >+more pairs of test artifacts and locations. Test artifacts are test suites and >+datapools. A location identifies the computer where you run the test suite. >+TPTP reads the pairing and deploys the test artifacts on the computer specified. >+You can also create a test deployment that specifies only a location; it does >+not specify test artifacts. Such a deployment is convenient when you want to >+run a specific test suite on a specific computer. In this case, you do not need >+to create a test artifact for the test suite. You select the test suite and the >+location-only deployment, and TPTP deploys the test suite to the computer >+specified in the deployment definition and runs the test suite on that >+computer.</p> >+ >+<p>To create a test deployment:</p> >+ >+<ol> >+ <li> >+ <p>In >+ the Test Navigator select the test suite for which you want to create a >+ deployment. Select <b>File</b><b> > </b><b>New</b><b> > </b><b>Other</b>. The New >+ wizard opens.</p> >+ </li> >+ <li> >+<p>Expand the Test folder and the Test Assets folder, then select Deployment. >+Click <b>Next</b>. The next page of the wizard >+opens.</p> >+<p>Navigate to the folder that will store the deployment file >+resource. Enter a name for the deployment in the name >+field. Click <b>Next</b>. The next page of the >+wizard opens: </p> >+</li> >+<li> >+<p>Optionally enter a brief description for the deployment. Click >+<b>Next</b>. The next page of the wizard opens.</p> >+</li> >+<li> >+<p>(To create a deployment that consists of a location only, >+click <b>Next</b> and skip ahead to <b>Step 9</b>). >+When you run a test with such a deployment, TPTP deploys the test suite to the >+location specified in the deployment. Otherwise, click Add >+to open the Add Artifact Association page.</p> >+</li> >+<li> >+<p>If you have previously defined one or more artifacts that >+you want to use in this deployment, click <b>Browse</b> >+and navigate to the artifact. After you select the artifact, click <b>Finish</b>. To define a new artifact check the <b>Create a new resource</b> button and click <b>Next</b>. The New Artifact wizard opens.</p> >+</li> >+<li> >+<p>Navigate to the folder that will store the artifact file >+resource. Enter a name for the artifact file resource in the Name field. Click <b>Next</b>. >+The next page of the wizard opens.</p> >+</li> >+<li> >+<p>Optionally enter a description for the artifact. Click <b>Next</b>. The next page of the wizard opens.</p> >+</li> >+<li> >+<p>Click the boxes next to the test asset(s) that you want to >+include in the artifact. Click <b>Finish</b>. The >+new artifact appears in the list of artifacts to be added to the deployment.</p> > <p> >-<b class="parentlink">Parent topic:</b> <a href="../concepts/ccommontestingtasksandconcepts.htm" title="The Eclipse test and performance tools platform (TFTP) provides support for three types of testing:">Common testing tasks and concepts</a><br /> >+To add another artifact click Add and repeat the >+steps. When you are satisfied with the list of artifacts, click <b>Next</b>. The next page of the wizard appears.</p> >+</li> >+<li> >+<p>Click <b>Add</b> to select a >+location to be associated with the deployment. The <b>Add Location Association</b> >+dialog box opens, as above.</p> >+</li> >+<li> >+<p>To select an existing location resource click <b>Browse</b> and navigate to the location. To create a >+location, check the <b>Create a new resource</b> >+button and click <b>Next</b>. The New Location >+wizard opens. </p> >+ >+<p>Navigate to the folder that will store the location resource >+file. Enter a name for the location resource file in the File >+name field. Click <b>Next</b>. The next >+page of the wizard appears.</p> >+</li> >+<li> >+<p>Optionally >+enter a description for the location. Click <b>Finish</b>. >+The new location appears in the list of locations to be added to the >+deployment.</p> >+<p> >+To add another location click <b>Add</b> and >+repeat the steps. When you are satisfied with the list of locations to be added >+to the deployment, click <b>Next</b>. The next >+page of the wizard opens.</p> >+</li> >+<li> >+ >+<p>The >+left-pane lists test artifacts and the right-pane lists locations. Create one >+or more pairs of test artifacts and locations by selecting one from each pane >+and clicking the down-arrow. By creating pairs of artifacts and locations you >+are specifying which test artifacts should be deployed to which computers when >+the test is run. If you are creating a location-only deployment, the test artifacts >+pane will be empty. To remove a pair, select it from the list and click Remove. To move a pair up in the list, select the pair >+and click Up. When you are satisfied with the list >+of pairs, click Finish.</p> >+</li> >+</ol> >+ >+<p><strong>Related tasks</strong><br/> >+ <a href="trunningmanualtestsuite.htm">Running a manual test</a><br/> >+ <a href="tediting_manual_test.htm">Editing a manual test</a><br/> >+ <a href="tanalyzingmanualtestresults.htm">Analyzing manual test results</a><br/> >+</p> >+ >+<p><strong>Related reference</strong><br/> >+ <a href="../ref/rtestlog.html">Test Log viewer</a><br/> > </p> >-</div><div class="runningfooter">(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.</div> >+ >+<p>(C) Copyright IBM Corporation 2000, 2005. All Rights >+Reserved.</p> >+ >+ >+</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" /> >-<!-- All rights reserved. Licensed Materials Property of IBM --> >-<!-- US Government Users Restricted Rights --> >-<!-- Use, duplication or disclosure restricted by --> >-<!-- GSA ADP Schedule Contract with IBM Corp. --> >-<link rel="stylesheet" type="text/css" href="../css/ibmdita.css" /> >-<link rel="stylesheet" type="text/css" href="../css/swg_info_common.css" /> >+<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><p>This section describes the procedure for creating a manual test >-suite.</p> >-<ol><li><span>Click <span class="menucascade"><span class="uicontrol">File</span> > <span class="uicontrol">New</span> > <span class="uicontrol">Other</span></span></span></li> >-<li><span>In the <span class="uicontrol">New</span> dialog box, shown below, expand >-the <span class="uicontrol">Test</span> folder, expand the <span class="uicontrol">Test Suite</span> folder, >-select <span class="uicontrol">Test Suite</span>, and click <span class="uicontrol">Next</span>. <br /><img src="../images/newmanualtest.gif" /><br /></span></li> >-<li><span>The <span class="uicontrol">New Test Suite</span> wizard appears, as shown >-below. <br /><img src="../images/newmanualtest2.gif" /><br />Navigate >-to the folder that will contain the test suite. Enter a name for the file >-resource that will store the test suite in the <span class="uicontrol">File name</span> field. >- Click <span class="uicontrol">Next</span>. The next page of the wizard appears, as >-shown below. <br /><img src="../images/newmanualtest3.gif" /><br /></span></li> >-<li><span>Specify the name of the test suite definition and enter a description >-of the test suite. By default, the name of the test suite definition is the >-same name that you specified for the file resource without the <kbd class="userinput">.testsuite</kbd> suffix. >-The name that you specify here is the name that appears in the Test Navigator. >-Click <span class="uicontrol">Finish</span> to close the wizard. The <span class="uicontrol">Test >-Suite</span> dialog box opens and you can now edit the definition by >-adding test methods and specifying behaviors that control how the methods >-should be run.</span></li> >-</ol> >-</div> >+<body> > > <div> >+ >+<h2>Creating a manual test</h2> > <p> >-<b class="parentlink">Parent topic:</b> <a href="../concepts/cmanualtestoverview.htm" title="">Manual testing with TPTP</a><br /> >+This topic describes how to create a manual test suite. >+</p> >+ >+<ol> >+ <li>Click <b>File > New > Other</b>. The <b>New</b> dialog appears.</li> >+ <li>Expand the <b>Test</b> folder, then select <b>TPTP Manual Test</b>.</li> >+ <li>Click <b>Next</b> and name the the manual test, for example, <em id="CodeName">exampleManualTest</em>.</li> >+ <li>Click <b>Next</b> and optionally provide a description for the manual test suite. Click <b>Finish</b>.</li> >+ <li>A manual test testsuite file (<em id="CodeName">exampleManualTest.testsuite</em>) will be created and becomes visible in the Navigator.</li> >+</ol> >+ >+<p><strong>Related tasks</strong><br /> >+<a href="tediting_manual_test.htm">Editing a manual test</a><br/> >+<a href="trunningmanualtestsuite.htm">Running a manual test</a><br /> > </p> >-</div><div class="runningfooter">(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.</div> >+ >+<p>(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.</p> >+ >+</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><p>This section describes how to edit your manual test suite.</p> >+<div> >+<p>This section describes how to edit your manual test suite.</p> > <div class="p">You must have created a manual test suite.</div> >-<ol><li><span>In the <span class="uicontrol">Navigator</span> double-click the test suite >-entry to open the <span class="uicontrol">Test Suite </span> dialog box as shown below. >-The test suite opens in the <span class="uicontrol">Overview</span> tab with the two >-edit areas (<span class="uicontrol">General Information</span> and <span class="uicontrol">Test >-Cases</span>) expanded. <br /><img src="../images/manualtestsuite.gif" /><br /></span></li> >-<li><span>The <span class="uicontrol">General Information</span> area displays the >-test suite's name, an optional description, test type, and name of the file >-containing the test suite. You can edit information appearing in boxes.</span></li> >-<li><span>The <span class="uicontrol">Test Cases</span> area lists the individual >-tests that make up the test suite. Click one of the test cases or <span class="uicontrol">More</span> to >-display the Test Cases view, as shown below. <br /><img src="../images/manualtestcases.gif" /><br />To change the name or description of a test case, select >-the test case and enter new text in the <span class="uicontrol">Name</span> or <span class="uicontrol">Description</span> boxes. >-Use the <span class="uicontrol">Add</span> and <span class="uicontrol">Remove</span> buttons >-to add test cases and to remove existing cases. Use the <span class="uicontrol">Up</span> and <span class="uicontrol">Down</span> buttons >-to change the order of cases.</span></li> >-<li><span>Click the <span class="uicontrol">Behaviors</span> tab to display the Behaviors >-view, as shown below. <br /><img src="../images/manualbehaviors.gif" /><br />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 <span class="uicontrol">Number >-of Iterations</span> box to specify how many times to execute the loop. >-With <span class="uicontrol">Synchronous</span> checked and more than one iteration >-specified, the loop iterations execute in sequence. With <span class="uicontrol">Synchronous</span> unchecked >-and more than one iteration specified, the loop iterations execute simultaneously. </span></li> >-<li><span>Use the <span class="uicontrol">Up</span> and <span class="uicontrol">Down</span> buttons >-to change the order of invocations and loops. Use the <span class="uicontrol">Add</span> and <span class="uicontrol">Remove</span> buttons >-to add and remove loops and invocations. After you create a loop you can add >-an invocation to it by right-clicking the loop and selecting <span class="menucascade"><span class="uicontrol">Add</span> > <span class="uicontrol">Invocation</span></span>. >-The <span class="uicontrol">Test Invocation</span> dialog box, shown below, appears. <br /><img src="../images/addinvocationmanual.gif" /><br />The top pane lists >-test cases in the test suite. The bottom pane lets you navigate to test cases >-in other test suites in your workspace. You can nest loops and create invocations >-that are outside of any loop.</span></li> >+<ol> >+ <li><span>In the <span class="uicontrol">Test Navigator</span> >+ double-click the test suite entry to open the <span class="uicontrol">Test >+ Suite </span> dialog box. The test suite opens in the <span >+ class="uicontrol">Overview</span> tab with the two edit areas (<span >+ class="uicontrol">General Information</span> and <span >+ class="uicontrol">Test Cases</span>) expanded.</span></li> >+ <li><span>The <span class="uicontrol">General Information</span> area >+ displays the test suite's name, an optional description, test type, and >+ name of the file containing the test suite. You can edit information >+ appearing in boxes.</span></li> >+ <li>The <span class="uicontrol">Test Cases</span> area lists the >+ individual tests that make up the test suite. Click one of the test >+ cases or <span class="uicontrol">More</span> to display the Test Cases >+ view. To change the name or description of a test case, select the test >+ case and enter new text in the <span class="uicontrol">Name</span> or <span >+ class="uicontrol">Description</span> boxes. Use the <span >+ class="uicontrol">Add</span> and <span class="uicontrol">Remove</span> >+ buttons to add test cases and to remove existing cases. Use the <span >+ class="uicontrol">Up</span> and <span class="uicontrol">Down</span> >+ buttons to change the order of cases.</li> >+ <li><span>Click the <span class="uicontrol">Behaviors</span> tab to >+ display the Behaviors view. Behaviors let you control the order in >+ which test cases are run; you do this by specifying invocations and >+ loops. For example, in the figure shown below, <kbd class="userinput">test >+ 1</kbd> runs inside <kbd class="userinput">Loop 1</kbd>.<img >+ src="../images/manualbehaviors.gif" /> >+ <br/>Use the <span >+ class="uicontrol">Number of Iterations</span> box to specify how many >+ times to execute the loop. With <span class="uicontrol">Synchronous</span> >+ checked and more than one iteration specified, the loop iterations >+ execute in sequence. With <span class="uicontrol">Synchronous</span> >+ unchecked and more than one iteration specified, the loop iterations >+ execute simultaneously. </span></li> >+ <li><span>Use the <span class="uicontrol">Up</span> and <span >+ class="uicontrol">Down</span> buttons to change the order of >+ invocations and loops. Use the <span class="uicontrol">Add</span> and <span >+ class="uicontrol">Remove</span> buttons to add and remove loops and >+ invocations. After you create a loop you can add an invocation to it by >+ right-clicking the loop and selecting <span class="menucascade"><span >+ class="uicontrol">Add</span> > <span class="uicontrol">Invocation</span></span>. >+ The <span class="uicontrol">Test Invocation</span> dialog box appears. >+ The top pane lists test cases in the test suite. The bottom pane lets >+ you navigate to test cases in other test suites in your workspace. You >+ can nest loops and create invocations that are outside of any loop.</span></li> > </ol> > </div> > >-<div> >-<p> >-<b class="parentlink">Parent topic:</b> <a href="../concepts/cmanualtestoverview.htm" title="">Manual testing with TPTP</a><br /> >+<p><strong>Related tasks</strong><br /> >+<a href="tcreatingamanualtest.htm">Creating a manual test</a><br /> >+<a href="trunningmanualtestsuite.htm">Running a manual test</a><br /> > </p> >-</div><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" /> >-<!-- All rights reserved. Licensed Materials Property of IBM --> >-<!-- US Government Users Restricted Rights --> >-<!-- Use, duplication or disclosure restricted by --> >-<!-- GSA ADP Schedule Contract with IBM Corp. --> >-<link rel="stylesheet" type="text/css" href="../css/ibmdita.css" /> >-<link rel="stylesheet" type="text/css" href="../css/swg_info_common.css" /> >+<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><p>This topic describes how to create and run a manual test.</p> >-<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"><span>From the Test Navigator click <span class="menucascade"><span class="uicontrol">Run</span> > <span class="uicontrol">Run</span></span>. The Run dialog box opens. </span></li> >-<li class="skipspace"><span>In the <span class="uicontrol">Configurations</span> pane on the left, >-click <span class="uicontrol">Hyades Manual Test</span>. <br /><img src="../images/perspectiveMan.gif" alt=" " /><br /></span></li> >-<li class="skipspace"><span>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.</span></li> >-<li class="skipspace"><span>To create a new configuration, click the <span class="uicontrol">New</span> button >-on the bottom left. </span> <p>A new test configuration, initially >-named <kbd class="userinput">New_Configuration</kbd>, is created. Change the name >-if you like. Alternatively, expand <span class="uicontrol">Hyades Manual Test</span> and >-click a listed configuration that you want to inspect or modify. The Run dialog >-box opens in the Test tab.<br /><img src="../images/manualDeploy.gif" alt=" " /><br /></p> >-</li> >-<li class="skipspace"><span>In the <span class="uicontrol">Select Test to run</span> pane in the middle >-listing all projects in the workspace, navigate to the project containing >-the test to run and click it.</span></li> >-<li class="skipspace"><span>In the <span class="uicontrol">Select a deployment</span> pane on the right >-listing all defined deployments in the workspace, click the one to use for >-this run.</span> <p>To run the test using default values, or using the >-same values that you set during the previous test run, you can click <span class="uicontrol">Run</span> now >-and stop reading.</p> >-</li> >-<li class="skipspace"><span>Click <span class="uicontrol">Apply</span> to save the selections on this >-tab.</span></li> >-<li class="skipspace"><span>Click <span class="uicontrol">Execution Results</span> to display that >-tab, as shown below. <br /><img src="../images/manualconfig2.gif" /><br /> </span></li> >-<li class="skipspace"><span>To overwrite the test results file that was used the last time >-this test was run, rather than creating a new results file, check the box >-beside <span class="uicontrol">Override existing Execution Results resource</span>.</span></li> >-<li class="skipspace"><span>In the <span class="uicontrol">Location</span> box listing Java projects >-in the workspace, click the one in which to store the test results.</span></li> >-<li class="skipspace"><span>Click <span class="uicontrol">Apply</span> to save the selections on this >-tab.</span></li> >-<li class="skipspace"><span>Click <span class="uicontrol">Common</span> to display the <span class="uicontrol">Common</span> tab, >-as shown below. <br /><img src="../images/manualconfig3.gif" /><br /></span></li> >-<li class="skipspace"><span>When you run a test configuration, Eclipse creates a file, with >-a <kbd class="userinput">.launch</kbd> suffix, containing metadata. If you select <span class="uicontrol">Local</span>, >-Eclipse stores this file in your workspace's metadata folder, which is not >-visible to other users. If you want other users to have access to the file, >-select <span class="uicontrol">Shared</span>, click <span class="uicontrol">Browse</span>, >-and navigate to a folder in your workspace where you want to store the file. </span></li> >-<li class="skipspace"><span>To have the test configuration appear in the <span class="uicontrol">Run</span> favorites >-toolbar menu, check this item in the <span class="uicontrol">Display in favorites menu >-box</span>.</span></li> >-<li class="skipspace"><span>Select <span class="uicontrol">Launch in background</span> to have Eclipse >-run the test configuration in the background so that you can perform other >-Eclipse tasks while the test runs. </span></li> >-<li class="skipspace"><span>Click <span class="uicontrol">Apply</span> to save the settings for the >-configuration. </span></li> >-<li class="skipspace"><span>Click <span class="uicontrol">Run</span>. The Manual Remote Application >-dialog box opens, as shown below. <br /><img src="../images/manualtestremote.gif" /><br /></span></li> >-<li class="skipspace"><span>Navigate to a test in the left pane. The name and description of >-the test appears in the right pane. After you perform the steps specified >-in the test's description, indicate whether the test passed, failed, returned >-an error, or was inconclusive by selecting a value in the <span class="uicontrol">Status</span> drop-down >-list. Enter comments about the test results in the <span class="uicontrol">Info</span> field. </span></li> >-<li class="skipspace"><span>Click <span class="uicontrol">Next</span> to save the test results and >-move to the next test.</span></li> >-<li class="skipspace"><span>When you finish running all tests, click <span class="uicontrol">End Execution</span> to >-close the dialog box.</span></li> >+<body> >+ >+<div> >+ >+<h2>Running a manual test</h2> >+<p>This topic describes how to create and run a manual test.</p> >+<ol> >+ <li><a href="tprereqmanualtestconfiguration.htm">Preparing to run a manual test</a></li> >+ <li><a href="tcreatemanualtestconfiguration.htm">Creating a test configuration</a></li> >+ <li><a href="trunmanualtest.htm">Running the test configuration</a></li> > </ol> >+ >+ >+ >+<p>(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.</p> >+ > </div> > >-<div> >-<p> >-<b class="parentlink">Parent topic:</b> <a href="../concepts/cmanualtestoverview.htm" title="">Manual testing with TPTP</a><br /> >-</p> >-</div><div class="runningfooter">(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.</div> > </body> >-</html> >\ 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"/> >- >-<!--[if !mso]> >-<style> >-v\:* {behavior:url(#default#VML);} >-o\:* {behavior:url(#default#VML);} >-w\:* {behavior:url(#default#VML);} >-.shape {behavior:url(#default#VML);} >-</style> >-<![endif]--> >-<title>Creating a test deployment</title> >-<style> >-<!-- >---> >-</style> >-</head> >- >-<body link=blue vlink=blue> >- >-<div> >- >-<h1><a name=creatingatestdeployment></a>Creating a Test Deployment</h1> >- >-<p>This topic describes how to create a deployment for your test suite. Unless >-you make use of the default deployment to run your test locally, you must >-create a deployment before you can run a test.</p> >- >-<p>A test deployment definition typically consists of one or >-more pairs of test artifacts and locations. Test artifacts are test suites and >-datapools. A location identifies the computer where you run the test suite. >-TPTP reads the pairing and deploys the test artifacts on the computer specified. >-You can also create a test deployment that specifies only a location; it does >-not specify test artifacts. Such a deployment is convenient when you want to >-run a specific test suite on a specific computer. In this case, you do not need >-to create a test artifact for the test suite. You select the test suite and the >-location-only deployment, and TPTP deploys the test suite to the computer >-specified in the deployment definition and runs the test suite on that >-computer.</p> >- >-<p> </p> >- >-<p>To create a test deployment:</p> >- >-<h3>Step 1</h3> >- >-<p>In >-the Test Navigator select the test suite for which you want to create a >-deployment. Select <b>File</b><b> > </b><b>New</b><b> > </b><b>Other</b>. The New >-wizard opens:</p> >- >-<p align=center><br/> >-<!--[if gte vml 1]><v:shapetype id="_x0000_t75" coordsize="21600,21600" o:spt="75" >- o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe" filled="f" stroked="f"> >- <v:stroke joinstyle="miter"/> >- <v:formulas> >- <v:f eqn="if lineDrawn pixelLineWidth 0"/> >- <v:f eqn="sum @0 1 0"/> >- <v:f eqn="sum 0 0 @1"/> >- <v:f eqn="prod @2 1 2"/> >- <v:f eqn="prod @3 21600 pixelWidth"/> >- <v:f eqn="prod @3 21600 pixelHeight"/> >- <v:f eqn="sum @0 0 1"/> >- <v:f eqn="prod @6 1 2"/> >- <v:f eqn="prod @7 21600 pixelWidth"/> >- <v:f eqn="sum @8 21600 0"/> >- <v:f eqn="prod @7 21600 pixelHeight"/> >- <v:f eqn="sum @10 21600 0"/> >- </v:formulas> >- <v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect"/> >- <o:lock v:ext="edit" aspectratio="t"/> >-</v:shapetype><v:shape id="_x0000_i1025" type="#_x0000_t75" style='width:375pt; >- height:326.25pt'> >- <v:imagedata src="../images_deploy/image001.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<h3>Step 2</h3> >- >-<p>Expand the Test folder and the Test Assets folder, then select Deployment. >-Click <b>Next</b>. The next page of the wizard >-opens: </p> >- >-<p align=center><!--[if gte vml 1]><v:shape id="_x0000_i1026" >- type="#_x0000_t75" style='width:375pt;height:300.75pt'> >- <v:imagedata src="../images_deploy/image003.png" o:title=""/> >-</v:shape><![endif]--><br/><br/></p> >- >-<p>Navigate to the folder that will store the deployment file >-resource. Enter a name for the deployment in the name >-field. Click <b>Next</b>. The next page of the >-wizard opens: </p> >- >-<h3>Step 3<br/><br/></h3> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1027" type="#_x0000_t75" style='width:375pt;height:213.75pt'> >- <v:imagedata src="../images_deploy/image005.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p>(Optionally) enter a brief description for the deployment. Click >-<b>Next</b>. The next page of the wizard opens:</p> >- >-<h3>Step 4 <br/><br/></h3> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1028" type="#_x0000_t75" style='width:375pt;height:213.75pt'> >- <v:imagedata src="../images_deploy/image007.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p>(To create a deployment that consists of a location only, >-click <b>Next</b> and skip ahead to <b>Step 9</b>). >-When you run a test with such a deployment, TPTP deploys the test suite to the >-location specified in the deployment. Otherwise, click Add >-to open the Add Artifact Association page: <br/><br/></p> >- >-<h3>Step 5</h3> >- >-<p align=center><!--[if gte vml 1]><v:shape id="_x0000_i1029" >- type="#_x0000_t75" style='width:328.5pt;height:311.25pt'> >- <v:imagedata src="../images_deploy/image009.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p>If you have previously defined one or more artifacts that >-you want to use in this deployment, click <b>Browse</b> >-and navigate to the artifact. After you select the artifact, click <b>Finish</b>. To define a new artifact check the <b>Create a new resource</b> button and click <b>Next</b>. The New Artifact wizard opens:</p> >- >-<h3>Step 6</h3> >- >-<p align=center><!--[if gte vml 1]><v:shape id="_x0000_i1030" >- type="#_x0000_t75" style='width:328.5pt;height:295.5pt'> >- <v:imagedata src="../images_deploy/image011.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p>Navigate to the folder that will store the artifact file >-resource. Enter a name for the artifact file resource in the Name field. Click <b>Next</b>. >-The next page of the wizard opens:<br/><br/></p> >- >-<h3>Step 7</h3> >- >-<p align=center><!--[if gte vml 1]><v:shape id="_x0000_i1031" >- type="#_x0000_t75" style='width:328.5pt;height:214.5pt'> >- <v:imagedata src="../images_deploy/image013.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p><br/><br/></p> >- >-<p>(Optionally) enter a description for the artifact. Click <b>Next</b>. The next page of the wizard opens:</p> >- >-<h3>Step 8</h3> >- >-<p align=center><!--[if gte vml 1]><v:shape id="_x0000_i1032" >- type="#_x0000_t75" style='width:328.5pt;height:248.25pt'> >- <v:imagedata src="../images_deploy/image015.png" o:title=""/> >-</v:shape><![endif]--> <br/><br/></p> >- >-<p>Click the boxes next to the test asset(s) that you want to >-include in the artifact. Click <b>Finish</b>. The >-new artifact appears in the list of artifacts to be added to the deployment:</p> >- >-<p align=center><!--[if gte vml 1]><v:shape id="_x0000_i1033" >- type="#_x0000_t75" style='width:375pt;height:236.25pt'> >- <v:imagedata src="../images_deploy/image017.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p><br/> >-<br/> >-To add another artifact click Add and repeat the >-steps. When you are satisfied with the list of artifacts, click <b>Next</b>. The next page of the wizard appears:</p> >- >-<h3>Step 9<br/><br/></h3> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1034" type="#_x0000_t75" style='width:402pt;height:258.75pt'> >- <v:imagedata src="../images_deploy/image019.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p>Click <b>Add</b> to select a >-location to be associated with the deployment. The <b>Add Location Association</b> >-dialog box opens, as above:<br/><br/></p> >- >-<h3>Step 10</h3> >- >-<p>To select an existing location resource click <b>Browse</b> and navigate to the location. To create a >-location, check the <b>Create a new resource</b> >-button and click <b>Next</b>. The New Location >-wizard opens: </p> >- >-<p align=center><!--[if gte vml 1]><v:shape id="_x0000_i1035" >- type="#_x0000_t75" style='width:328.5pt;height:276pt'> >- <v:imagedata src="../images_deploy/image021.png" o:title=""/> >-</v:shape><![endif]--><br/><br/></p> >- >-<p>Navigate to the folder that will store the location resource >-file. Enter a name for the location resource file in the File >-name field. Click <b>Next</b>. The next >-page of the wizard appears:</p> >- >-<h3>Step 11 <br/><br/></h3> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1036" type="#_x0000_t75" style='width:328.5pt;height:206.25pt'> >- <v:imagedata src="../images_deploy/image023.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p>(Optionally) >-enter a description for the location. Click <b>Finish</b>. >-The new location appears in the list of locations to be added to the >-deployment:</p> >- >-<p align=center><!--[if gte vml 1]><v:shape id="_x0000_i1037" type="#_x0000_t75" >- style='width:375pt;height:235.5pt'> >- <v:imagedata src="../images_deploy/image025.png" o:title=""/> >-</v:shape><![endif]--> </p> >- >-<p><br/> >-<br/> >-To add another location click <b>Add</b> and >-repeat the steps. When you are satisfied with the list of locations to be added >-to the deployment, click <b>Next</b>. The next >-page of the wizard opens:</p> >- >-<h3>Step 12 <br/><br/></h3> >- >-<p align=center><!--[if gte vml 1]><v:shape >- id="_x0000_i1038" type="#_x0000_t75" style='width:375pt;height:319.5pt'> >- <v:imagedata src="../images_deploy/image027.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p>The >-left-pane lists test artifacts and the right-pane lists locations. Create one >-or more pairs of test artifacts and locations by selecting one from each pane >-and clicking the down-arrow. By creating pairs of artifacts and locations you >-are specifying which test artifacts should be deployed to which computers when >-the test is run. If you are creating a location-only deployment, the test artifacts >-pane will be empty. To remove a pair, select it from the list and click Remove. To move a pair up in the list, select the pair >-and click Up. When you are satisfied with the list >-of pairs, click Finish.</p> >- >-<h3>Viewing and Editing Artifacts, Locations, and Deployments </h3> >- >-<p>To >-view any of the entities you have created, double-click on it in the Navigator >-View. For example, for the location sampleLocation:</p> >- >-<p align=center><!--[if gte vml 1]><v:shape id="_x0000_i1039" type="#_x0000_t75" >- style='width:400.5pt;height:382.5pt'> >- <v:imagedata src="../images_deploy/image029.png" o:title=""/> >-</v:shape><![endif]--></p> >- >-<p>The >-location's <b>Overview</b><b> tab</b> opens, as >-shown below. The default host name for >-the location is <kbd><b>localhost</b></kbd>. >-If the location is for another computer, enter the name of that computer in the >-<b>Host name</b> field. </p> >- >-<p><b>Parent topic:</b> <a >-href="../concepts/ccommontestingtasksandconcepts.htm" >-title="The Eclipse test and performance tools platform (TFTP) provides support for three types of testing:">Common >-testing tasks and concepts</a></p> >- >-<p>(C) Copyright IBM Corporation 2000, 2005. All Rights >-Reserved.</p> >- >-<p> </p> >- >-</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 >+<i>TPTP Tester guide</i> in detail. >+ >+<ul> >+ <li><a href="rmanualcreate.htm">Generic launch configuration properties</a></li> >+ <li><a href="rtestlog.html">Test Log viewer</a></li> >+</ul> >+ >+<p>(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.</p> >+ >+</div> >+ >+</body> >+ >+</html> >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> >+<p>Eclipse provides the <b>Common</b> tab at the right of the <b>Run</b> dialog for editing various generic launch configuration properties. Select the <b>Common</b> >+tab at the right of the <b>Run</b> dialog to edit the following generic launch configuration properties:</p> >+ >+<ul> >+ <li>When the launch configuration is saved by clicking <b>Run</b> at the bottom of the <b>Run</b> dialog, a >+launch configuration file (<i>.launch</i>) is created and saved. By default, the launch configuration file is saved in the workspace's <i>.metadata</i> >+directory. The location for the .launch file may be changed to any directory in the workspace via the <b>Save as</b> pane of the <b>Common</b> tab.</li> >+ <li>When rerunning a launch configuration, a shortcut may be associated with one or more favorites tool bar menus in the <b>Display in favorites menu</b> >+ pane of the <b>Common</b> tab.</li> >+ <li>When a launch configuration is executed by clicking <b>Run</b> at the bottom of the <b>Run</b> dialog, the <b>Console</b> view >+ is used for rendering standard output data and reading standard input data. By default, the encoding of the <b>Console</b> view is the encoding for the >+ local platform. The encoding of the <b>Console</b> view may be changed to any valid encoding in the <b>Console Encoding</b> pane of the <b>Common</b> tab.</li> >+ <li>When a launch configuration is executed, the standard output and standard input might display output data and read input data, respectively. By default, the <b>Console</b> view is used for both the standard output and standard input. >+ The standard input may be disabled and the standard output may be changed to write or append to a local file in the <b>Standard Input and Output</b> pane of the >+ <b>Common</b> tab.</li> >+ <li>When a launch configuration is executed, by default Eclipse will run the launch configuration >+ in the background so that the user may continue interacting with Eclipse. To restrict the user from interacting with Eclipse until the execution has terminated, clear the <b>Launch >+ in background</b> check box at the bottom of the <b>Common</b> tab. .</li> >+</ul> >+ >+<br/> >+ >+ >+<p><strong>Related concepts</strong><br/> >+ <a href="../tasks/trunningmanualtestsuite.htm">Running a manual test</a><br/> >+</p> >+ >+<p><strong>Related tasks</strong><br/> >+ <a href="../tasks/tcreating_test_deployment.htm">Creating a test deployment</a><br/> >+</p> >+ >+<p>(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.</p> >+ >+</div> >+ >+</body> >+ >+</html> >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> >+<p>A new test configuration is required to run a manual test. >+When the test configuration is executed, a test log captures the >+launch of the manual test.</p> >+ >+<p>Open the <b>Run</b> dialog to create the test configuration. >+Right-click on a test suite file in the Test Navigator and select >+<b>Run As</b> > <b>Run</b> from the pop-up menu. >+The <b>Run</b> dialog opens.</p> >+ >+<p>Create the test configuration by selecting the <b>Test</b> entry from the list >+of launch <b>Configurations</b> and clicking <b>New</b>. The test configuration is created and >+by default is named New_configuration. You may edit the default name of the test configuration in the >+<b>Name</b> field at the top of the <b>Run</b> dialog.</p> >+ >+<p>The test configuration requires an association to the manual test and its >+deployment. Select the manual test >+and its deployment for the test configuration. Select the <b>Test</b> tab at the right of the <b>Run</b> dialog >+and complete the following steps:</p> >+ >+<ol> >+ <li>Select the manual test to run. Navigate to and select the manual test in the <b>1. Select test to run</b> pane of the <b>Test</b> tab. >+ </li> >+ <li>Select the deployment for running the manual test. Select the <i>local_deployment</i> deployment in the <b>2. >+ Select a deployment</b> pane of the <b>Test</b> tab.</li> >+ <li> >+ <p>Optionally, you may override the default settings >+ for the generated test log. By default, the test log's name is the same as the manual test and it is saved in the same location >+ as the manual test. Select the <b>Test Logs</b> tab at the >+ right of the <b>Run</b> dialog and complete the following steps:</p> >+ >+ <ul> >+ <li>Clear the <b>Use defaults</b> check box at the top of the <b>Test Logs</b> tab.</li> >+ <li>Edit the default name of the generated test log in the <b>Name</b> field under the <b>Use defaults</b> check box.</li> >+ <li>Select the <b>Override existing test logs resource</b> check box under the <b>Name</b> field to override an existing test log with the same name in the same location. >+ If the check box is cleared, the generated test log will be uniquely named.</li> >+ <li>Edit the default location of the generated test log in the <b>Location</b> pane at the bottom of the <b>Test Logs</b> tab.</li> >+ </ul> >+ </li> >+ <li>Optionally edit the generic launch configuration properties</li> >+ <li>Save the test configuration by clicking the <b>Apply</b> button at the bottom of the <b>Run</b> dialog.</li> >+</ol> >+ >+<p></p> >+ >+<p><strong>Related tasks</strong><br/> >+ <a href="trunningmanualtestsuite.htm">Running a manual test</a><br/> >+ <a href="tcreating_test_deployment.htm">Creating a test deployment</a><br/> >+</p> >+ >+<p><strong>Related reference</strong><br/> >+ <a href="../ref/rmanualcreate.htm">Generic launch configuration properties</a><br/> >+</p> >+ >+<p>(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.</p> >+ >+</div> >+ >+</body> >+ >+</html> >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> >+ >+<br/> >+ >+<p>To prepare to run a manual test, complete the following steps:</p> >+ >+<ol> >+ <li>Open the <b>Test</b> perspective. Select <b>Window</b> > <b>Open Perspective</b> > <b>Other...</b> > <b>Test</b> > <b>OK</b>.</li> >+ <li>Launch the Agent Controller.</li> >+ <li>Optionally create a test deployment.</li> >+</ol> >+ >+<br/> >+ >+<p><strong>Related concepts</strong><br/> >+ <a href="../concepts/cmanualtestoverview.htm">Manual testing with TPTP - overview</a><br/> >+</p> >+ >+<p><strong>Related tasks</strong><br/> >+ <a href="trunningmanualtestsuite.htm">Running a manual test</a><br/> >+ <a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/tasks/tworkwac.html">Working with the Agent Controller</a><br/> >+ <a href="tcreating_test_deployment.htm">Creating a test deployment</a><br/> >+</p> >+ >+<p>(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.</p> >+ >+</div> >+ >+</body> >+ >+</html> >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> >+ >+<p>Run the test configuration by clicking the <b>Run</b> button at the bottom of the <b>Run</b> dialog.</p> >+ >+<p>When a manual test is executed, the <b>Manual Test View</b> is launched on the host as specified in the test deployment associated >+with the execution test launch configuration. The <b>Manual Test View</b> is an independent Standard Widget Toolkit >+window for executing a manual test. </p> >+ >+<p>The <b>Manual Test View</b> displays the manual test as a hierarchal tree at the left of the <b>Manual Test View</b> for viewing and navigation. The executed manual test is displayed at the root with loops and referenced manual tests >+as branches of the manual test tree. Any manual test or loop node in the tree may be expanded and collapsed by selecting the node in the manual test tree and >+selecting <b>View > Expand node</b> and <b>View > Collapse node</b>, respectively. Individual manual test cases are displayed as leaves of the manual test tree. >+Selecting a node in the tree will display the details of that node at the right of the <b>Manual Test View</b>.</p> >+ >+<p> >+At any time during the execution of the manual test, the tester may record a message in the test log by selecting <b>Action > Send message...</b>. The <b>Manual Test View</b> >+may be terminated at any time during the execution of the manual test by selecting <b>File > Exit</b>. >+</p> >+ >+<p>When the <b>Manual Test View</b> initially appears, the tester may optionally capture contextual information on the execution of the manual test; for example, enter the tester's name. Select <b>Start</b> to begin executing the individual manual test cases in the manual test.</p> >+ >+The first manual test case of the manual test is automatically selected. The execution >+steps for the manual test case are displayed at the upper-right of the <b>Manual Test View</b>. After completing the execution steps of the manual test case, >+input the status at the lower-right of the <b>Manual Test View</b>: >+<ul> >+ <li>verdict (<b>pass</b>, <b>fail</b>, <b>error</b> or <b>inconclusive</b>)</li> >+ <li>reason (<b>abort</b>, <b>did not complete</b>, <b>unknown</b>, <b>none</b> or <b>see description</b>) </li> >+ <li>optional contextual information (for example, defect number for failures)</li> >+ <li>attachments (for example, screen captures of a failure state or error message)</li> >+</ul> >+ >+<p> >+To record the status and contextual information in the test log and advance to the next manual test case, select the >+<b>Next</b> button at the lower-right of the <b>Manual Test View</b>. At any time during the execution of the manual test, the tester may advance to the next >+manual test case by selecting <b>View > Select task to execute...</b>. Testers may execute the same manual test case multiple times by navigating to the manual >+test case in the test tree and recording a new status, reason and optional contextual information and attachments.</p> >+ >+<p>When the manual test execution is complete, exit the <b>Manual Test View</b> by selecting <b>File > Exit</b>.</p> >+ >+ >+ >+<p><strong>Related tasks</strong><br /> >+<a href="tcreatingamanualtest.htm">Creating a manual test</a><br/> >+<a href="trunningmanualtestsuite.htm">Running a manual test</a><br /> >+<a href="tanalyzingmanualtestresults.htm">Analyzing manual test results</a><br/> >+<a href="tcreating_test_deployment.htm">Creating a test deployment</a><br /> >+<a href="http://www.eclipse.org/swt/">Standard Widget Toolkit</a><br/> >+</p> >+<p><strong>Related reference</strong><br /> >+<a href="../ref/rmanualcreate.htm">Generic launch configuration properties</a></p> >+ >+ >+<p>(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.</p> >+ >+</div> >+ >+</body> >+ >+</html>
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Actions:
View
|
Diff
Attachments on
bug 110436
:
27475
| 27655