Attachment #102903 for bug #213622

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

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

Lines 38-44 Link Here

(-)tasks/tcreatingamanualtest.htm (-1 / +1 lines)
38	<li>Expand the <b>Test</b> folder, then select <b>TPTP Manual Test</b>.</li>	38	<li>Expand the <b>Test</b> folder, then select <b>TPTP Manual Test</b>.</li>
39	<li>Click <b>Next</b>, select the location (<i>generalProject</i>), and name the manual test suite, for example, <i>exampleManualTest</i>.</li>	39	<li>Click <b>Next</b>, select the location (<i>generalProject</i>), and name the manual test suite, for example, <i>exampleManualTest</i>.</li>
40	<li>Click <b>Next</b> and optionally provide a description for the manual test suite. Click <b>Finish</b>.</li>	40	<li>Click <b>Next</b> and optionally provide a description for the manual test suite. Click <b>Finish</b>.</li>
41	<li>A manual test suite file (exampleManualTest.testsuite) will be created, becomes visible in the Test Navigator and opens in the Manual Test editor.</li>	41	<li>The <b>Confirm Open Editor</b> dialog may appear (see the <b>Window</b> > <b>Preferences...</b> > <b>Test</b> > <b>Open Editor</b> preference), confirming if the new manual test suite is to be opened in the Manual Test editor.</li>
42	</ol>	42	</ol>
43		43
44	<p><strong>Related tasks</strong><br />	44	<p><strong>Related tasks</strong><br />




<head>
<!-- 
/**********************************************************************
 * Copyright (c) 2000, 2008 IBM Corporation.
 * All rights reserved.   This content
 * is made available under the terms of the Eclipse Public License v1.0
 * which accompanies this distribution, and is available at

typically typed based on what is expected by the application-under-test.</p>
</li>
</ul>

to a spreadsheet. Right-clicking on the grid opens the pop-up menu that you
use to add or maintain the datapool structural elements described above. You
add data by typing in a cell.<br /><img src="../images/dpeditpopup.gif" alt=""/><br /></p>
<p>When you create a datapool, you have the option of initializing the new
datapool with data contained in an existing comma-separated value text file (CSV)
that you created with a spreadsheet editor or with some external or custom

individual records but provides no means of generating large amounts of typed
data.
</p>

</div>

<div>




<p> </p>
<p>Open the performance test in the TPTP URL Test editor:</p>
<img src="../images/editOverview.jpg" alt=""/><p>The test opens in the <span class="uicontrol">Overview</span> tab (see the bottom
border) with the four edit areas (<span class="uicontrol">TPTP URL Test</span> and <span class="uicontrol">Source
Information</span> on the left and <span class="uicontrol">Deployment</span> and <span class="uicontrol">HTTP Requests</span> on
the right) expanded. You switch to the other edit panes by clicking the appropriate
tab. </p>
<p>The <span class="uicontrol">TPTP URL Test</span> area displays the test's
name, an optional description, the test's type, and the name of the file containing
the test. Information appearing in boxes can be edited. The <span class="uicontrol">Name</span> box
under <span class="uicontrol">TPTP URL Test</span> displays the name of the
test. You can change the name. If you do, the
name displayed in the Test Navigator changes also but the filename containing
the test does not change. In this example, the test's name, as listed in the

executed simultaneously.  That is, the invocation is executed at the same time as the sibling invocations and loops.</p>
</div>

<div>
<p>
<b class="parentlink">Parent topic:</b> <a href="../concepts/ctestwithhyades.htm" title="The Eclipse test and performance tools platform (TPTP) supports automated performance testing of HTTP applications.">Performance Testing with TPTP</a><br />
</p>
</div>
</body>
</html>





<!-- 
/**********************************************************************
 * Copyright (c) 2000, 2008 IBM Corporation.
 * All rights reserved.   This content
 * is made available under the terms of the Eclipse Public License v1.0
 * which accompanies this distribution, and is available at

	<li>Select <b>File</b> &gt; <b>New</b> &gt; <b>Other</b>.</li>
	<li>Expand <b>Test</b>. Select <b>TPTP JUnit Test</b>.</li>
	<li>Click <b>Next</b> to launch the <b>New JUnit Test Definition</b> dialog. 
	Identify the Source folder (<i>javaProject/src</i>), the Package
	(<i>junit.samples</i>), and the name to be assigned to the JUnit Test source code
	(<i>JUnit_src</i>).
	</li>
	<li>Click <b>Next</b>. The <b>New JUnit Test Definition</b> dialog launches.</li>
	<li>Enter the parent folder (<i>javaProject/src/junit/samples</i>) and Name (<i>JUnit_src</i>).</li>
	<li>Optionally click <b>Next</b> and provide a description of the JUnit test definition.</li>
	<li>Click on <b>Finish</b>.</li>
	<li>The <b>Confirm Open Editor</b> dialog may appear (see the <b>Window</b> &gt; <b>Preferences...</b> &gt; <b>Test</b> &gt; <b>Open Editor</b> preference), confirming if the new JUnit test suite is to be opened in the JUnit Test editor.</li>	
</ol>
<p>Note that the second and third pages of the wizard are optional (that is, you can finish the wizard at the first page). Also, the difference between the information requested in page 1 and page 2 is as follows: the first page asks for the name and location of the source code, while the second one asks for the name and location of the TPTP Test (the model). By default, they are identical.</p>
</body>




<html lang="en-us" xml:lang="en-us">
<!-- 
/**********************************************************************
 * Copyright (c) 2006, 2008 IBM Corporation.
 * All rights reserved.   This content
 * is made available under the terms of the Eclipse Public License v1.0
 * which accompanies this distribution, and is available at

</head>
<body><a name="associating_defects.dita"><!-- --></a>
<h1 class="topictitle1">Associating defects with a test log</h1>
<div>

<p>The Test Log viewer is integrated with a Web-based Bugzilla defect tracking
system used to submit, search, and open defects in the internal Web Browser.  Existing 
defects may be associated with individual execution events in the test log.</p>

<p>By default, the Test Log viewer is integrated with the Web-based 
<a href="https://bugs.eclipse.org/bugs/">Eclipse Bugzilla</a> defect tracking system. To use 
another Web-based Bugzilla defect tracking system, you can configure in the 
Test Log viewer preferences:</p>

<ol>
 	<li>Select <b>Window</b> &gt; <b>Preferences...</b> from the file menu.</li>
	<li>Select the <b>Test</b> &gt; <b>Test Log viewer</b> preference page.</li>
	<li>Configure the <b>Submit URL</b>, <b>Search URL</b>, and <b>Open URL</b> links for the Web-based Bugzilla defect tracking system.</li>
	<li>Click <b>OK</b> to save the preferences.</li>
tracking system to find it. Click <span class="uicontrol">Search</span>. </span> The
defect tracking tool's Search page opens, enabling you to search for the defect.</li>
</ol>

<p>Defects may be associated with any execution event in the Events page.</p>

<p>Add, open, and remove a defect:</p>

<ol>
 	<li>Select execution event in the <b>Events</b> tree of the Events page and expand <b>Defects</b>.</li>
	<li>To add a defect to the execution event, click <b>Add...</b>, enter the defect number, and click <b>OK</b>.</li>
	<li>The defect is associated with the execution event and the defect number is displayed as a link.</li>
	<li>To open the defect, click the defect number link, and view the defect in the internal Web Browser.</li>
	<li>To remove the defect, click the remove link to the right of the defect number link.</li>
</ol>

<p>Submit a new defect:</p>

<ol>
 	<li>Select execution event in the <b>Events</b> tree of the Events page and expand <b>Defects</b>.</li>
	<li>Click <b>Submit...</b> and enter the defect details in the internal Web Browser according to the procedure for the Web-based Bugzilla defect tracking system.</li>
</ol>

<p>Search for an existing defect:</p>

<ol>
 	<li>Select execution event in the <b>Events</b> tree of the Events page and expand <b>Defects</b>.</li>
	<li>Click <b>Search...</b> and enter the search details in the internal Web Browser according to the procedure for the Web-based Bugzilla defect tracking system.</li>
</ol>

</div>
</body>
</html>




<html lang="en-us" xml:lang="en-us">
<!-- 
/**********************************************************************
 * Copyright (c) 2006, 2008 IBM Corporation.
 * All rights reserved.   This content
 * is made available under the terms of the Eclipse Public License v1.0
 * which accompanies this distribution, and is available at

(<img src="../images/th_vertical.gif" alt="Vertical orientation button" />) to display information horizontally or vertically.</span></li>
</ol>
</div>
</body>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/c_viewingtestresults.html" title="After running a test, the test results for the events are saved in a test log. Use the Test Log viewer to examine test results and events.">Analyzing test results</a></div>
</div>
</div></body>
</html>

Lines 46-51 Link Here

(-)tasks/tcreatetestdeployment.htm (+1 lines)
46	src="../images/downArrow.gif" width="16" height="16" alt="Image of down arrow."/>). Selected pairs of test artifacts and test locations can be removed	46	src="../images/downArrow.gif" width="16" height="16" alt="Image of down arrow."/>). Selected pairs of test artifacts and test locations can be removed
47	(<b>Remove</b>), moved up (<b>Up</b>), or moved down (<b>Down</b>).</li>	47	(<b>Remove</b>), moved up (<b>Up</b>), or moved down (<b>Down</b>).</li>
48	<li>Click <b>Finish</b> to create the test deployment.</li>	48	<li>Click <b>Finish</b> to create the test deployment.</li>
		49	<li>The <b>Confirm Open Editor</b> dialog may appear (see the <b>Window</b> > <b>Preferences...</b> > <b>Test</b> > <b>Open Editor</b> preference), confirming if the new test deployment is to be opened in the Deployment editor.</li>
49	</ol>	50	</ol>
50		51
51	<p>	52	<p>

Lines 3-9 Link Here

(-)tasks/tdatapool.htm (-4 / +5 lines)
3	<html lang="en-us" xml:lang="en-us">	3	<html lang="en-us" xml:lang="en-us">
4	<!--	4	<!--
5	/**********************************************************************	5	/**********************************************************************
6	* Copyright (c) 2000, 2007 IBM Corporation.	6	* Copyright (c) 2000, 2008 IBM Corporation.
7	* All rights reserved. This content	7	* All rights reserved. This content
8	* is made available under the terms of the Eclipse Public License v1.0	8	* is made available under the terms of the Eclipse Public License v1.0
9	* which accompanies this distribution, and is available at	9	* which accompanies this distribution, and is available at
Lines 45-61 Link Here
45		45
46	<div>	46	<div>
47	<blockquote>	47	<blockquote>
		48	<div class="ulchildlink"><b><a href="../concepts/cdatapools.htm">Datapool structure</a></b><br />
		49	Datapools provide variable data to your tests during execution.</div>
48	<div class="ulchildlink"><b><a href="../tasks/tcreatedp.htm">Creating a datapool</a></b><br />	50	<div class="ulchildlink"><b><a href="../tasks/tcreatedp.htm">Creating a datapool</a></b><br />
49	Datapools contain data that tests can use when they run.</div>	51	Datapools contain data that tests can use when they run.</div>
50	<div class="ulchildlink"><b><a href="../tasks/topendp.htm">Opening a datapool</a></b><br />	52	<div class="ulchildlink"><b><a href="../tasks/topendp.htm">Opening a datapool</a></b><br />
51	Inspect or modify the contents of a datapool.</div>	53	Inspect or modify the contents of a datapool.</div>
52	<div class="ulchildlink"><b><a href="../tasks/teditdp.htm">Editing a datapool</a></b><br />	54	<div class="ulchildlink"><b><a href="../tasks/teditdp.htm">Editing a datapool</a></b><br />
53	In a manner similar to editing a spreadsheet, you can add, modify or remove data from a datapool.</div>	55	In a manner similar to editing a spreadsheet, you can add, modify or remove data from a datapool.</div>
		56	<div class="ulchildlink"><b><a href="../samples/saccessdp.htm">Tutorial: Accessing a datapool from a JUnit test</a></b><br />
		57	Create and access a datapool from an example test application.</div>
54	</blockquote>	58	</blockquote>
55		59
56	<p>
57	<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 />
58	</p>
59	</div>	60	</div>
60	</body>	61	</body>
61	</html>	62	</html>




<html lang="en-us" xml:lang="en-us">
<!-- 
/**********************************************************************
 * Copyright (c) 2005, 2008 IBM Corporation.
 * All rights reserved.   This content
 * is made available under the terms of the Eclipse Public License v1.0
 * which accompanies this distribution, and is available at

<div class="section">Alternatively, locate in the Test Navigator the test log file and
then double-click it.</div>
</div>
</body>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/c_viewingtestresults.html" title="After running a test, the test results for the events are saved in a test log. Use the Test Log viewer to examine test results and events.">Analyzing test results</a></div>
</div>
</div></body>
</html>

Lines 35-40 Link Here

(-)tasks/tcreateartifact.htm (+1 lines)
35	<li>Optionally, provide a description for the test artifact and click <b>Next</b>.</li>	35	<li>Optionally, provide a description for the test artifact and click <b>Next</b>.</li>
36	<li>Select the associated test assets, such as test suites and datapools.</li>	36	<li>Select the associated test assets, such as test suites and datapools.</li>
37	<li>Click <b>Finish</b> to create the test artifact.</li>	37	<li>Click <b>Finish</b> to create the test artifact.</li>
		38	<li>The <b>Confirm Open Editor</b> dialog may appear (see the <b>Window</b> > <b>Preferences...</b> > <b>Test</b> > <b>Open Editor</b> preference), confirming if the new test artifact is to be opened in the Artifact editor.</li>
38	</ol>	39	</ol>
39		40
40	<p>	41	<p>




<link rel="stylesheet" type="text/css" href="../css/swg_info_common.css" />
<title>Editing a datapool</title>
</head>
<body>
<div>
<h1 class="topictitle1">Editing a datapool</h1>
<p>In a manner similar to editing a spreadsheet, you can add, modify
or remove data from a datapool.</p>
<div class="skipspace"><p>When you right-click on the datapool editing grid, the following pop up menu appears. <br />
<img src="../images/dpeditpopup.gif" alt="" /><br /><br />
The pop up menu allows you to add records or variables. Records are added automatically. If you choose &quot;Insert variable&quot; the following dialog appears. The <b>Insert</b> drop down option specifies the position of the new column with respect to other datapool columns.</p>
<img src="../images/columndlg.png" alt=""/>

<p>The datapool editor is a grid similar to a spreadsheet.</p>

<p>In a manner similar to editing a spreadsheet, you can add, modify or remove data from a datapool.</p>

<p>When you right-click on the datapool editing grid, a context menu appears to add, edit, and remove a 
record or variable, and cut, copy, and paste the selected cell.</p>

<p>If you insert a variable, the name, type, and relative position of the new variable is required.  
In addition, you may encrypt the new variable, which requires a password.</p>

<p>The Datapool editor's overview tab allows you to edit variables and equivalence classes.</p> 

<p>
	href="../tasks/tdatapool.htm"
	title="If you associate a value in a test with a datapool column, the test substitutes column data for that value when it runs.">Providing
tests with variable data</a><br />
<br />
<strong>Related concepts</strong><br />
	<a href="../samples/saccessdp.htm">Tutorial: Creating a datapool driven JUnit test application</a><br />
<strong><br />
Related tasks</strong><br />
	<a href="../tasks/tcreatedp.htm">Creating a datapool</a><br />
</p>

</div>
</body>
</html>




<html lang="en-us" xml:lang="en-us">
<!-- 
/**********************************************************************
 * Copyright (c) 2004, 2008 IBM Corporation.
 * All rights reserved.   This content
 * is made available under the terms of the Eclipse Public License v1.0
 * which accompanies this distribution, and is available at

</ol>
</div>

<div>
<p>
<b class="parentlink">Parent topic:</b> <a href="../tasks/tdatapool.htm" title="If you associate a value in a test with a datapool column, the test substitutes column data for that value when it runs.">Providing tests with variable data</a><br />
</p>
</div>
</body>
</html>




<!DOCTYPE html
  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<!-- 
/**********************************************************************
 * Copyright (c) 2006, 2007 IBM Corporation.
 * All rights reserved.   This content
 * is made available under the terms of the Eclipse Public License v1.0
 * which accompanies this distribution, and is available at
 * http://www.eclipse.org/legal/epl-v10.html        
 * $Id: t_submitting_defects.html,v 1.3 2007/05/03 14:33:14 paules Exp $
 *
 * Contributors:
 * IBM - Initial contribution
 **********************************************************************/  
 -->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252" />
<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="Submitting defects" />
<meta name="abstract" content="The Test Log viewer provides a direct link to a defect tracking system that you can use to submit defects as you find them." />
<meta name="description" content="The Test Log viewer provides a direct link to a defect tracking system that you can use to submit defects as you find them." />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="submitting_defects" />
<meta name="DC.Language" content="en-us" />
<link rel="stylesheet" type="text/css" href="../css/book.css" />
<link rel="stylesheet" type="text/css" href="../css/ibmdita.css" />
<title>Submitting defects</title>
</head>
<body><a name="submitting_defects"><!-- --></a>
<h1 class="topictitle1">Submitting defects</h1>
<div><p>The Test Log viewer provides a direct link to a defect tracking
system that you can use to submit defects as you find them.</p>
<div class="p">This feature uses the Bugzilla Web interface by default. If your application
uses another defect tracking tool, then that tool must be available with your
Eclipse installation.</div>
<div class="section">To submit a defect for tracking, perform the following steps:</div>
<ol><li class="stepexpand"><span>Make sure that the desired test log is open. </span></li>
<li class="stepexpand"><span>Click the <span class="uicontrol">Events</span> tab.</span></li>
<li class="stepexpand"><span>Under <span class="wintitle">Events</span>, select the execution event with
which to associate the new defect.</span></li>
<li class="stepexpand"><span>Under <span class="wintitle">Defects</span>, click <span class="uicontrol">Submit</span>.</span> The defect tracking system opens. Log in (if required) and then
submit the defect according to the procedure for your defect-tracking tool. </li>
</ol>
<div class="section">In the test log, the new defect number is shown as a
link; click this link to return to the record in the defect database.</div>
</div>
<div></div></body>
</html>




	<li>Expand the <b>Test</b> folder, then select <b>TPTP URL Test</b>.</li>
	<li>Click <b>Next</b>, select the location (the project created in step 1), and name the performance test suite, for example, <i>examplePerformanceTest</i>.</li>
	<li>Click <b>Next</b> and optionally provide a description for the performance test suite. Click <b>Finish</b>.</li>
    <li>The <b>Confirm Open Editor</b> dialog may appear (see the <b>Window</b> &gt; <b>Preferences...</b> &gt; <b>Test</b> &gt; <b>Open Editor</b> preference), confirming if the new performance test suite is to be opened in the URL Test editor.</li>
</ol>
</div>

<div>
<p>
<b class="parentlink">Parent topic:</b> <a href="../concepts/ctestwithhyades.htm" shape="rect" title="The Eclipse test and performance tools platform (TPTP) supports automated performance testing of HTTP applications.">Performance Testing with TPTP</a><br clear="none" />
</p>
</div>

</body>

</html>

Lines 66-75 Link Here

(-)tasks/tptpJUnitTest_importing.htm (-4 / +1 lines)
66	<li>	66	<li>
67	Navigate to the required files and then click on <b>Finish</b>.	67	Navigate to the required files and then click on <b>Finish</b>.
68	</li>	68	</li>
69	<li>	69	<li>The <b>Confirm Open Editor</b> dialog may appear (see the <b>Window</b> > <b>Preferences...</b> > <b>Test</b> > <b>Open Editor</b> preference), confirming if the new JUnit test suite is to be opened in the JUnit Test editor.</li>
70	The outcome of a successful import operation will be a TPTP
71	JUnit Test File associated with the imported package or class.
72	</li>
73	</ul>	70	</ul>
74		71
75	<p>Note that the import wizard shows all existing JUnit test cases in the workspace that have not already been imported to TPTP. If this list is empty, then it means that either no JUnit tests were found in the workspace, or that all existing JUnit test classes have already been imported to TPTP.</p>	72	<p>Note that the import wizard shows all existing JUnit test cases in the workspace that have not already been imported to TPTP. If this list is empty, then it means that either no JUnit tests were found in the workspace, or that all existing JUnit test classes have already been imported to TPTP.</p>




		<td>Time Frame Historic<sup>1</sup></td>
		<td>Report with all of the execution results for each selected test within a specified period of time.</td>
    </tr>
    <tr>
		<td>Test Pass Report<sup>1</sup></td>
		<td>Report with only the most recent execution results for each selected test within a specified period of time.</td>
    </tr>
  </tbody>
</table>


<p>Configure the fonts used when generating a test report:</p>
<ol>
 	<li>Select <b>Window</b> &gt; <b>Preferences...</b> from the file menu.</li>
	<li>Select the <b>Test</b> &gt; <b>Test Reports</b> &gt; <b>Fonts</b> preference page.</li>
	<li>Configure the fonts used when generating a test report.</li>
	<li>Click <b>OK</b> to save the preferences.</li>
</ol>

  <li>Provide the parent folder and the name for the test report and click <b>Next</b>.</li>
  <li>Optionally, provide the report window (start and end data and time) for the test report.</li>
  <li>Click <b>Finish </b> to generate the test report.</li>
  <li>The <b>Confirm Open Editor</b> dialog may appear (see the <b>Window</b> &gt; <b>Preferences...</b> &gt; <b>Test</b> &gt; <b>Open Editor</b> preference), confirming if the new test report is to be opened in the internal Web Browser.</li>	
</ol>

</body>




<html lang="en-us" xml:lang="en-us">
<!-- 
/**********************************************************************
 * Copyright (c) 2004, 2008 IBM Corporation.
 * All rights reserved.   This content
 * is made available under the terms of the Eclipse Public License v1.0
 * which accompanies this distribution, and is available at

<div class="skipspace">To generate a test's source code:</div>
<ol><li class="skipspace"><span>In the Test Navigator, right-click the test to be run and select <span class="uicontrol">Generate</span>. </span> The <span class="uicontrol">JUnit Test Definition Code Generation</span> dialog
box opens.</li>
<li class="skipspace"><span>In the <span class="uicontrol">Source Folder</span> field, accept the default
or click <span class="uicontrol">Browse</span> to select the source folder in a Java project in which
to store the test code.</span></li>
<li class="skipspace"><span>In the <span class="uicontrol">Package Name</span> field, accept the
default or click <span class="uicontrol">Browse</span> to select the package the selected Java project 
in which to store the test code.</span></li>
<li class="skipspace"><span>In the <span class="uicontrol">Class Name</span> field, specify the name of the test code.</span></li>
<li class="skipspace"><span>Click <span class="uicontrol">Finish</span>.</span></li>
</ol>
</div>

<div>
<p>
<b class="parentlink">Parent topic:</b> <a href="../concepts/ctestwithhyades.htm" title="The Eclipse test and performance tools platform (TPTP) supports automated performance testing of HTTP applications.">Performance Testing with TPTP</a><br />
</p>
</div>
</body>
</html>

Lines 38-43 Link Here

(-)tasks/tcreatelocation.htm (+1 lines)
38	<li>Enter the host name or IP address of the target host. By default, <i>localhost</i> is entered. Test the	38	<li>Enter the host name or IP address of the target host. By default, <i>localhost</i> is entered. Test the
39	connection to the target host by clicking the <b>Test Connection</b> link<sup>1</sup>.</li>	39	connection to the target host by clicking the <b>Test Connection</b> link<sup>1</sup>.</li>
40	<li>Click <b>Finish</b> to create the test location.</li>	40	<li>Click <b>Finish</b> to create the test location.</li>
		41	<li>The <b>Confirm Open Editor</b> dialog may appear (see the <b>Window</b> > <b>Preferences...</b> > <b>Test</b> > <b>Open Editor</b> preference), confirming if the new test location is to be opened in the Location editor.</li>
41	</ol>	42	</ol>
42		43
43	<p>[1] The <a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/concepts/ac/c_ac_ovr.html">Agent Controller</a> or	44	<p>[1] The <a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/concepts/ac/c_ac_ovr.html">Agent Controller</a> or

Lines 71-77 Link Here

(-)tasks/tcreateperformancetestreports.htm (-1 / +2 lines)
71	<p>Configure the fonts used when generating a performance test report:</p>	71	<p>Configure the fonts used when generating a performance test report:</p>
72	<ol>	72	<ol>
73	<li>Select <b>Window</b> > <b>Preferences...</b> from the file menu.</li>	73	<li>Select <b>Window</b> > <b>Preferences...</b> from the file menu.</li>
74	<li>Select the report <b>Test</b> > <b>Test Reports</b> > <b>Fonts</b> preference page.</li>	74	<li>Select the <b>Test</b> > <b>Test Reports</b> > <b>Fonts</b> preference page.</li>
75	<li>Configure the fonts used when generating a performance test report.</li>	75	<li>Configure the fonts used when generating a performance test report.</li>
76	<li>Click <b>OK</b> to save the preferences.</li>	76	<li>Click <b>OK</b> to save the preferences.</li>
77	</ol>	77	</ol>
Lines 83-88 Link Here
83	<li>Provide the parent folder and the name for the performance test report and click <b>Next</b>.</li>	83	<li>Provide the parent folder and the name for the performance test report and click <b>Next</b>.</li>
84	<li>Optionally, provide the report window (start and end data and time) for the performance test report.</li>	84	<li>Optionally, provide the report window (start and end data and time) for the performance test report.</li>
85	<li>Click <b>Finish </b> to generate the performance test report.</li>	85	<li>Click <b>Finish </b> to generate the performance test report.</li>
		86	<li>The <b>Confirm Open Editor</b> dialog may appear (see the <b>Window</b> > <b>Preferences...</b> > <b>Test</b> > <b>Open Editor</b> preference), confirming if the new performance test report is to be opened in the internal Web Browser.</li>
86	</ol>	87	</ol>
87		88
88	</body>	89	</body>




<html lang="en-us" xml:lang="en-us">
<!-- 
/**********************************************************************
 * Copyright (c) 2004, 2008 IBM Corporation.
 * All rights reserved.   This content
 * is made available under the terms of the Eclipse Public License v1.0
 * which accompanies this distribution, and is available at

	</ul>
	</li><li class="skipspace"><span>Click <span class="uicontrol">Finish</span>.</span> If you specified initial datapool dimensions, which may conflict with the CSV file dimensions, a dialog appears. Click <b>Yes</b> to use the dimensions of the CSV file. Click <b>No</b> to use the specified initial dimensions (and possibly truncate the CSV file data). The Datapool editor appears, showing the
	datapool's first equivalence class. <br />
	<img src="../images/dpeditpopup.gif" alt=""/><br />
	</li>
	<li class="skipspace">The <b>Confirm Open Editor</b> dialog may appear (see the <b>Window</b> &gt; <b>Preferences...</b> &gt; <b>Test</b> &gt; <b>Open Editor</b> preference), confirming if the new datapool is to be opened in the Datapool editor.<br />
	</li>
	
</ol>
<div class="skipspace"><br />For instructions
on how to add data to or edit the new datapool, go to <a


<div>
<p>
<b class="parentlink">Parent topic:</b> <a href="../tasks/tdatapool.htm" title="If you associate a value in a test with a datapool column, the test substitutes column data for that value when it runs.">Providing tests with variable data</a><br />
<br />
<strong>Related concepts</strong><br />
	<a href="../samples/saccessdp.htm">Tutorial: Creating a datapool driven JUnit test application</a><br />
<br />

Lines 3-9 Link Here

(-)ref/r_testlog_toolbar.html (-2 / +9 lines)
3	<html lang="en-us" xml:lang="en-us">	3	<html lang="en-us" xml:lang="en-us">
4	<!--	4	<!--
5	/**********************************************************************	5	/**********************************************************************
6	* Copyright (c) 2006, 2007 IBM Corporation.	6	* Copyright (c) 2006, 2008 IBM Corporation.
7	* All rights reserved. This content	7	* All rights reserved. This content
8	* is made available under the terms of the Eclipse Public License v1.0	8	* is made available under the terms of the Eclipse Public License v1.0
9	* which accompanies this distribution, and is available at	9	* which accompanies this distribution, and is available at
Lines 77-81 Link Here
77	the Events page.</p>	77	the Events page.</p>
78	</div>	78	</div>
79	</div>	79	</div>
80	<div></div></body>	80
		81	<p>
		82	<b>Related tasks</b><br/>
		83	<a href="../tasks/t_searching_testlogs.html">Searching a test log</a><br/>
		84	<a href="../tasks/t_associating_defects.html">Associating defects with a test log</a><br/>
		85	</p>
		86
		87	</body>
81	</html>	88	</html>

Lines 3-9 Link Here

(-)ref/r_testlog_overview.html (-4 / +13 lines)
3	<html lang="en-us" xml:lang="en-us">	3	<html lang="en-us" xml:lang="en-us">
4	<!--	4	<!--
5	/**********************************************************************	5	/**********************************************************************
6	* Copyright (c) 2006, 2007 IBM Corporation.	6	* Copyright (c) 2006, 2008 IBM Corporation.
7	* All rights reserved. This content	7	* All rights reserved. This content
8	* is made available under the terms of the Eclipse Public License v1.0	8	* is made available under the terms of the Eclipse Public License v1.0
9	* which accompanies this distribution, and is available at	9	* which accompanies this distribution, and is available at
Lines 59-66 Link Here
59	<dd>Displays the path and filename of the test suite file that was run.</dd>	59	<dd>Displays the path and filename of the test suite file that was run.</dd>
60	</dl>	60	</dl>
61	<dl><dt class="dlterm"><span class="uicontrol">Host name</span></dt>	61	<dl><dt class="dlterm"><span class="uicontrol">Host name</span></dt>
62	<dd>Displays the name of the computer on which the test was run.</dd>	62	<dd>Displays the name of the computer on which the test was run.</dd></dl>
63	</dl>	63	<dl><dt class="dlterm"><span class="uicontrol">Deployment (optional)</span></dt>
		64	<dd>Displays the name and link to the test deployment that was run.</dd></dl>
		65	<dl><dt class="dlterm"><span class="uicontrol">Location (optional)</span></dt>
		66	<dd>Displays the name and link to the test location that was run.</dd></dl>
64	</dd>	67	</dd>
65	</dl>	68	</dl>
66	<dl><dt class="dlterm"><span class="uicontrol">Verdict Summary</span></dt>	69	<dl><dt class="dlterm"><span class="uicontrol">Verdict Summary</span></dt>
Lines 82-86 Link Here
82	page.</p>	85	page.</p>
83	</div>	86	</div>
84	</div>	87	</div>
85	<div></div></body>	88
		89	<p>
		90	<b>Related tasks</b><br/>
		91	<a href="../tasks/t_searching_testlogs.html">Searching a test log</a><br/>
		92	</p>
		93
		94	</body>
86	</html>	95	</html>




<html lang="en-us" xml:lang="en-us">
<!-- 
/**********************************************************************
 * Copyright (c) 2006, 2008 IBM Corporation.
 * All rights reserved.   This content
 * is made available under the terms of the Eclipse Public License v1.0
 * which accompanies this distribution, and is available at

<div class="section"><h4 class="sectiontitle">Events page</h4><dl><dt class="dlterm"><span class="uicontrol">Events</span></dt>
<dd>Lists all test execution events, such as the script start and end, loop,
invocation, message, or verdict. When you select an object in the <span class="uicontrol">Events</span> tree,
the properties of the selected event or object are displayed under <span class="uicontrol">Properties</span> and <span class="uicontrol">Extended Properties</span>. </dd>
Properties</span> and <span class="uicontrol">Detailed Properties</span>. </dd>
</dl>
<dl><dt class="dlterm"><span class="uicontrol">Properties</span></dt>
<dd>Displays the link, type, time and text of a selected event in the <span class="uicontrol">Events</span> tree. 
<dl><dt class="dlterm"><span class="uicontrol">Test</span></dt>
<dd>Click to open the test suite, test case, or test behavior for the event.</dd>
</dl>
<dl><dt class="dlterm"><span class="uicontrol">Severity/Type/Status/Verdict</span></dt>
<dd>Displays the severity (message events), type (time events), status (invocation events), and verdict (verdict events) of the event.</dd>
</dl>
<dl><dt class="dlterm"><span class="uicontrol">Time</span></dt>
<dd>Displays the date and time of the event.</dd>
</dl>
<dl><dt class="dlterm"><span class="uicontrol">Text</span></dt>
<dd>Displays a message for the event. </dd>
in the <span class="uicontrol">Events</span> tree. </dd>
</dl>
</dd>
<dt class="dlterm"><span class="uicontrol">Defects</span></dt>
<dd>See <a href="../tasks/t_associating_defects.html">Associating defects with a test log</a>.</dd>
<dt class="dlterm"><span class="uicontrol">Extended Properties</span></dt>
<dd>Displays properties for the event that you selected in the <span class="uicontrol">Events</span> tree. </dd>
</dl>
</div>
</div>

<p>
<b>Related tasks</b><br/>
<a href="../tasks/t_searching_testlogs.html">Searching a test log</a><br/>
<a href="../tasks/t_associating_defects.html">Associating defects with a test log</a><br/>
</p>

</body>
</html>

Lines 66-75 Link Here

(-)tasks/tptpJUnitPluginTest_importing.htm (-4 / +1 lines)
66	<li>	66	<li>
67	Navigate to the required files and then click on <b>Finish</b>.	67	Navigate to the required files and then click on <b>Finish</b>.
68	</li>	68	</li>
69	<li>	69	<li>The <b>Confirm Open Editor</b> dialog may appear (see the <b>Window</b> > <b>Preferences...</b> > <b>Test</b> > <b>Open Editor</b> preference), confirming if the new JUnit Plug-in test suite is to be opened in the JUnit Plug-in Test editor.</li>
70	The outcome of a successful import operation will be a TPTP
71	JUnit Plug-in Test File associated with the imported package or class.
72	</li>
73	</ul>	70	</ul>
74		71
75	<p>Note that the import wizard shows all existing JUnit Plug-in test cases in the workspace that have not already been imported to TPTP. If this list is empty, then it means that either no JUnit Plug-in tests were found in the workspace, or that all existing JUnit Plug-in test classes have already been imported to TPTP.</p>	72	<p>Note that the import wizard shows all existing JUnit Plug-in test cases in the workspace that have not already been imported to TPTP. If this list is empty, then it means that either no JUnit Plug-in tests were found in the workspace, or that all existing JUnit Plug-in test classes have already been imported to TPTP.</p>




	<li>Select <b>File</b> &gt; <b>New</b> &gt; <b>Other</b>.</li>
	<li>Expand <b>Test</b>. Select <b>TPTP JUnit Plug-in Test</b>.</li>
	<li>Click <b>Next</b> to launch the <b>New JUnit Plug-in Test</b> dialog. 
	Identify the Source folder (<i>pluginProject/src</i>), the Package
	(<i>junit.plugin.samples</i>), and the name to be assigned to the JUnit Plug-in Test source code
	(<i>EclipseUiTest</i>).
	</li>
	<li>Select either 'In the test editor' or 'In the code editor' for the test behavior option. See JUnit Test Suite Editor for a detailed explanation of these options.</li>
	<li>Click <b>Next</b> and provide the test's name and location.</li>
	<li>Click <b>Next</b> and provide a description if required. Click <b>Finish</b>.</li>
	<li>The <b>Confirm Open Editor</b> dialog may appear (see the <b>Window</b> &gt; <b>Preferences...</b> &gt; <b>Test</b> &gt; <b>Open Editor</b> preference), confirming if the new JUnit Plug-in test suite is to be opened in the JUnit Plug-in Test editor.</li>	
</ol>
<p>Note that the second and third pages of the wizard are optional (that is, you can finish the wizard at the first page). Also, the difference between the information requested in page 1 and page 2 is as follows: the first page asks for the name and location of the source code, while the second one asks for the name and location of the TPTP Test (the model). By default, they are identical.</p>
</body>

Lines 67-72 Link Here

(-)tasks/treporttest.xhtml (+1 lines)
67	<li>Provide the parent folder and the name for the BIRT test report and click <b>Next</b>.</li>	67	<li>Provide the parent folder and the name for the BIRT test report and click <b>Next</b>.</li>
68	<li>Optionally, provide the report window (start and end data and time) for the BIRT test report.</li>	68	<li>Optionally, provide the report window (start and end data and time) for the BIRT test report.</li>
69	<li>Click <b>Finish </b> to generate the BIRT test report.</li>	69	<li>Click <b>Finish </b> to generate the BIRT test report.</li>
		70	<li>The <b>Confirm Open Editor</b> dialog may appear (see the <b>Window</b> > <b>Preferences...</b> > <b>Test</b> > <b>Open Editor</b> preference), confirming if the new BIRT test report is to be opened in the internal Web Browser or text editor.</li>
70	</ol>	71	</ol>
71	</body>	72	</body>
72	</html>	73	</html>

Lines 107-112 Link Here

(-)tasks/trecordtest.html (-5 / +2 lines)
107	recording, close your browser or click on the <span class="uicontrol">Stop Recording</span>	107	recording, close your browser or click on the <span class="uicontrol">Stop Recording</span>
108	button on the right side of the Recorder Control	108	button on the right side of the Recorder Control
109	view bar. </span> A progress window opens while the test is generated. </li>	109	view bar. </span> A progress window opens while the test is generated. </li>
		110	<li>The <b>Confirm Open Editor</b> dialog may appear (see the <b>Window</b> > <b>Preferences...</b> > <b>Test</b> > <b>Open Editor</b> preference), confirming if the new performance test suite is to be opened in the URL Test editor.</li>
		111
110	</ol>	112	</ol>
111	<div class="section">By default, when you have finished recording an interaction with a browser-based application,	113	<div class="section">By default, when you have finished recording an interaction with a browser-based application,
112	the Recorder Control view displays the message <tt class="sysout">Test	114	the Recorder Control view displays the message <tt class="sysout">Test
Lines 115-124 Link Here
115	by editing the URL Recorder preferences.)</div>	117	by editing the URL Recorder preferences.)</div>
116	</div>	118	</div>
117		119
118	<div>
119	<p>
120	<b class="parentlink">Parent topic:</b> <a href="../../org.eclipse.hyades.test.doc.user/concepts/ctestwithhyades.htm" shape="rect" title="The Eclipse test and performance tools platform (TPTP) supports automated performance testing of HTTP applications.">Performance Testing with TPTP</a><br clear="none" />
121	</p>
122	</div>
123	</body>	120	</body>
124	</html>	121	</html>




<html lang="en-us" xml:lang="en-us">
<!--
/**********************************************************************
 * Copyright (c) 2005, 2008 IBM Corporation.
 * All rights reserved.   This content
 * is made available under the terms of the Eclipse Public License v1.0
 * which accompanies this distribution, and is available at

recorder extension point documentation</a>.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/t_extgenrec.html" title="A test recorder captures user interactions with an application. These interactions are saved, and a test is generated from these recorded actions. Developing a test recorder entails adding the Generic Recorder extension point to the Generic Recorder Framework (GRF), and extending the recorder user interface wizard and the four main GRF helper classes.">Extending the generic test recorder</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="c_genrecframework.html" title="The Generic Recorder Framework (GRF) provides a common user interface experience for all users that record tests. The GRF simplifies the process of extending a recorder by including a reusable extension point. For example, you could define one custom set of wizard pages to reuse for multiple recorders.">Generic Recorder Framework</a></div>
<div><a href="c_testrecorders.html" title="A test recorder captures user interactions with an application. These interactions are saved, and a test is generated from these recorded actions.">Test recorders</a></div>




<html lang="en-us" xml:lang="en-us">
<!--
/**********************************************************************
 * Copyright (c) 2005, 2008 IBM Corporation.
 * All rights reserved.   This content
 * is made available under the terms of the Eclipse Public License v1.0
 * which accompanies this distribution, and is available at

including the user interface and the Agent Controller components.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/t_extgenrec.html" title="A test recorder captures user interactions with an application. These interactions are saved, and a test is generated from these recorded actions. Developing a test recorder entails adding the Generic Recorder extension point to the Generic Recorder Framework (GRF), and extending the recorder user interface wizard and the four main GRF helper classes.">Extending the generic test recorder</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="c_genrecframework.html" title="The Generic Recorder Framework (GRF) provides a common user interface experience for all users that record tests. The GRF simplifies the process of extending a recorder by including a reusable extension point. For example, you could define one custom set of wizard pages to reuse for multiple recorders.">Generic Recorder Framework</a></div>
<div><a href="c_recuiwizard.html" title="The recorder user interface wizard records a session with a Web application, generates a test from the recording, and then opens the test in the test editor.">Recorder user interface wizard</a></div>

Lines 57-65 Link Here

(-)concepts/c_exnewtestrec.html (-3 lines)
57	recorder extension point documentation</a></p>	57	recorder extension point documentation</a></p>
58	</div>	58	</div>
59	<div>	59	<div>
60	<div class="familylinks">
61	<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/t_extgenrec.html" title="A test recorder captures user interactions with an application. These interactions are saved, and a test is generated from these recorded actions. Developing a test recorder entails adding the Generic Recorder extension point to the Generic Recorder Framework (GRF), and extending the recorder user interface wizard and the four main GRF helper classes.">Extending the generic test recorder</a></div>
62	</div>
63	<div class="reltasks"><strong>Related tasks</strong><br />	60	<div class="reltasks"><strong>Related tasks</strong><br />
64	<div><a href="../tasks/t_cretestrec.html" title="To create a test recorder, you extend the recorder user interface wizard and the four main Generic Recorder Framework (GRF) helper classes in the extension point org.eclipse.hyades.test.core.Recorder.">Creating a new test recorder</a></div>	61	<div><a href="../tasks/t_cretestrec.html" title="To create a test recorder, you extend the recorder user interface wizard and the four main Generic Recorder Framework (GRF) helper classes in the extension point org.eclipse.hyades.test.core.Recorder.">Creating a new test recorder</a></div>
65	</div>	62	</div>




<html lang="en-us" xml:lang="en-us">
<!--
/**********************************************************************
 * Copyright (c) 2005, 2008 IBM Corporation.
 * All rights reserved.   This content
 * is made available under the terms of the Eclipse Public License v1.0
 * which accompanies this distribution, and is available at

<p>For more information about these classes, see the <a href="../../org.eclipse.tptp.platform.doc.isv/ref/rextpoint.xhtml#org.eclipse.hyades.test.core.Recorder">generic recorder extension point documentation</a>.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/t_extgenrec.html" title="A test recorder captures user interactions with an application. These interactions are saved, and a test is generated from these recorded actions. Developing a test recorder entails adding the Generic Recorder extension point to the Generic Recorder Framework (GRF), and extending the recorder user interface wizard and the four main GRF helper classes.">Extending the generic test recorder</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="c_testrecorders.html" title="A test recorder captures user interactions with an application. These interactions are saved, and a test is generated from these recorded actions.">Test recorders</a></div>
<div><a href="c_recuiwizard.html" title="The recorder user interface wizard records a session with a Web application, generates a test from the recording, and then opens the test in the test editor.">Recorder user interface wizard</a></div>




<html lang="en-us" xml:lang="en-us">
<!--
/**********************************************************************
 * Copyright (c) 2005, 2008 IBM Corporation.
 * All rights reserved.   This content
 * is made available under the terms of the Eclipse Public License v1.0
 * which accompanies this distribution, and is available at

</ol>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="t_extgenrec.html" title="A test recorder captures user interactions with an application. These interactions are saved, and a test is generated from these recorded actions. Developing a test recorder entails adding the Generic Recorder extension point to the Generic Recorder Framework (GRF), and extending the recorder user interface wizard and the four main GRF helper classes.">Extending the generic test recorder</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="../concepts/c_genrecframework.html" title="The Generic Recorder Framework (GRF) provides a common user interface experience for all users that record tests. The GRF simplifies the process of extending a recorder by including a reusable extension point. For example, you could define one custom set of wizard pages to reuse for multiple recorders.">Generic Recorder Framework</a></div>
<div><a href="../concepts/c_testrecorders.html" title="A test recorder captures user interactions with an application. These interactions are saved, and a test is generated from these recorded actions.">Test recorders</a></div>

Lines 109-117 Link Here

(-)tasks/t_cretestrec.html (-3 lines)
109	</div>	109	</div>
110	</div>	110	</div>
111	<div>	111	<div>
112	<div class="familylinks">
113	<div class="parentlink"><strong>Parent topic:</strong> <a href="t_extgenrec.html" title="A test recorder captures user interactions with an application. These interactions are saved, and a test is generated from these recorded actions. Developing a test recorder entails adding the Generic Recorder extension point to the Generic Recorder Framework (GRF), and extending the recorder user interface wizard and the four main GRF helper classes.">Extending the generic test recorder</a></div>
114	</div>
115	<div class="relconcepts"><strong>Related concepts</strong><br />	112	<div class="relconcepts"><strong>Related concepts</strong><br />
116	<div><a href="../concepts/c_genrecframework.html" title="The Generic Recorder Framework (GRF) provides a common user interface experience for all users that record tests. The GRF simplifies the process of extending a recorder by including a reusable extension point. For example, you could define one custom set of wizard pages to reuse for multiple recorders.">Generic Recorder Framework</a></div>	113	<div><a href="../concepts/c_genrecframework.html" title="The Generic Recorder Framework (GRF) provides a common user interface experience for all users that record tests. The GRF simplifies the process of extending a recorder by including a reusable extension point. For example, you could define one custom set of wizard pages to reuse for multiple recorders.">Generic Recorder Framework</a></div>
117	<div><a href="../concepts/c_testrecorders.html" title="A test recorder captures user interactions with an application. These interactions are saved, and a test is generated from these recorded actions.">Test recorders</a></div>	114	<div><a href="../concepts/c_testrecorders.html" title="A test recorder captures user interactions with an application. These interactions are saved, and a test is generated from these recorded actions.">Test recorders</a></div>

Return to bug 213622

Lines 4-10 Link Here

(-)concepts/cdatapools.htm (-5 / +3 lines)
4	<head>	4	<head>
5	<!--	5	<!--
6	/**********************************************************************	6	/**********************************************************************
7	* Copyright (c) 2000, 2007 IBM Corporation.	7	* Copyright (c) 2000, 2008 IBM Corporation.
8	* All rights reserved. This content	8	* All rights reserved. This content
9	* is made available under the terms of the Eclipse Public License v1.0	9	* is made available under the terms of the Eclipse Public License v1.0
10	* which accompanies this distribution, and is available at	10	* which accompanies this distribution, and is available at
Lines 70-79 Link Here
70	typically typed based on what is expected by the application-under-test.</p>	70	typically typed based on what is expected by the application-under-test.</p>
71	</li>	71	</li>
72	</ul>	72	</ul>
73	<p>As shown in the following figure, the datapool editor is a grid similar	73
74	to a spreadsheet. Right-clicking on the grid opens the pop-up menu that you
75	use to add or maintain the datapool structural elements described above. You
76	add data by typing in a cell.<br /><img src="../images/dpeditpopup.gif" alt=""/><br /></p>
77	<p>When you create a datapool, you have the option of initializing the new	74	<p>When you create a datapool, you have the option of initializing the new
78	datapool with data contained in an existing comma-separated value text file (CSV)	75	datapool with data contained in an existing comma-separated value text file (CSV)
79	that you created with a spreadsheet editor or with some external or custom	76	that you created with a spreadsheet editor or with some external or custom
Lines 82-87 Link Here
82	individual records but provides no means of generating large amounts of typed	79	individual records but provides no means of generating large amounts of typed
83	data.	80	data.
84	</p>	81	</p>
		82
85	</div>	83	</div>
86		84
87	<div>	85	<div>

Lines 42-55 Link Here

(-)concepts/cedittest.htm (-8 / +3 lines)
42	<p> </p>	42	<p> </p>
43	<p>Open the performance test in the TPTP URL Test editor:</p>	43	<p>Open the performance test in the TPTP URL Test editor:</p>
44	<img src="../images/editOverview.jpg" alt=""/><p>The test opens in the <span class="uicontrol">Overview</span> tab (see the bottom	44	<img src="../images/editOverview.jpg" alt=""/><p>The test opens in the <span class="uicontrol">Overview</span> tab (see the bottom
45	border) with the four edit areas (<span class="uicontrol">General Information</span> and <span class="uicontrol">Source	45	border) with the four edit areas (<span class="uicontrol">TPTP URL Test</span> and <span class="uicontrol">Source
46	Information</span> on the left and <span class="uicontrol">Deployment</span> and <span class="uicontrol">HTTP Requests</span> on	46	Information</span> on the left and <span class="uicontrol">Deployment</span> and <span class="uicontrol">HTTP Requests</span> on
47	the right) expanded. You switch to the other edit panes by clicking the appropriate	47	the right) expanded. You switch to the other edit panes by clicking the appropriate
48	tab. </p>	48	tab. </p>
49	<p>The <span class="uicontrol">General Information</span> area displays the test's	49	<p>The <span class="uicontrol">TPTP URL Test</span> area displays the test's
50	name, an optional description, the test's type, and the name of the file containing	50	name, an optional description, the test's type, and the name of the file containing
51	the test. Information appearing in boxes can be edited. The <span class="uicontrol">Name</span> box	51	the test. Information appearing in boxes can be edited. The <span class="uicontrol">Name</span> box
52	under <span class="uicontrol">General Information</span> displays the name of the	52	under <span class="uicontrol">TPTP URL Test</span> displays the name of the
53	test. You can change the name. If you do, the	53	test. You can change the name. If you do, the
54	name displayed in the Test Navigator changes also but the filename containing	54	name displayed in the Test Navigator changes also but the filename containing
55	the test does not change. In this example, the test's name, as listed in the	55	the test does not change. In this example, the test's name, as listed in the
Lines 109-118 Link Here
109	executed simultaneously. That is, the invocation is executed at the same time as the sibling invocations and loops.</p>	109	executed simultaneously. That is, the invocation is executed at the same time as the sibling invocations and loops.</p>
110	</div>	110	</div>
111		111
112	<div>
113	<p>
114	<b class="parentlink">Parent topic:</b> <a href="../concepts/ctestwithhyades.htm" title="The Eclipse test and performance tools platform (TPTP) supports automated performance testing of HTTP applications.">Performance Testing with TPTP</a><br />
115	</p>
116	</div>
117	</body>	112	</body>
118	</html>	113	</html>

Lines 3-9 Link Here

(-)tasks/tptpJUnitTest_creatingManually.htm (-3 / +4 lines)
3		3
4	<!--	4	<!--
5	/**********************************************************************	5	/**********************************************************************
6	* Copyright (c) 2000, 2007 IBM Corporation.	6	* Copyright (c) 2000, 2008 IBM Corporation.
7	* All rights reserved. This content	7	* All rights reserved. This content
8	* is made available under the terms of the Eclipse Public License v1.0	8	* is made available under the terms of the Eclipse Public License v1.0
9	* which accompanies this distribution, and is available at	9	* which accompanies this distribution, and is available at
Lines 36-49 Link Here
36	<li>Select <b>File</b> > <b>New</b> > <b>Other</b>.</li>	36	<li>Select <b>File</b> > <b>New</b> > <b>Other</b>.</li>
37	<li>Expand <b>Test</b>. Select <b>TPTP JUnit Test</b>.</li>	37	<li>Expand <b>Test</b>. Select <b>TPTP JUnit Test</b>.</li>
38	<li>Click <b>Next</b> to launch the <b>New JUnit Test Definition</b> dialog.	38	<li>Click <b>Next</b> to launch the <b>New JUnit Test Definition</b> dialog.
39	Identify the Source folder (<i>javaProject</i>), the Package	39	Identify the Source folder (<i>javaProject/src</i>), the Package
40	(<i>junit.samples</i>), and the name to be assigned to the JUnit Test source code	40	(<i>junit.samples</i>), and the name to be assigned to the JUnit Test source code
41	(<i>JUnit_src</i>).	41	(<i>JUnit_src</i>).
42	</li>	42	</li>
43	<li>Click <b>Next</b>. The <b>New JUnit Test Definition</b> dialog launches.</li>	43	<li>Click <b>Next</b>. The <b>New JUnit Test Definition</b> dialog launches.</li>
44	<li>Enter the parent folder (<i>javaProject/junit/samples</i>) and Name (<i>JUnit_src</i>).</li>	44	<li>Enter the parent folder (<i>javaProject/src/junit/samples</i>) and Name (<i>JUnit_src</i>).</li>
45	<li>Optionally click <b>Next</b> and provide a description of the JUnit test definition.</li>	45	<li>Optionally click <b>Next</b> and provide a description of the JUnit test definition.</li>
46	<li>Click on <b>Finish</b>.</li>	46	<li>Click on <b>Finish</b>.</li>
		47	<li>The <b>Confirm Open Editor</b> dialog may appear (see the <b>Window</b> > <b>Preferences...</b> > <b>Test</b> > <b>Open Editor</b> preference), confirming if the new JUnit test suite is to be opened in the JUnit Test editor.</li>
47	</ol>	48	</ol>
48	<p>Note that the second and third pages of the wizard are optional (that is, you can finish the wizard at the first page). Also, the difference between the information requested in page 1 and page 2 is as follows: the first page asks for the name and location of the source code, while the second one asks for the name and location of the TPTP Test (the model). By default, they are identical.</p>	49	<p>Note that the second and third pages of the wizard are optional (that is, you can finish the wizard at the first page). Also, the difference between the information requested in page 1 and page 2 is as follows: the first page asks for the name and location of the source code, while the second one asks for the name and location of the TPTP Test (the model). By default, they are identical.</p>
49	</body>	50	</body>

Lines 3-9 Link Here

(-)tasks/t_associating_defects.html (-22 / +45 lines)
3	<html lang="en-us" xml:lang="en-us">	3	<html lang="en-us" xml:lang="en-us">
4	<!--	4	<!--
5	/**********************************************************************	5	/**********************************************************************
6	* Copyright (c) 2006, 2007 IBM Corporation.	6	* Copyright (c) 2006, 2008 IBM Corporation.
7	* All rights reserved. This content	7	* All rights reserved. This content
8	* is made available under the terms of the Eclipse Public License v1.0	8	* is made available under the terms of the Eclipse Public License v1.0
9	* which accompanies this distribution, and is available at	9	* which accompanies this distribution, and is available at
Lines 32-58 Link Here
32	</head>	32	</head>
33	<body><a name="associating_defects.dita"><!-- --></a>	33	<body><a name="associating_defects.dita"><!-- --></a>
34	<h1 class="topictitle1">Associating defects with a test log</h1>	34	<h1 class="topictitle1">Associating defects with a test log</h1>
35	<div><p>Use the Test Log viewer to associate defects with a test log using	35	<div>
36	the defect number. Associated defects are conveniently displayed in the test	36
37	log as links to the defect database.</p>	37	<p>The Test Log viewer is integrated with a Web-based Bugzilla defect tracking
38	<div class="p">This feature uses the Bugzilla Web interface by default. If your application	38	system used to submit, search, and open defects in the internal Web Browser. Existing
39	uses another defect-tracking tool, then that tool must be available with your	39	defects may be associated with individual execution events in the test log.</p>
40	Eclipse installation.</div>	40
41	<div class="section">To associate an existing defect with a test log, perform the following	41	<p>By default, the Test Log viewer is integrated with the Web-based
42	steps:</div>	42	<a href="https://bugs.eclipse.org/bugs/">Eclipse Bugzilla</a> defect tracking system. To use
43	<ol><li class="stepexpand"><span>Make sure that the desired test log is open.</span></li>	43	another Web-based Bugzilla defect tracking system, you can configure in the
44	<li class="stepexpand"><span>Click the <span class="uicontrol">Events</span> tab.</span></li>	44	Test Log viewer preferences:</p>
45	<li class="stepexpand"><span>Under <span class="wintitle">Events</span>, select the execution event with	45
46	which to associate the defect.</span></li>	46	<ol>
47	<li class="stepexpand"><span>Under <span class="wintitle">Defects</span>, click <span class="uicontrol">Add</span>.</span></li>	47	<li>Select <b>Window</b> > <b>Preferences...</b> from the file menu.</li>
48	<li class="stepexpand"><span>Type the number of the existing defect, and then click <span class="uicontrol">OK</span>.</span> The newly associated defect number is shown as a link; click the	48	<li>Select the <b>Test</b> > <b>Test Log viewer</b> preference page.</li>
49	link to view the record in the defect database.</li>	49	<li>Configure the <b>Submit URL</b>, <b>Search URL</b>, and <b>Open URL</b> links for the Web-based Bugzilla defect tracking system.</li>
50	<li class="stepexpand"><span>If you do not know the defect number, you can search the defect	50	<li>Click <b>OK</b> to save the preferences.</li>
51	tracking system to find it. Click <span class="uicontrol">Search</span>. </span> The
52	defect tracking tool's Search page opens, enabling you to search for the defect.</li>
53	</ol>	51	</ol>
54	<div class="section">Similarly, click <span class="uicontrol">Remove</span> to remove defects	52
55	from the test log.</div>	53	<p>Defects may be associated with any execution event in the Events page.</p>
		54
		55	<p>Add, open, and remove a defect:</p>
		56
		57	<ol>
		58	<li>Select execution event in the <b>Events</b> tree of the Events page and expand <b>Defects</b>.</li>
		59	<li>To add a defect to the execution event, click <b>Add...</b>, enter the defect number, and click <b>OK</b>.</li>
		60	<li>The defect is associated with the execution event and the defect number is displayed as a link.</li>
		61	<li>To open the defect, click the defect number link, and view the defect in the internal Web Browser.</li>
		62	<li>To remove the defect, click the remove link to the right of the defect number link.</li>
		63	</ol>
		64
		65	<p>Submit a new defect:</p>
		66
		67	<ol>
		68	<li>Select execution event in the <b>Events</b> tree of the Events page and expand <b>Defects</b>.</li>
		69	<li>Click <b>Submit...</b> and enter the defect details in the internal Web Browser according to the procedure for the Web-based Bugzilla defect tracking system.</li>
		70	</ol>
		71
		72	<p>Search for an existing defect:</p>
		73
		74	<ol>
		75	<li>Select execution event in the <b>Events</b> tree of the Events page and expand <b>Defects</b>.</li>
		76	<li>Click <b>Search...</b> and enter the search details in the internal Web Browser according to the procedure for the Web-based Bugzilla defect tracking system.</li>
		77	</ol>
		78
56	</div>	79	</div>
57	<div></div></body>	80	</body>
58	</html>	81	</html>

Lines 3-9 Link Here

(-)tasks/t_viewingevents.html (-6 / +2 lines)
3	<html lang="en-us" xml:lang="en-us">	3	<html lang="en-us" xml:lang="en-us">
4	<!--	4	<!--
5	/**********************************************************************	5	/**********************************************************************
6	* Copyright (c) 2006, 2007 IBM Corporation.	6	* Copyright (c) 2006, 2008 IBM Corporation.
7	* All rights reserved. This content	7	* All rights reserved. This content
8	* is made available under the terms of the Eclipse Public License v1.0	8	* is made available under the terms of the Eclipse Public License v1.0
9	* which accompanies this distribution, and is available at	9	* which accompanies this distribution, and is available at
Lines 66-74 Link Here
66	(<img src="../images/th_vertical.gif" alt="Vertical orientation button" />) to display information horizontally or vertically.</span></li>	66	(<img src="../images/th_vertical.gif" alt="Vertical orientation button" />) to display information horizontally or vertically.</span></li>
67	</ol>	67	</ol>
68	</div>	68	</div>
69	<div>	69	</body>
70	<div class="familylinks">
71	<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/c_viewingtestresults.html" title="After running a test, the test results for the events are saved in a test log. Use the Test Log viewer to examine test results and events.">Analyzing test results</a></div>
72	</div>
73	</div></body>
74	</html>	70	</html>

Lines 3-9 Link Here

(-)tasks/t_openinglogs.html (-6 / +2 lines)
3	<html lang="en-us" xml:lang="en-us">	3	<html lang="en-us" xml:lang="en-us">
4	<!--	4	<!--
5	/**********************************************************************	5	/**********************************************************************
6	* Copyright (c) 2005, 2007 IBM Corporation.	6	* Copyright (c) 2005, 2008 IBM Corporation.
7	* All rights reserved. This content	7	* All rights reserved. This content
8	* is made available under the terms of the Eclipse Public License v1.0	8	* is made available under the terms of the Eclipse Public License v1.0
9	* which accompanies this distribution, and is available at	9	* which accompanies this distribution, and is available at
Lines 44-52 Link Here
44	<div class="section">Alternatively, locate in the Test Navigator the test log file and	44	<div class="section">Alternatively, locate in the Test Navigator the test log file and
45	then double-click it.</div>	45	then double-click it.</div>
46	</div>	46	</div>
47	<div>	47	</body>
48	<div class="familylinks">
49	<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/c_viewingtestresults.html" title="After running a test, the test results for the events are saved in a test log. Use the Test Log viewer to examine test results and events.">Analyzing test results</a></div>
50	</div>
51	</div></body>
52	</html>	48	</html>

Lines 31-67 Link Here

(-)tasks/teditdp.htm (-21 / +14 lines)
31	<link rel="stylesheet" type="text/css" href="../css/swg_info_common.css" />	31	<link rel="stylesheet" type="text/css" href="../css/swg_info_common.css" />
32	<title>Editing a datapool</title>	32	<title>Editing a datapool</title>
33	</head>	33	</head>
34	<body><a name="teditdp"><!-- --></a>	34	<body>
35		35	<div>
36	<h1 class="topictitle1">Editing a datapool</h1>	36	<h1 class="topictitle1">Editing a datapool</h1>
37	<p>In a manner similar to editing a spreadsheet, you can add, modify
38	or remove data from a datapool.</p>
39	<div class="skipspace"><p>When you right-click on the datapool editing grid, the following pop up menu appears. <br />
40	<img src="../images/dpeditpopup.gif" alt="" /><br /><br />
41	The pop up menu allows you to add records or variables. Records are added automatically. If you choose "Insert variable" the following dialog appears. The <b>Insert</b> drop down option specifies the position of the new column with respect to other datapool columns.</p>
42	<img src="../images/columndlg.png" alt=""/>
43		37
		38	<p>The datapool editor is a grid similar to a spreadsheet.</p>
44		39
		40	<p>In a manner similar to editing a spreadsheet, you can add, modify or remove data from a datapool.</p>
45		41
46	<br />	42	<p>When you right-click on the datapool editing grid, a context menu appears to add, edit, and remove a
47	<br />	43	record or variable, and cut, copy, and paste the selected cell.</p>
48	The Datapool editor's overview tab allows you to edit variables and equivalence classes. As shown below left, the Properties window includes detailed properties for each item.<img	44
49	border="0" src="../images/dpEditor_OverviewTab.gif" width="844"	45	<p>If you insert a variable, the name, type, and relative position of the new variable is required.
50	height="421" alt=""/>	46	In addition, you may encrypt the new variable, which requires a password.</p>
51	</div>	47
52	<div class="p"><span></span>	48	<p>The Datapool editor's overview tab allows you to edit variables and equivalence classes.</p>
53	<p><b class="parentlink"><br />	49
54	Parent topic:</b> <a	50	<p>
55	href="../tasks/tdatapool.htm"
56	title="If you associate a value in a test with a datapool column, the test substitutes column data for that value when it runs.">Providing
57	tests with variable data</a><br />
58	<br />
59	<strong>Related concepts</strong><br />	51	<strong>Related concepts</strong><br />
60	<a href="../samples/saccessdp.htm">Tutorial: Creating a datapool driven JUnit test application</a><br />	52	<a href="../samples/saccessdp.htm">Tutorial: Creating a datapool driven JUnit test application</a><br />
61	<strong><br />	53	<strong><br />
62	Related tasks</strong><br />	54	Related tasks</strong><br />
63	<a href="../tasks/tcreatedp.htm">Creating a datapool</a><br />	55	<a href="../tasks/tcreatedp.htm">Creating a datapool</a><br />
64	</p>	56	</p>
		57
65	</div>	58	</div>
66	</body>	59	</body>
67	</html>	60	</html>

Lines 3-9 Link Here

(-)tasks/topendp.htm (-6 / +1 lines)
3	<html lang="en-us" xml:lang="en-us">	3	<html lang="en-us" xml:lang="en-us">
4	<!--	4	<!--
5	/**********************************************************************	5	/**********************************************************************
6	* Copyright (c) 2004, 2007 IBM Corporation.	6	* Copyright (c) 2004, 2008 IBM Corporation.
7	* All rights reserved. This content	7	* All rights reserved. This content
8	* is made available under the terms of the Eclipse Public License v1.0	8	* is made available under the terms of the Eclipse Public License v1.0
9	* which accompanies this distribution, and is available at	9	* which accompanies this distribution, and is available at
Lines 46-55 Link Here
46	</ol>	46	</ol>
47	</div>	47	</div>
48		48
49	<div>
50	<p>
51	<b class="parentlink">Parent topic:</b> <a href="../tasks/tdatapool.htm" title="If you associate a value in a test with a datapool column, the test substitutes column data for that value when it runs.">Providing tests with variable data</a><br />
52	</p>
53	</div>
54	</body>	49	</body>
55	</html>	50	</html>

Removed Link Here

(-)tasks/t_submitting_defects.html (-52 lines)
1	<!DOCTYPE html
2	PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3	<html lang="en-us" xml:lang="en-us">
4	<!--
5	/**********************************************************************
6	* Copyright (c) 2006, 2007 IBM Corporation.
7	* All rights reserved. This content
8	* is made available under the terms of the Eclipse Public License v1.0
9	* which accompanies this distribution, and is available at
10	* http://www.eclipse.org/legal/epl-v10.html
11	* $Id: t_submitting_defects.html,v 1.3 2007/05/03 14:33:14 paules Exp $
12	*
13	* Contributors:
14	* IBM - Initial contribution
15	**********************************************************************/
16	-->
17	<head>
18	<meta http-equiv="Content-Type" content="text/html; charset=windows-1252" />
19	<meta name="security" content="public" />
20	<meta name="Robots" content="index,follow" />
21	<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))' />
22	<meta name="DC.Type" content="task" />
23	<meta name="DC.Title" content="Submitting defects" />
24	<meta name="abstract" content="The Test Log viewer provides a direct link to a defect tracking system that you can use to submit defects as you find them." />
25	<meta name="description" content="The Test Log viewer provides a direct link to a defect tracking system that you can use to submit defects as you find them." />
26	<meta name="DC.Format" content="XHTML" />
27	<meta name="DC.Identifier" content="submitting_defects" />
28	<meta name="DC.Language" content="en-us" />
29	<link rel="stylesheet" type="text/css" href="../css/book.css" />
30	<link rel="stylesheet" type="text/css" href="../css/ibmdita.css" />
31	<title>Submitting defects</title>
32	</head>
33	<body><a name="submitting_defects"><!-- --></a>
34	<h1 class="topictitle1">Submitting defects</h1>
35	<div><p>The Test Log viewer provides a direct link to a defect tracking
36	system that you can use to submit defects as you find them.</p>
37	<div class="p">This feature uses the Bugzilla Web interface by default. If your application
38	uses another defect tracking tool, then that tool must be available with your
39	Eclipse installation.</div>
40	<div class="section">To submit a defect for tracking, perform the following steps:</div>
41	<ol><li class="stepexpand"><span>Make sure that the desired test log is open. </span></li>
42	<li class="stepexpand"><span>Click the <span class="uicontrol">Events</span> tab.</span></li>
43	<li class="stepexpand"><span>Under <span class="wintitle">Events</span>, select the execution event with
44	which to associate the new defect.</span></li>
45	<li class="stepexpand"><span>Under <span class="wintitle">Defects</span>, click <span class="uicontrol">Submit</span>.</span> The defect tracking system opens. Log in (if required) and then
46	submit the defect according to the procedure for your defect-tracking tool. </li>
47	</ol>
48	<div class="section">In the test log, the new defect number is shown as a
49	link; click this link to return to the record in the defect database.</div>
50	</div>
51	<div></div></body>
52	</html>

Lines 38-53 Link Here

(-)tasks/tcreatingaperformancetest.htm (-7 / +1 lines)
38	<li>Expand the <b>Test</b> folder, then select <b>TPTP URL Test</b>.</li>	38	<li>Expand the <b>Test</b> folder, then select <b>TPTP URL Test</b>.</li>
39	<li>Click <b>Next</b>, select the location (the project created in step 1), and name the performance test suite, for example, <i>examplePerformanceTest</i>.</li>	39	<li>Click <b>Next</b>, select the location (the project created in step 1), and name the performance test suite, for example, <i>examplePerformanceTest</i>.</li>
40	<li>Click <b>Next</b> and optionally provide a description for the performance test suite. Click <b>Finish</b>.</li>	40	<li>Click <b>Next</b> and optionally provide a description for the performance test suite. Click <b>Finish</b>.</li>
41	<li>A performance test suite file (examplePerformanceTest.testsuite) will be created, becomes visible in the Test Navigator and opens in the URL Test editor.</li>	41	<li>The <b>Confirm Open Editor</b> dialog may appear (see the <b>Window</b> > <b>Preferences...</b> > <b>Test</b> > <b>Open Editor</b> preference), confirming if the new performance test suite is to be opened in the URL Test editor.</li>
42	</ol>	42	</ol>
43	</div>	43	</div>
44		44
45	<div>
46	<p>
47	<b class="parentlink">Parent topic:</b> <a href="../concepts/ctestwithhyades.htm" shape="rect" title="The Eclipse test and performance tools platform (TPTP) supports automated performance testing of HTTP applications.">Performance Testing with TPTP</a><br clear="none" />
48	</p>
49	</div>
50
51	</body>	45	</body>
52		46
53	</html>	47	</html>

Lines 49-58 Link Here

(-)tasks/tcreatetestreports.htm (-5 / +2 lines)
49	<td>Time Frame Historic<sup>1</sup></td>	49	<td>Time Frame Historic<sup>1</sup></td>
50	<td>Report with all of the execution results for each selected test within a specified period of time.</td>	50	<td>Report with all of the execution results for each selected test within a specified period of time.</td>
51	</tr>	51	</tr>
52	<tr>
53	<td>Test Pass Report<sup>1</sup></td>
54	<td>Report with only the most recent execution results for each selected test within a specified period of time.</td>
55	</tr>
56	</tbody>	52	</tbody>
57	</table>	53	</table>
58		54
Lines 61-67 Link Here
61	<p>Configure the fonts used when generating a test report:</p>	57	<p>Configure the fonts used when generating a test report:</p>
62	<ol>	58	<ol>
63	<li>Select <b>Window</b> > <b>Preferences...</b> from the file menu.</li>	59	<li>Select <b>Window</b> > <b>Preferences...</b> from the file menu.</li>
64	<li>Select the report <b>Test</b> > <b>Test Reports</b> > <b>Fonts</b> preference page.</li>	60	<li>Select the <b>Test</b> > <b>Test Reports</b> > <b>Fonts</b> preference page.</li>
65	<li>Configure the fonts used when generating a test report.</li>	61	<li>Configure the fonts used when generating a test report.</li>
66	<li>Click <b>OK</b> to save the preferences.</li>	62	<li>Click <b>OK</b> to save the preferences.</li>
67	</ol>	63	</ol>
Lines 73-78 Link Here
73	<li>Provide the parent folder and the name for the test report and click <b>Next</b>.</li>	69	<li>Provide the parent folder and the name for the test report and click <b>Next</b>.</li>
74	<li>Optionally, provide the report window (start and end data and time) for the test report.</li>	70	<li>Optionally, provide the report window (start and end data and time) for the test report.</li>
75	<li>Click <b>Finish </b> to generate the test report.</li>	71	<li>Click <b>Finish </b> to generate the test report.</li>
		72	<li>The <b>Confirm Open Editor</b> dialog may appear (see the <b>Window</b> > <b>Preferences...</b> > <b>Test</b> > <b>Open Editor</b> preference), confirming if the new test report is to be opened in the internal Web Browser.</li>
76	</ol>	73	</ol>
77		74
78	</body>	75	</body>

Lines 3-9 Link Here

(-)tasks/tgenerateexecutabletest.htm (-11 / +7 lines)
3	<html lang="en-us" xml:lang="en-us">	3	<html lang="en-us" xml:lang="en-us">
4	<!--	4	<!--
5	/**********************************************************************	5	/**********************************************************************
6	* Copyright (c) 2004, 2007 IBM Corporation.	6	* Copyright (c) 2004, 2008 IBM Corporation.
7	* All rights reserved. This content	7	* All rights reserved. This content
8	* is made available under the terms of the Eclipse Public License v1.0	8	* is made available under the terms of the Eclipse Public License v1.0
9	* which accompanies this distribution, and is available at	9	* which accompanies this distribution, and is available at
Lines 47-66 Link Here
47	<div class="skipspace">To generate a test's source code:</div>	47	<div class="skipspace">To generate a test's source code:</div>
48	<ol><li class="skipspace"><span>In the Test Navigator, right-click the test to be run and select <span class="uicontrol">Generate</span>. </span> The <span class="uicontrol">JUnit Test Definition Code Generation</span> dialog	48	<ol><li class="skipspace"><span>In the Test Navigator, right-click the test to be run and select <span class="uicontrol">Generate</span>. </span> The <span class="uicontrol">JUnit Test Definition Code Generation</span> dialog
49	box opens.</li>	49	box opens.</li>
50	<li class="skipspace"><span>In the <span class="uicontrol">Java Project</span> field, accept the default	50	<li class="skipspace"><span>In the <span class="uicontrol">Source Folder</span> field, accept the default
51	or click <span class="uicontrol">Browse</span> to select the Java project in which	51	or click <span class="uicontrol">Browse</span> to select the source folder in a Java project in which
52	to store the test code.</span></li>	52	to store the test code.</span></li>
53	<li class="skipspace"><span>In the <span class="uicontrol">Source folder</span> field, accept the	53	<li class="skipspace"><span>In the <span class="uicontrol">Package Name</span> field, accept the
54	default or click <span class="uicontrol">Browse</span> to select the folder in the	54	default or click <span class="uicontrol">Browse</span> to select the package the selected Java project
55	selected Java project in which to store the test code.</span></li>	55	in which to store the test code.</span></li>
		56	<li class="skipspace"><span>In the <span class="uicontrol">Class Name</span> field, specify the name of the test code.</span></li>
56	<li class="skipspace"><span>Click <span class="uicontrol">Finish</span>.</span></li>	57	<li class="skipspace"><span>Click <span class="uicontrol">Finish</span>.</span></li>
57	</ol>	58	</ol>
58	</div>	59	</div>
59		60
60	<div>
61	<p>
62	<b class="parentlink">Parent topic:</b> <a href="../concepts/ctestwithhyades.htm" title="The Eclipse test and performance tools platform (TPTP) supports automated performance testing of HTTP applications.">Performance Testing with TPTP</a><br />
63	</p>
64	</div>
65	</body>	61	</body>
66	</html>	62	</html>

Lines 3-9 Link Here

(-)tasks/t_searching_testlogs.html (-3 / +2 lines)
3	<html lang="en-us" xml:lang="en-us">	3	<html lang="en-us" xml:lang="en-us">
4	<!--	4	<!--
5	/**********************************************************************	5	/**********************************************************************
6	* Copyright (c) 2006, 2007 IBM Corporation.	6	* Copyright (c) 2006, 2008 IBM Corporation.
7	* All rights reserved. This content	7	* All rights reserved. This content
8	* is made available under the terms of the Eclipse Public License v1.0	8	* is made available under the terms of the Eclipse Public License v1.0
9	* which accompanies this distribution, and is available at	9	* which accompanies this distribution, and is available at
Lines 44-51 Link Here
44	you want to find. </span></li>	44	you want to find. </span></li>
45	<li><span>To make the search case-sensitive, select the appropriate option. </span></li>	45	<li><span>To make the search case-sensitive, select the appropriate option. </span></li>
46	<li><span>To search only a portion of the test log, click <span class="uicontrol">Restrict	46	<li><span>To search only a portion of the test log, click <span class="uicontrol">Restrict
47	to descendants of selected element</span> or <span class="uicontrol">Search only immediate	47	to descendants of selected element</span>. This option refers to the element you currently
48	descendants</span>. These options refer to the element you currently
49	have selected in the Events page of the test log. </span></li>	48	have selected in the Events page of the test log. </span></li>
50	<li><span>Optionally, use <span class="uicontrol">Elements to Search</span> to limit	49	<li><span>Optionally, use <span class="uicontrol">Elements to Search</span> to limit
51	your search to certain event types. Additional options are displayed for each	50	your search to certain event types. Additional options are displayed for each

Lines 3-9 Link Here

(-)tasks/tcreatedp.htm (-4 / +4 lines)
3	<html lang="en-us" xml:lang="en-us">	3	<html lang="en-us" xml:lang="en-us">
4	<!--	4	<!--
5	/**********************************************************************	5	/**********************************************************************
6	* Copyright (c) 2004, 2007 IBM Corporation.	6	* Copyright (c) 2004, 2008 IBM Corporation.
7	* All rights reserved. This content	7	* All rights reserved. This content
8	* is made available under the terms of the Eclipse Public License v1.0	8	* is made available under the terms of the Eclipse Public License v1.0
9	* which accompanies this distribution, and is available at	9	* which accompanies this distribution, and is available at
Lines 75-82 Link Here
75	</ul>	75	</ul>
76	</li><li class="skipspace"><span>Click <span class="uicontrol">Finish</span>.</span> If you specified initial datapool dimensions, which may conflict with the CSV file dimensions, a dialog appears. Click <b>Yes</b> to use the dimensions of the CSV file. Click <b>No</b> to use the specified initial dimensions (and possibly truncate the CSV file data). The Datapool editor appears, showing the	76	</li><li class="skipspace"><span>Click <span class="uicontrol">Finish</span>.</span> If you specified initial datapool dimensions, which may conflict with the CSV file dimensions, a dialog appears. Click <b>Yes</b> to use the dimensions of the CSV file. Click <b>No</b> to use the specified initial dimensions (and possibly truncate the CSV file data). The Datapool editor appears, showing the
77	datapool's first equivalence class. <br />	77	datapool's first equivalence class. <br />
78	<img src="../images/dpeditpopup.gif" alt=""/><br />
79	</li>	78	</li>
		79	<li class="skipspace">The <b>Confirm Open Editor</b> dialog may appear (see the <b>Window</b> > <b>Preferences...</b> > <b>Test</b> > <b>Open Editor</b> preference), confirming if the new datapool is to be opened in the Datapool editor.<br />
		80	</li>
		81
80	</ol>	82	</ol>
81	<div class="skipspace"><br />For instructions	83	<div class="skipspace"><br />For instructions
82	on how to add data to or edit the new datapool, go to <a	84	on how to add data to or edit the new datapool, go to <a
Lines 86-93 Link Here
86		88
87	<div>	89	<div>
88	<p>	90	<p>
89	<b class="parentlink">Parent topic:</b> <a href="../tasks/tdatapool.htm" title="If you associate a value in a test with a datapool column, the test substitutes column data for that value when it runs.">Providing tests with variable data</a><br />
90	<br />
91	<strong>Related concepts</strong><br />	91	<strong>Related concepts</strong><br />
92	<a href="../samples/saccessdp.htm">Tutorial: Creating a datapool driven JUnit test application</a><br />	92	<a href="../samples/saccessdp.htm">Tutorial: Creating a datapool driven JUnit test application</a><br />
93	<br />	93	<br />

Lines 1-7 Link Here

(-)toc/logviewer_toc.xml (-2 / +1 lines)
1	<?xml version="1.0" encoding="utf-8"?>	1	<?xml version="1.0" encoding="utf-8"?>
2	<!--	2	<!--
3	/**********************************************************************	3	/**********************************************************************
4	* Copyright (c) 2007 IBM Corporation.	4	* Copyright (c) 2007, 2008 IBM Corporation.
5	* All rights reserved. This content	5	* All rights reserved. This content
6	* is made available under the terms of the Eclipse Public License v1.0	6	* is made available under the terms of the Eclipse Public License v1.0
7	* which accompanies this distribution, and is available at	7	* which accompanies this distribution, and is available at
Lines 21-27 Link Here
21	<topic label="Test Log viewer Events page" href="ref/r_testlog_events.html"/>	21	<topic label="Test Log viewer Events page" href="ref/r_testlog_events.html"/>
22	<topic label="Test Log viewer Events toolbar" href="ref/r_testlog_toolbar.html"/>	22	<topic label="Test Log viewer Events toolbar" href="ref/r_testlog_toolbar.html"/>
23	<topic label="Searching a test log" href="tasks/t_searching_testlogs.html"/>	23	<topic label="Searching a test log" href="tasks/t_searching_testlogs.html"/>
24	<topic label="Submitting defects" href="tasks/t_submitting_defects.html"/>
25	<topic label="Associating defects with a test log" href="tasks/t_associating_defects.html"/>	24	<topic label="Associating defects with a test log" href="tasks/t_associating_defects.html"/>
26	</topic>	25	</topic>
27	</topic>	26	</topic>

Lines 3-9 Link Here

(-)ref/r_testlog_events.html (-12 / +22 lines)
3	<html lang="en-us" xml:lang="en-us">	3	<html lang="en-us" xml:lang="en-us">
4	<!--	4	<!--
5	/**********************************************************************	5	/**********************************************************************
6	* Copyright (c) 2006, 2007 IBM Corporation.	6	* Copyright (c) 2006, 2008 IBM Corporation.
7	* All rights reserved. This content	7	* All rights reserved. This content
8	* is made available under the terms of the Eclipse Public License v1.0	8	* is made available under the terms of the Eclipse Public License v1.0
9	* which accompanies this distribution, and is available at	9	* which accompanies this distribution, and is available at
Lines 36-61 Link Here
36	<div class="section"><h4 class="sectiontitle">Events page</h4><dl><dt class="dlterm"><span class="uicontrol">Events</span></dt>	36	<div class="section"><h4 class="sectiontitle">Events page</h4><dl><dt class="dlterm"><span class="uicontrol">Events</span></dt>
37	<dd>Lists all test execution events, such as the script start and end, loop,	37	<dd>Lists all test execution events, such as the script start and end, loop,
38	invocation, message, or verdict. When you select an object in the <span class="uicontrol">Events</span> tree,	38	invocation, message, or verdict. When you select an object in the <span class="uicontrol">Events</span> tree,
39	the properties of the selected event or object are displayed under <span class="uicontrol">Common	39	the properties of the selected event or object are displayed under <span class="uicontrol">Properties</span> and <span class="uicontrol">Extended Properties</span>. </dd>
40	Properties</span> and <span class="uicontrol">Detailed Properties</span>. </dd>
41	</dl>	40	</dl>
42	<dl><dt class="dlterm"><span class="uicontrol">Common Properties</span></dt>	41	<dl><dt class="dlterm"><span class="uicontrol">Properties</span></dt>
43	<dd>Displays the time and text of a selected event in the <span class="uicontrol">Events</span> tree. <dl><dt class="dlterm"><span class="uicontrol">Test</span></dt>	42	<dd>Displays the link, type, time and text of a selected event in the <span class="uicontrol">Events</span> tree.
44	<dd>Click to open the test suite, test case, or test behavior of the event	43	<dl><dt class="dlterm"><span class="uicontrol">Test</span></dt>
45	that you selected in the <span class="uicontrol">Events</span> tree.</dd>	44	<dd>Click to open the test suite, test case, or test behavior for the event.</dd>
		45	</dl>
		46	<dl><dt class="dlterm"><span class="uicontrol">Severity/Type/Status/Verdict</span></dt>
		47	<dd>Displays the severity (message events), type (time events), status (invocation events), and verdict (verdict events) of the event.</dd>
46	</dl>	48	</dl>
47	<dl><dt class="dlterm"><span class="uicontrol">Time</span></dt>	49	<dl><dt class="dlterm"><span class="uicontrol">Time</span></dt>
48	<dd>Displays the date and time of the particular test run. </dd>	50	<dd>Displays the date and time of the event.</dd>
49	</dl>	51	</dl>
50	<dl><dt class="dlterm"><span class="uicontrol">Text</span></dt>	52	<dl><dt class="dlterm"><span class="uicontrol">Text</span></dt>
51	<dd>Displays a message about the execution of the event that you selected	53	<dd>Displays a message for the event. </dd>
52	in the <span class="uicontrol">Events</span> tree. </dd>
53	</dl>	54	</dl>
54	</dd>	55	</dd>
55	<dt class="dlterm"><span class="uicontrol">Detailed Properties</span></dt>	56	<dt class="dlterm"><span class="uicontrol">Defects</span></dt>
		57	<dd>See <a href="../tasks/t_associating_defects.html">Associating defects with a test log</a>.</dd>
		58	<dt class="dlterm"><span class="uicontrol">Extended Properties</span></dt>
56	<dd>Displays properties for the event that you selected in the <span class="uicontrol">Events</span> tree. </dd>	59	<dd>Displays properties for the event that you selected in the <span class="uicontrol">Events</span> tree. </dd>
57	</dl>	60	</dl>
58	</div>	61	</div>
59	</div>	62	</div>
60	<div></div></body>	63
		64	<p>
		65	<b>Related tasks</b><br/>
		66	<a href="../tasks/t_searching_testlogs.html">Searching a test log</a><br/>
		67	<a href="../tasks/t_associating_defects.html">Associating defects with a test log</a><br/>
		68	</p>
		69
		70	</body>
61	</html>	71	</html>

Lines 36-48 Link Here

(-)tasks/tptpJUnitPluginTest_creatingManually.htm (-1 / +2 lines)
36	<li>Select <b>File</b> > <b>New</b> > <b>Other</b>.</li>	36	<li>Select <b>File</b> > <b>New</b> > <b>Other</b>.</li>
37	<li>Expand <b>Test</b>. Select <b>TPTP JUnit Plug-in Test</b>.</li>	37	<li>Expand <b>Test</b>. Select <b>TPTP JUnit Plug-in Test</b>.</li>
38	<li>Click <b>Next</b> to launch the <b>New JUnit Plug-in Test</b> dialog.	38	<li>Click <b>Next</b> to launch the <b>New JUnit Plug-in Test</b> dialog.
39	Identify the Source folder (<i>pluginProject</i>), the Package	39	Identify the Source folder (<i>pluginProject/src</i>), the Package
40	(<i>junit.plugin.samples</i>), and the name to be assigned to the JUnit Plug-in Test source code	40	(<i>junit.plugin.samples</i>), and the name to be assigned to the JUnit Plug-in Test source code
41	(<i>EclipseUiTest</i>).	41	(<i>EclipseUiTest</i>).
42	</li>	42	</li>
43	<li>Select either 'In the test editor' or 'In the code editor' for the test behavior option. See JUnit Test Suite Editor for a detailed explanation of these options.</li>	43	<li>Select either 'In the test editor' or 'In the code editor' for the test behavior option. See JUnit Test Suite Editor for a detailed explanation of these options.</li>
44	<li>Click <b>Next</b> and provide the test's name and location.</li>	44	<li>Click <b>Next</b> and provide the test's name and location.</li>
45	<li>Click <b>Next</b> and provide a description if required. Click <b>Finish</b>.</li>	45	<li>Click <b>Next</b> and provide a description if required. Click <b>Finish</b>.</li>
		46	<li>The <b>Confirm Open Editor</b> dialog may appear (see the <b>Window</b> > <b>Preferences...</b> > <b>Test</b> > <b>Open Editor</b> preference), confirming if the new JUnit Plug-in test suite is to be opened in the JUnit Plug-in Test editor.</li>
46	</ol>	47	</ol>
47	<p>Note that the second and third pages of the wizard are optional (that is, you can finish the wizard at the first page). Also, the difference between the information requested in page 1 and page 2 is as follows: the first page asks for the name and location of the source code, while the second one asks for the name and location of the TPTP Test (the model). By default, they are identical.</p>	48	<p>Note that the second and third pages of the wizard are optional (that is, you can finish the wizard at the first page). Also, the difference between the information requested in page 1 and page 2 is as follows: the first page asks for the name and location of the source code, while the second one asks for the name and location of the TPTP Test (the model). By default, they are identical.</p>
48	</body>	49	</body>

Lines 3-9 Link Here

(-)concepts/c_recuiwizard.html (-4 / +1 lines)
3	<html lang="en-us" xml:lang="en-us">	3	<html lang="en-us" xml:lang="en-us">
4	<!--	4	<!--
5	/**********************************************************************	5	/**********************************************************************
6	* Copyright (c) 2005, 2007 IBM Corporation.	6	* Copyright (c) 2005, 2008 IBM Corporation.
7	* All rights reserved. This content	7	* All rights reserved. This content
8	* is made available under the terms of the Eclipse Public License v1.0	8	* is made available under the terms of the Eclipse Public License v1.0
9	* which accompanies this distribution, and is available at	9	* which accompanies this distribution, and is available at
Lines 52-60 Link Here
52	recorder extension point documentation</a>.</p>	52	recorder extension point documentation</a>.</p>
53	</div>	53	</div>
54	<div>	54	<div>
55	<div class="familylinks">
56	<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/t_extgenrec.html" title="A test recorder captures user interactions with an application. These interactions are saved, and a test is generated from these recorded actions. Developing a test recorder entails adding the Generic Recorder extension point to the Generic Recorder Framework (GRF), and extending the recorder user interface wizard and the four main GRF helper classes.">Extending the generic test recorder</a></div>
57	</div>
58	<div class="relconcepts"><strong>Related concepts</strong><br />	55	<div class="relconcepts"><strong>Related concepts</strong><br />
59	<div><a href="c_genrecframework.html" title="The Generic Recorder Framework (GRF) provides a common user interface experience for all users that record tests. The GRF simplifies the process of extending a recorder by including a reusable extension point. For example, you could define one custom set of wizard pages to reuse for multiple recorders.">Generic Recorder Framework</a></div>	56	<div><a href="c_genrecframework.html" title="The Generic Recorder Framework (GRF) provides a common user interface experience for all users that record tests. The GRF simplifies the process of extending a recorder by including a reusable extension point. For example, you could define one custom set of wizard pages to reuse for multiple recorders.">Generic Recorder Framework</a></div>
60	<div><a href="c_testrecorders.html" title="A test recorder captures user interactions with an application. These interactions are saved, and a test is generated from these recorded actions.">Test recorders</a></div>	57	<div><a href="c_testrecorders.html" title="A test recorder captures user interactions with an application. These interactions are saved, and a test is generated from these recorded actions.">Test recorders</a></div>

Lines 3-9 Link Here

(-)concepts/c_testrecorders.html (-4 / +1 lines)
3	<html lang="en-us" xml:lang="en-us">	3	<html lang="en-us" xml:lang="en-us">
4	<!--	4	<!--
5	/**********************************************************************	5	/**********************************************************************
6	* Copyright (c) 2005, 2007 IBM Corporation.	6	* Copyright (c) 2005, 2008 IBM Corporation.
7	* All rights reserved. This content	7	* All rights reserved. This content
8	* is made available under the terms of the Eclipse Public License v1.0	8	* is made available under the terms of the Eclipse Public License v1.0
9	* which accompanies this distribution, and is available at	9	* which accompanies this distribution, and is available at
Lines 51-59 Link Here
51	including the user interface and the Agent Controller components.</p>	51	including the user interface and the Agent Controller components.</p>
52	</div>	52	</div>
53	<div>	53	<div>
54	<div class="familylinks">
55	<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/t_extgenrec.html" title="A test recorder captures user interactions with an application. These interactions are saved, and a test is generated from these recorded actions. Developing a test recorder entails adding the Generic Recorder extension point to the Generic Recorder Framework (GRF), and extending the recorder user interface wizard and the four main GRF helper classes.">Extending the generic test recorder</a></div>
56	</div>
57	<div class="relconcepts"><strong>Related concepts</strong><br />	54	<div class="relconcepts"><strong>Related concepts</strong><br />
58	<div><a href="c_genrecframework.html" title="The Generic Recorder Framework (GRF) provides a common user interface experience for all users that record tests. The GRF simplifies the process of extending a recorder by including a reusable extension point. For example, you could define one custom set of wizard pages to reuse for multiple recorders.">Generic Recorder Framework</a></div>	55	<div><a href="c_genrecframework.html" title="The Generic Recorder Framework (GRF) provides a common user interface experience for all users that record tests. The GRF simplifies the process of extending a recorder by including a reusable extension point. For example, you could define one custom set of wizard pages to reuse for multiple recorders.">Generic Recorder Framework</a></div>
59	<div><a href="c_recuiwizard.html" title="The recorder user interface wizard records a session with a Web application, generates a test from the recording, and then opens the test in the test editor.">Recorder user interface wizard</a></div>	56	<div><a href="c_recuiwizard.html" title="The recorder user interface wizard records a session with a Web application, generates a test from the recording, and then opens the test in the test editor.">Recorder user interface wizard</a></div>

Lines 3-9 Link Here

(-)concepts/c_genrecframework.html (-4 / +1 lines)
3	<html lang="en-us" xml:lang="en-us">	3	<html lang="en-us" xml:lang="en-us">
4	<!--	4	<!--
5	/**********************************************************************	5	/**********************************************************************
6	* Copyright (c) 2005, 2007 IBM Corporation.	6	* Copyright (c) 2005, 2008 IBM Corporation.
7	* All rights reserved. This content	7	* All rights reserved. This content
8	* is made available under the terms of the Eclipse Public License v1.0	8	* is made available under the terms of the Eclipse Public License v1.0
9	* which accompanies this distribution, and is available at	9	* which accompanies this distribution, and is available at
Lines 57-65 Link Here
57	<p>For more information about these classes, see the <a href="../../org.eclipse.tptp.platform.doc.isv/ref/rextpoint.xhtml#org.eclipse.hyades.test.core.Recorder">generic recorder extension point documentation</a>.</p>	57	<p>For more information about these classes, see the <a href="../../org.eclipse.tptp.platform.doc.isv/ref/rextpoint.xhtml#org.eclipse.hyades.test.core.Recorder">generic recorder extension point documentation</a>.</p>
58	</div>	58	</div>
59	<div>	59	<div>
60	<div class="familylinks">
61	<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/t_extgenrec.html" title="A test recorder captures user interactions with an application. These interactions are saved, and a test is generated from these recorded actions. Developing a test recorder entails adding the Generic Recorder extension point to the Generic Recorder Framework (GRF), and extending the recorder user interface wizard and the four main GRF helper classes.">Extending the generic test recorder</a></div>
62	</div>
63	<div class="relconcepts"><strong>Related concepts</strong><br />	60	<div class="relconcepts"><strong>Related concepts</strong><br />
64	<div><a href="c_testrecorders.html" title="A test recorder captures user interactions with an application. These interactions are saved, and a test is generated from these recorded actions.">Test recorders</a></div>	61	<div><a href="c_testrecorders.html" title="A test recorder captures user interactions with an application. These interactions are saved, and a test is generated from these recorded actions.">Test recorders</a></div>
65	<div><a href="c_recuiwizard.html" title="The recorder user interface wizard records a session with a Web application, generates a test from the recording, and then opens the test in the test editor.">Recorder user interface wizard</a></div>	62	<div><a href="c_recuiwizard.html" title="The recorder user interface wizard records a session with a Web application, generates a test from the recording, and then opens the test in the test editor.">Recorder user interface wizard</a></div>

Lines 3-9 Link Here

(-)tasks/t_portrecorder.html (-4 / +1 lines)
3	<html lang="en-us" xml:lang="en-us">	3	<html lang="en-us" xml:lang="en-us">
4	<!--	4	<!--
5	/**********************************************************************	5	/**********************************************************************
6	* Copyright (c) 2005, 2007 IBM Corporation.	6	* Copyright (c) 2005, 2008 IBM Corporation.
7	* All rights reserved. This content	7	* All rights reserved. This content
8	* is made available under the terms of the Eclipse Public License v1.0	8	* is made available under the terms of the Eclipse Public License v1.0
9	* which accompanies this distribution, and is available at	9	* which accompanies this distribution, and is available at
Lines 77-85 Link Here
77	</ol>	77	</ol>
78	</div>	78	</div>
79	<div>	79	<div>
80	<div class="familylinks">
81	<div class="parentlink"><strong>Parent topic:</strong> <a href="t_extgenrec.html" title="A test recorder captures user interactions with an application. These interactions are saved, and a test is generated from these recorded actions. Developing a test recorder entails adding the Generic Recorder extension point to the Generic Recorder Framework (GRF), and extending the recorder user interface wizard and the four main GRF helper classes.">Extending the generic test recorder</a></div>
82	</div>
83	<div class="relconcepts"><strong>Related concepts</strong><br />	80	<div class="relconcepts"><strong>Related concepts</strong><br />
84	<div><a href="../concepts/c_genrecframework.html" title="The Generic Recorder Framework (GRF) provides a common user interface experience for all users that record tests. The GRF simplifies the process of extending a recorder by including a reusable extension point. For example, you could define one custom set of wizard pages to reuse for multiple recorders.">Generic Recorder Framework</a></div>	81	<div><a href="../concepts/c_genrecframework.html" title="The Generic Recorder Framework (GRF) provides a common user interface experience for all users that record tests. The GRF simplifies the process of extending a recorder by including a reusable extension point. For example, you could define one custom set of wizard pages to reuse for multiple recorders.">Generic Recorder Framework</a></div>
85	<div><a href="../concepts/c_testrecorders.html" title="A test recorder captures user interactions with an application. These interactions are saved, and a test is generated from these recorded actions.">Test recorders</a></div>	82	<div><a href="../concepts/c_testrecorders.html" title="A test recorder captures user interactions with an application. These interactions are saved, and a test is generated from these recorded actions.">Test recorders</a></div>