Attachment 27475 Details for Bug 110436 – tptpManualTest_run.htm

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

tptpManualTest_run.htm

tptpManualTest_run.htm (text/xml), 10.16 KB, created by Paul Slauenwhite

on 2005-09-23 17:37:37 EDT

(hide)

Description:

Filename:

MIME Type:

Creator: Paul Slauenwhite

Created: 2005-09-23 17:37:37 EDT

Size: 10.16 KB

patch

obsolete

><?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>Preparation Steps</h2>
>
> 
>
>In preparation for running a manual test, complete the following steps:
>
><ol>
>	<li>Open the Test perspective:
>		<ul>
>			<li>Select Window &gt; Open Perspective &gt; Other... &gt; Test &gt; OK.</li>
>		</ul>
>	</li>
>	<li>Launch the Agent Controller:
>		<ul>
>			<li>If the Agent Controller is not running, follow the instructions to launch the <a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/tasks/tworkwac.html">Agent Controller</a>.</li>
>		</ul>
>	</li>
></ol>
>
> 
>
><h2>Running a Manual Test</h2>
>
> 
>
><h4>Create a Test Launch Configuration</h4>
>
> 
>
>A new test launch configuration is required to run a manual test.
>
>Open the Run dialog for creating the test launch configuration. Right-click on the exampleManualTest 
>test suite file in the Test Navigator and select Run As &gt; Run from the context menu. Alternatively, select 
>Run &gt; Run.... This will show the Run dialog.
>
>Create the test launch configuration by selecting the Test entry from the list 
>of launch Configurations and clicking New. The test launch configuration is created and 
>by default named New_configuration. You may edit the default name of the test launch configuration in the 
>Name field at the top of the Run dialog.
>
>The test launch configuration requires an association to the manual test and its <a href="../tasks/tcreating_test_deployment.htm">deployment</a>. Select the manual test 
>and its deployment for the test launch configuration. Select the Test tab at the right of the Run dialog 
>and complete the following steps:
>
><ol>
>	<li>Select the manual test to run:
>		<ul>
>			<li>Navigate to and select the exampleManualTest manual test in the 1. Select test to run pane of the Test tab.</li>
>		</ul>
>	</li>
>	<li>Select the deployment for running the manual test:
>		<ul>
>			<li>Select the local_deployment deployment in the 2. Select a deployment pane of the Test tab.</li>
>		</ul>
>	</li>
></ol>
>
>When the test launch configuration is executed, a test log capturing the launch of the manual test. By default, the test log's name is the same
>as the manual test (for example, exampleManualTest) and it is saved in the same location as the manual test. Optionally, you may override the default settings 
>for the generated test log. Select the Test Logs tab at the right of the Run dialog and complete the following steps:
>
><ol>
>	<li>Override the default settings for the generated test log:
>		<ul>
>			<li>Deselect the Use defaults check box at the top of the Test Logs tab.</li>
>			<li>Edit the default name of the generated test log in the Name field under the Use defaults check box.</li>
>			<li>Select the Override existing test logs resource check box under the Name field to override an existing test log with the same name in the same location. 
>			If deselected, the generated test log will be uniquely named.</li>
>			<li>Edit the default location of the generated test log in the Location pane at the bottom of the Test Logs tab.</li>
>		</ul>
>	</li>
></ol>
>
>Eclipse provides the Common tab at the right of the Run dialog for editing various generic launch configuration properties. Select the Common 
>tab at the right of the Run dialog to edit the following generic launch configuration properties:
>
><ul>
>	<li>When the launch configuration is saved (for example, clicking either the Apply or Run buttons at the bottom of the Run dialog), a 
>launch configuration file (for example, .launch) is created and saved. By default, the launch configuration file is saved in the workspace's .metadata 
>directory. The location for the generated launch configuration file may be changed to any directory in the workspace in the Save as pane of the Common tab.</li>
>	<li>When rerunning a launch configuration, a shortcut may be associated with one or more favorites tool bar menus (for example, Run, Debug or Profiling) in the Display in favorites menu 
>	pane of the Common tab.</li>
>	<li>When a launch configuration is executed (for example, clicking the Run button at the bottom of the Run dialog), the Console view 
>	is used for rendering standard output data and reading standard input data. By default, the encoding of the Console view is encoding for the
>	local platform. The encoding of the Console view may be changed to any valid encoding in the Console Encoding pane of the Common tab.</li>
>	<li>When a launch configuration is executed (for example, clicking the Run button at the bottom of the Run dialog), the standard output and standard input are
>	may be used display output data and read input data, respectively. By default, the Console view is used for both the standard output and standard input. 
>	The standard input may be disabled and the standard output may be changed to write or append to a local file in the Standard Input and Output pane of the 
>	Common tab.</li>
>	<li>When a launch configuration is executed (for example, clicking the Run button at the bottom of the Run dialog), by default Eclipse will run the launch configuration 
>	in the background as a non-blocking execution so the user may continue interaction with Eclipse. The launch configuration may be executed as a blocking execution, thereby restricting 
>	the user from interacting with Eclipse until the execution has terminated by deselecting the Launch in background check box at the bottom of the Common tab.</li>
></ul>
>
>Finally, save the test launch configuration by clicking the Apply button at the bottom of the Run dialog.</a>
>
> 
>
><h4>Run the Test Launch Configuration</h4>
>
>Run the test launch configuration by clicking the Run button at the bottom of the Run dialog.</a>
>
>When a manual test is executed, the Manual Test View is launched on the host as specified in the <a href="../tasks/tcreating_test_deployment.htm">deployment</a> associated 
>with the execution test launch configuration. The Manual Test View is an independent <a href="http://www.eclipse.org/swt/">Standard Widget Toolkit (SWT)</a> 
>window for executing a manual test. At any time during the execution of the manual test, the tester may record a message in the test log by selecting Action &gt; Send message.... The Manual Test View 
>may be terminated at any time during the execution of the manual test by selecting File &gt; Exit.
>
>When the Manual Test View initial appears, the tester may optionally capture contextual information on the execution of the manual test. 
>For example, the tester's name. Select Start to start executing the individual manual test cases in the manual test.
>
>The Manual Test View displays the manual test as a hierarchal tree at the left of the Manual Test View for viewing and navigation. The manual 
>test tree may be expanded and collapsed by selecting View &gt; Expand all and View &gt; Collapse all, repetitively. 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 manual test tree may be expanded and collapsed by selecting the node in the manual test tree and
>selecting View &gt; Expand node and View &gt; Collapse node, respectively. Individual manual test cases are displayed as leaves of the manual test tree. 
>Selecting node in the manual test tree will display the details of that node at the right of the Manual Test View. 
>
>The first manual test case (for example, Instruction Set A - invocation in the exampleManualTest manual test) of the of the manual test is automatically selected. The execution 
>steps for the manual test case are displayed at the upper-right of the Manual Test View. After completing the execution steps of the manual test case, 
>input the status (for example pass, fail, error or inconclusive), reason (for example abort, did not complete, unknown, none or see description), 
>and optional contextual information (for example, defect number for failures) and attachments (for example, screen captures of a failure state or error message) at the lower-right of the Manual Test View. To record the status and contextual information in the test log and advance to the next manual test case, select the 
>Next button at the lower-right of the Manual Test View. At any time during the execution of the manual test, the tester may advance to the next 
>manual test case by selecting View &gt; Select task to execute.... Testers may execute the same manual test case multiple times by navigating to the manual
>test case in the test tree and recording a new status, reason and optional contextual information and attachments.
> 
>When the manual test execution is complete, exit the Manual Test View by selecting File &gt; Exit.
>
> 
>
>(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
>
></div>
>
></body>
>
></html>

Actions: View

Attachments on bug 110436: 27475 | 27655