Attachment 102903 Details for Bug 213622 – Patch.

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

[patch] Patch.

Defect_213622_Patch.txt (text/plain), 63.88 KB, created by Paul Slauenwhite

on 2008-05-30 12:47:57 EDT

(hide)

Description:

Filename:

MIME Type:

Creator: Paul Slauenwhite

Created: 2008-05-30 12:47:57 EDT

Size: 63.88 KB

patch

obsolete

>### Eclipse Workspace Patch 1.0
>#P org.eclipse.tptp.test.tools.manual.doc.user
>Index: tasks/tcreatingamanualtest.htm
>===================================================================
>RCS file: /cvsroot/tptp/test/org.eclipse.tptp.test.tools.manual.doc.user/tasks/tcreatingamanualtest.htm,v
>retrieving revision 1.4
>diff -u -r1.4 tcreatingamanualtest.htm
>--- tasks/tcreatingamanualtest.htm	9 Apr 2008 19:57:57 -0000	1.4
>+++ tasks/tcreatingamanualtest.htm	30 May 2008 16:47:41 -0000
>@@ -38,7 +38,7 @@
> 	<li>Expand the <b>Test</b> folder, then select <b>TPTP Manual Test</b>.</li>
> 	<li>Click <b>Next</b>, select the location (<i>generalProject</i>), and name the manual test suite, for example, <i>exampleManualTest</i>.</li>
> 	<li>Click <b>Next</b> and optionally provide a description for the manual test suite. Click <b>Finish</b>.</li>
>-	<li>A manual test suite file (exampleManualTest.testsuite) will be created, becomes visible in the Test Navigator and opens in the Manual Test editor.</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 manual test suite is to be opened in the Manual Test editor.</li>	
> </ol>
> 
> <p><strong>Related tasks</strong><br />
>#P org.eclipse.hyades.test.doc.user
>Index: concepts/cdatapools.htm
>===================================================================
>RCS file: /cvsroot/tptp/test/org.eclipse.hyades.test.doc.user/concepts/cdatapools.htm,v
>retrieving revision 1.16
>diff -u -r1.16 cdatapools.htm
>--- concepts/cdatapools.htm	11 May 2007 11:17:06 -0000	1.16
>+++ concepts/cdatapools.htm	30 May 2008 16:47:42 -0000
>@@ -4,7 +4,7 @@
> <head>
> </a>
> <h1 class="topictitle1">Associating defects with a test log</h1>
>-<div><p>Use the Test Log viewer to associate defects with a test log using
>-the defect number. Associated defects are conveniently displayed in the test
>-log as links to the defect database.</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 associate an existing defect with a test log, 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 defect.</span></li>
>-<li class="stepexpand"><span>Under <span class="wintitle">Defects</span>, click <span class="uicontrol">Add</span>.</span></li>
>-<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
>-link to view the record in the defect database.</li>
>-<li class="stepexpand"><span>If you do not know the defect number, you can search the defect
>-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>
>+<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>
> </ol>
>-<div class="section">Similarly, click <span class="uicontrol">Remove</span> to remove defects
>-from the test log.</div>
>+
>+<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>
>-<div></div></body>
>+</body>
> </html>
>\ No newline at end of file
>Index: tasks/t_viewingevents.html
>===================================================================
>RCS file: /cvsroot/tptp/test/org.eclipse.hyades.test.doc.user/tasks/t_viewingevents.html,v
>retrieving revision 1.10
>diff -u -r1.10 t_viewingevents.html
>--- tasks/t_viewingevents.html	3 May 2007 14:33:14 -0000	1.10
>+++ tasks/t_viewingevents.html	30 May 2008 16:47:42 -0000
>@@ -3,7 +3,7 @@
> <html lang="en-us" xml:lang="en-us">
> </a>
>-
>+<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>
> 
>-<br />
>-<br />
>-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
>-	border="0" src="../images/dpEditor_OverviewTab.gif" width="844"
>-	height="421" alt=""/>
>-</div>
>-<div class="p"><span></span>
>-<p><b class="parentlink"><br />
>-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 />
>+<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>
> <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>
>Index: tasks/topendp.htm
>===================================================================
>RCS file: /cvsroot/tptp/test/org.eclipse.hyades.test.doc.user/tasks/topendp.htm,v
>retrieving revision 1.10
>diff -u -r1.10 topendp.htm
>--- tasks/topendp.htm	3 May 2007 14:33:14 -0000	1.10
>+++ tasks/topendp.htm	30 May 2008 16:47:42 -0000
>@@ -3,7 +3,7 @@
> <html lang="en-us" xml:lang="en-us">
> 
>-<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>
>\ No newline at end of file
>Index: tasks/tcreatingaperformancetest.htm
>===================================================================
>RCS file: /cvsroot/tptp/test/org.eclipse.hyades.test.doc.user/tasks/tcreatingaperformancetest.htm,v
>retrieving revision 1.2
>diff -u -r1.2 tcreatingaperformancetest.htm
>--- tasks/tcreatingaperformancetest.htm	9 Apr 2008 19:58:07 -0000	1.2
>+++ tasks/tcreatingaperformancetest.htm	30 May 2008 16:47:42 -0000
>@@ -38,16 +38,10 @@
> 	<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>A performance test suite file (examplePerformanceTest.testsuite) will be created, becomes visible in the Test Navigator and opens in the URL Test editor.</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>
>Index: tasks/tptpJUnitTest_importing.htm
>===================================================================
>RCS file: /cvsroot/tptp/test/org.eclipse.hyades.test.doc.user/tasks/tptpJUnitTest_importing.htm,v
>retrieving revision 1.12
>diff -u -r1.12 tptpJUnitTest_importing.htm
>--- tasks/tptpJUnitTest_importing.htm	9 Apr 2008 19:58:07 -0000	1.12
>+++ tasks/tptpJUnitTest_importing.htm	30 May 2008 16:47:42 -0000
>@@ -66,10 +66,7 @@
> 	<li>
> 	Navigate to the required files and then click on <b>Finish</b>.
> 	</li>
>-	<li>
>-	The outcome of a successful import operation will be a TPTP 
>-	JUnit Test File associated with the imported package or class.
>-	</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>	
> </ul>
> 
> <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>
>Index: tasks/tcreatetestreports.htm
>===================================================================
>RCS file: /cvsroot/tptp/test/org.eclipse.hyades.test.doc.user/tasks/tcreatetestreports.htm,v
>retrieving revision 1.5
>diff -u -r1.5 tcreatetestreports.htm
>--- tasks/tcreatetestreports.htm	30 Apr 2008 11:40:22 -0000	1.5
>+++ tasks/tcreatetestreports.htm	30 May 2008 16:47:42 -0000
>@@ -49,10 +49,6 @@
> 		<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>
> 
>@@ -61,7 +57,7 @@
> <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 report <b>Test</b> &gt; <b>Test Reports</b> &gt; <b>Fonts</b> preference page.</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>
>@@ -73,6 +69,7 @@
>   <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>
>Index: tasks/tgenerateexecutabletest.htm
>===================================================================
>RCS file: /cvsroot/tptp/test/org.eclipse.hyades.test.doc.user/tasks/tgenerateexecutabletest.htm,v
>retrieving revision 1.11
>diff -u -r1.11 tgenerateexecutabletest.htm
>--- tasks/tgenerateexecutabletest.htm	3 May 2007 14:33:14 -0000	1.11
>+++ tasks/tgenerateexecutabletest.htm	30 May 2008 16:47:42 -0000
>@@ -3,7 +3,7 @@
> <html lang="en-us" xml:lang="en-us">
> <!-- 
> /**********************************************************************
>- * Copyright (c) 2004, 2007 IBM Corporation.
>+ * 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
>@@ -47,20 +47,16 @@
> <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">Java Project</span> field, accept the default
>-or click <span class="uicontrol">Browse</span> to select the Java project in which
>+<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">Source folder</span> field, accept the
>-default or click <span class="uicontrol">Browse</span> to select the folder in the
>-selected 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>
>Index: tasks/t_searching_testlogs.html
>===================================================================
>RCS file: /cvsroot/tptp/test/org.eclipse.hyades.test.doc.user/tasks/t_searching_testlogs.html,v
>retrieving revision 1.3
>diff -u -r1.3 t_searching_testlogs.html
>--- tasks/t_searching_testlogs.html	3 May 2007 14:33:14 -0000	1.3
>+++ tasks/t_searching_testlogs.html	30 May 2008 16:47:42 -0000
>@@ -3,7 +3,7 @@
> <html lang="en-us" xml:lang="en-us">
> <!-- 
> /**********************************************************************
>- * Copyright (c) 2006, 2007 IBM Corporation.
>+ * 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
>@@ -44,8 +44,7 @@
> you want to find. </span></li>
> <li><span>To make the search case-sensitive, select the appropriate option. </span></li>
> <li><span>To search only a portion of the test log, click <span class="uicontrol">Restrict
>-to descendants of selected element</span> or <span class="uicontrol">Search only immediate
>-descendants</span>. These options refer to the element you currently
>+to descendants of selected element</span>. This option refers to the element you currently
> have selected in the Events page of the test log. </span></li>
> <li><span>Optionally, use <span class="uicontrol">Elements to Search</span> to limit
> your search to certain event types. Additional options are displayed for each
>Index: tasks/tcreatelocation.htm
>===================================================================
>RCS file: /cvsroot/tptp/test/org.eclipse.hyades.test.doc.user/tasks/tcreatelocation.htm,v
>retrieving revision 1.6
>diff -u -r1.6 tcreatelocation.htm
>--- tasks/tcreatelocation.htm	18 Apr 2008 16:04:05 -0000	1.6
>+++ tasks/tcreatelocation.htm	30 May 2008 16:47:42 -0000
>@@ -38,6 +38,7 @@
>     <li>Enter the host name or IP address of the target host. By default, <i>localhost</i> is entered.  Test the 
>     connection to the target host by clicking the <b>Test Connection</b> link<sup>1</sup>.</li>
>     <li>Click <b>Finish</b> to create the test location.</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 location is to be opened in the Location editor.</li>
> </ol>
> 
> <p>[1] The <a href="../../org.eclipse.tptp.platform.agentcontroller.doc.user/concepts/ac/c_ac_ovr.html">Agent Controller</a> or 
>Index: tasks/tcreateperformancetestreports.htm
>===================================================================
>RCS file: /cvsroot/tptp/test/org.eclipse.hyades.test.doc.user/tasks/tcreateperformancetestreports.htm,v
>retrieving revision 1.6
>diff -u -r1.6 tcreateperformancetestreports.htm
>--- tasks/tcreateperformancetestreports.htm	30 Apr 2008 11:40:22 -0000	1.6
>+++ tasks/tcreateperformancetestreports.htm	30 May 2008 16:47:42 -0000
>@@ -71,7 +71,7 @@
> <p>Configure the fonts used when generating a performance test report:</p>
> <ol>
>  	<li>Select <b>Window</b> &gt; <b>Preferences...</b> from the file menu.</li>
>-	<li>Select the report <b>Test</b> &gt; <b>Test Reports</b> &gt; <b>Fonts</b> preference page.</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 performance test report.</li>
> 	<li>Click <b>OK</b> to save the preferences.</li>
> </ol>
>@@ -83,6 +83,7 @@
>   <li>Provide the parent folder and the name for the performance test report and click <b>Next</b>.</li>
>   <li>Optionally, provide the report window (start and end data and time) for the performance test report.</li>
>   <li>Click <b>Finish </b> to generate the performance 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 performance test report is to be opened in the internal Web Browser.</li>	
> </ol>
> 
> </body>
>Index: tasks/tcreatedp.htm
>===================================================================
>RCS file: /cvsroot/tptp/test/org.eclipse.hyades.test.doc.user/tasks/tcreatedp.htm,v
>retrieving revision 1.13
>diff -u -r1.13 tcreatedp.htm
>--- tasks/tcreatedp.htm	3 May 2007 14:33:14 -0000	1.13
>+++ tasks/tcreatedp.htm	30 May 2008 16:47:42 -0000
>@@ -3,7 +3,7 @@
> <html lang="en-us" xml:lang="en-us">
> <!-- 
> /**********************************************************************
>- * Copyright (c) 2004, 2007 IBM Corporation.
>+ * 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
>@@ -75,8 +75,10 @@
> 	</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
>@@ -86,8 +88,6 @@
> 
> <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 />
>Index: toc/logviewer_toc.xml
>===================================================================
>RCS file: /cvsroot/tptp/test/org.eclipse.hyades.test.doc.user/toc/logviewer_toc.xml,v
>retrieving revision 1.1
>diff -u -r1.1 logviewer_toc.xml
>--- toc/logviewer_toc.xml	5 Dec 2007 20:04:00 -0000	1.1
>+++ toc/logviewer_toc.xml	30 May 2008 16:47:42 -0000
>@@ -1,7 +1,7 @@
> <?xml version="1.0" encoding="utf-8"?>
> <!-- 
> /**********************************************************************
>- * Copyright (c) 2007 IBM Corporation.
>+ * Copyright (c) 2007, 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
>@@ -21,7 +21,6 @@
> 		  <topic label="Test Log viewer Events page" href="ref/r_testlog_events.html"/>
> 		  <topic label="Test Log viewer Events toolbar" href="ref/r_testlog_toolbar.html"/>
> 	   	  <topic label="Searching a test log" href="tasks/t_searching_testlogs.html"/>
>-	      <topic label="Submitting defects" href="tasks/t_submitting_defects.html"/>
> 	      <topic label="Associating defects with a test log" href="tasks/t_associating_defects.html"/>
> 	  </topic>
>    </topic>
>Index: ref/r_testlog_toolbar.html
>===================================================================
>RCS file: /cvsroot/tptp/test/org.eclipse.hyades.test.doc.user/ref/r_testlog_toolbar.html,v
>retrieving revision 1.4
>diff -u -r1.4 r_testlog_toolbar.html
>--- ref/r_testlog_toolbar.html	3 May 2007 14:33:15 -0000	1.4
>+++ ref/r_testlog_toolbar.html	30 May 2008 16:47:42 -0000
>@@ -3,7 +3,7 @@
> <html lang="en-us" xml:lang="en-us">
> <!-- 
> /**********************************************************************
>- * Copyright (c) 2006, 2007 IBM Corporation.
>+ * 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
>@@ -77,5 +77,12 @@
> the Events page.</p>
> </div>
> </div>
>-<div></div></body>
>+
>+<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>
>\ No newline at end of file
>Index: ref/r_testlog_overview.html
>===================================================================
>RCS file: /cvsroot/tptp/test/org.eclipse.hyades.test.doc.user/ref/r_testlog_overview.html,v
>retrieving revision 1.4
>diff -u -r1.4 r_testlog_overview.html
>--- ref/r_testlog_overview.html	3 May 2007 14:33:15 -0000	1.4
>+++ ref/r_testlog_overview.html	30 May 2008 16:47:42 -0000
>@@ -3,7 +3,7 @@
> <html lang="en-us" xml:lang="en-us">
> <!-- 
> /**********************************************************************
>- * Copyright (c) 2006, 2007 IBM Corporation.
>+ * 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
>@@ -59,8 +59,11 @@
> <dd>Displays the path and filename of the test suite file that was run.</dd>
> </dl>
> <dl><dt class="dlterm"><span class="uicontrol">Host name</span></dt>
>-<dd>Displays the name of the computer on which the test was run.</dd>
>-</dl>
>+<dd>Displays the name of the computer on which the test was run.</dd></dl>
>+<dl><dt class="dlterm"><span class="uicontrol">Deployment (optional)</span></dt>
>+<dd>Displays the name and link to the test deployment that was run.</dd></dl>
>+<dl><dt class="dlterm"><span class="uicontrol">Location (optional)</span></dt>
>+<dd>Displays the name and link to the test location that was run.</dd></dl>
> </dd>
> </dl>
> <dl><dt class="dlterm"><span class="uicontrol">Verdict Summary</span></dt>
>@@ -82,5 +85,11 @@
> page.</p>
> </div>
> </div>
>-<div></div></body>
>+
>+<p>
>+<b>Related tasks</b><br/>
>+<a href="../tasks/t_searching_testlogs.html">Searching a test log</a><br/>
>+</p>
>+
>+</body>
> </html>
>\ No newline at end of file
>Index: ref/r_testlog_events.html
>===================================================================
>RCS file: /cvsroot/tptp/test/org.eclipse.hyades.test.doc.user/ref/r_testlog_events.html,v
>retrieving revision 1.4
>diff -u -r1.4 r_testlog_events.html
>--- ref/r_testlog_events.html	3 May 2007 14:33:15 -0000	1.4
>+++ ref/r_testlog_events.html	30 May 2008 16:47:42 -0000
>@@ -3,7 +3,7 @@
> <html lang="en-us" xml:lang="en-us">
> <!-- 
> /**********************************************************************
>- * Copyright (c) 2006, 2007 IBM Corporation.
>+ * 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
>@@ -36,26 +36,36 @@
> <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">Common
>-Properties</span> and <span class="uicontrol">Detailed Properties</span>. </dd>
>+the properties of the selected event or object are displayed under <span class="uicontrol">Properties</span> and <span class="uicontrol">Extended Properties</span>. </dd>
> </dl>
>-<dl><dt class="dlterm"><span class="uicontrol">Common Properties</span></dt>
>-<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>
>-<dd>Click to open the test suite, test case, or test behavior of the event
>-that you selected in the <span class="uicontrol">Events</span> tree.</dd>
>+<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 particular test run. </dd>
>+<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 about the execution of the event that you selected
>-in the <span class="uicontrol">Events</span> tree. </dd>
>+<dd>Displays a message for the event. </dd>
> </dl>
> </dd>
>-<dt class="dlterm"><span class="uicontrol">Detailed Properties</span></dt>
>+<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>
>-<div></div></body>
>+
>+<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>
>\ No newline at end of file
>#P org.eclipse.tptp.test.tools.junit.plugin.doc.user
>Index: tasks/tptpJUnitPluginTest_importing.htm
>===================================================================
>RCS file: /cvsroot/tptp/test/org.eclipse.tptp.test.tools.junit.plugin.doc.user/tasks/tptpJUnitPluginTest_importing.htm,v
>retrieving revision 1.1
>diff -u -r1.1 tptpJUnitPluginTest_importing.htm
>--- tasks/tptpJUnitPluginTest_importing.htm	9 Apr 2008 19:57:53 -0000	1.1
>+++ tasks/tptpJUnitPluginTest_importing.htm	30 May 2008 16:47:43 -0000
>@@ -66,10 +66,7 @@
> 	<li>
> 	Navigate to the required files and then click on <b>Finish</b>.
> 	</li>
>-	<li>
>-	The outcome of a successful import operation will be a TPTP 
>-	JUnit Plug-in Test File associated with the imported package or class.
>-	</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>	
> </ul>
> 
> <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>
>Index: tasks/tptpJUnitPluginTest_creatingManually.htm
>===================================================================
>RCS file: /cvsroot/tptp/test/org.eclipse.tptp.test.tools.junit.plugin.doc.user/tasks/tptpJUnitPluginTest_creatingManually.htm,v
>retrieving revision 1.1
>diff -u -r1.1 tptpJUnitPluginTest_creatingManually.htm
>--- tasks/tptpJUnitPluginTest_creatingManually.htm	9 Apr 2008 19:57:53 -0000	1.1
>+++ tasks/tptpJUnitPluginTest_creatingManually.htm	30 May 2008 16:47:43 -0000
>@@ -36,13 +36,14 @@
> 	<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</i>), the Package
>+	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>
>#P org.eclipse.tptp.test.report.birt.doc.user
>Index: tasks/treporttest.xhtml
>===================================================================
>RCS file: /cvsroot/tptp/test/org.eclipse.tptp.test.report.birt.doc.user/tasks/treporttest.xhtml,v
>retrieving revision 1.14
>diff -u -r1.14 treporttest.xhtml
>--- tasks/treporttest.xhtml	18 Apr 2008 16:04:09 -0000	1.14
>+++ tasks/treporttest.xhtml	30 May 2008 16:47:44 -0000
>@@ -67,6 +67,7 @@
>   <li>Provide the parent folder and the name for the BIRT test report and click <b>Next</b>.</li>
>   <li>Optionally, provide the report window (start and end data and time) for the BIRT test report.</li>
>   <li>Click <b>Finish </b> to generate the BIRT 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 BIRT test report is to be opened in the internal Web Browser or text editor.</li>	
> </ol>
> </body>
> </html>
>#P org.eclipse.tptp.test.recorders.url.doc.user
>Index: tasks/trecordtest.html
>===================================================================
>RCS file: /cvsroot/tptp/test/org.eclipse.tptp.test.recorders.url.doc.user/tasks/trecordtest.html,v
>retrieving revision 1.4
>diff -u -r1.4 trecordtest.html
>--- tasks/trecordtest.html	18 Apr 2008 16:04:12 -0000	1.4
>+++ tasks/trecordtest.html	30 May 2008 16:47:44 -0000
>@@ -107,6 +107,8 @@
> recording, close your browser or click on the <span class="uicontrol">Stop Recording</span>
> button on the right side of the Recorder Control
> view bar. </span> A progress window opens while the test is generated. </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 class="section">By default, when you have finished recording an interaction with a browser-based application, 
> the Recorder Control view displays the message <tt class="sysout">Test
>@@ -115,10 +117,5 @@
> by editing the URL Recorder preferences.)</div>
> </div>
> 
>-<div>
>-<p>
>-<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" />
>-</p>
>-</div>
> </body>
> </html>
>\ No newline at end of file
>#P org.eclipse.tptp.test.doc.isv
>Index: concepts/c_recuiwizard.html
>===================================================================
>RCS file: /cvsroot/tptp/test/org.eclipse.tptp.test.doc.isv/concepts/c_recuiwizard.html,v
>retrieving revision 1.3
>diff -u -r1.3 c_recuiwizard.html
>--- concepts/c_recuiwizard.html	3 May 2007 14:33:08 -0000	1.3
>+++ concepts/c_recuiwizard.html	30 May 2008 16:47:45 -0000
>@@ -3,7 +3,7 @@
> <html lang="en-us" xml:lang="en-us">
> <!--
> /**********************************************************************
>- * Copyright (c) 2005, 2007 IBM Corporation.
>+ * 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
>@@ -52,9 +52,6 @@
> 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>
>Index: concepts/c_testrecorders.html
>===================================================================
>RCS file: /cvsroot/tptp/test/org.eclipse.tptp.test.doc.isv/concepts/c_testrecorders.html,v
>retrieving revision 1.3
>diff -u -r1.3 c_testrecorders.html
>--- concepts/c_testrecorders.html	3 May 2007 14:33:08 -0000	1.3
>+++ concepts/c_testrecorders.html	30 May 2008 16:47:45 -0000
>@@ -3,7 +3,7 @@
> <html lang="en-us" xml:lang="en-us">
> <!--
> /**********************************************************************
>- * Copyright (c) 2005, 2007 IBM Corporation.
>+ * 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
>@@ -51,9 +51,6 @@
> 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>
>Index: concepts/c_exnewtestrec.html
>===================================================================
>RCS file: /cvsroot/tptp/test/org.eclipse.tptp.test.doc.isv/concepts/c_exnewtestrec.html,v
>retrieving revision 1.6
>diff -u -r1.6 c_exnewtestrec.html
>--- concepts/c_exnewtestrec.html	24 Mar 2008 16:42:14 -0000	1.6
>+++ concepts/c_exnewtestrec.html	30 May 2008 16:47:45 -0000
>@@ -57,9 +57,6 @@
> 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="reltasks"><strong>Related tasks</strong><br />
> <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>
> </div>
>Index: concepts/c_genrecframework.html
>===================================================================
>RCS file: /cvsroot/tptp/test/org.eclipse.tptp.test.doc.isv/concepts/c_genrecframework.html,v
>retrieving revision 1.3
>diff -u -r1.3 c_genrecframework.html
>--- concepts/c_genrecframework.html	3 May 2007 14:33:08 -0000	1.3
>+++ concepts/c_genrecframework.html	30 May 2008 16:47:45 -0000
>@@ -3,7 +3,7 @@
> <html lang="en-us" xml:lang="en-us">
> <!--
> /**********************************************************************
>- * Copyright (c) 2005, 2007 IBM Corporation.
>+ * 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
>@@ -57,9 +57,6 @@
> <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>
>Index: tasks/t_portrecorder.html
>===================================================================
>RCS file: /cvsroot/tptp/test/org.eclipse.tptp.test.doc.isv/tasks/t_portrecorder.html,v
>retrieving revision 1.4
>diff -u -r1.4 t_portrecorder.html
>--- tasks/t_portrecorder.html	3 May 2007 14:33:09 -0000	1.4
>+++ tasks/t_portrecorder.html	30 May 2008 16:47:45 -0000
>@@ -3,7 +3,7 @@
> <html lang="en-us" xml:lang="en-us">
> <!--
> /**********************************************************************
>- * Copyright (c) 2005, 2007 IBM Corporation.
>+ * 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
>@@ -77,9 +77,6 @@
> </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>
>Index: tasks/t_cretestrec.html
>===================================================================
>RCS file: /cvsroot/tptp/test/org.eclipse.tptp.test.doc.isv/tasks/t_cretestrec.html,v
>retrieving revision 1.5
>diff -u -r1.5 t_cretestrec.html
>--- tasks/t_cretestrec.html	24 Mar 2008 16:42:14 -0000	1.5
>+++ tasks/t_cretestrec.html	30 May 2008 16:47:45 -0000
>@@ -109,9 +109,6 @@
> </div>
> </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>

Actions: View | Diff

Attachments on bug 213622: 102903