Material ID: GI11-6746-00
© Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
The latest version of this document is available at the following web site:
http://download.boulder.ibm.com/ibmdl/pub/software/rationalsdp/v7/rmt/70/docs/readme/readme.htmlAdditional updates about limitations and problems can be found in the form of individual technotes in the Support knowledge base at http://www.ibm.com/software/rational/support/. As problems are discovered and resolved, the IBM Rational Support team updates the knowledge base. By searching the knowledge base, you can quickly find solutions or workarounds to problems.
This file is available in the following national languages:
Brazilian Portuguese Chinese — Simplified Chinese — Traditional French German Italian Japanese Korean Spanish 1.1 New in this release
The following key new features are included in IBM Rational Manual Tester 7.0:
- Integration with Rational ClearQuest. Provided you have ClearQuest installed, the full ClearQuest client is available from within Manual Tester. For easy creation of defect records, you can map data from Manual Tester to ClearQuest automatically.
- Script publishing to HTML. You can now publish manual test scripts to HTML files.
- New Authoring Editor. You can import or paste tables from other applications, and perform multiple levels of undo and redo.
- New Test Log Viewer. The Test Log Viewer has been updated with new features, including defect-tracking system integration and the ability to attach external files, such as data or screen shots.
- New Welcome screen, with a new product tour and updated tutorials.
- Updated user interface. Improvements include a new Properties view, new icons, and improved Outline and Reuse views.
- Usability enhancements. There is better support for drag-and-drop within the editor and between the Reuse and Outline views.
For information about installing Manual Tester, installation prerequisites, installing from a command line, and using a local repository on an HTTP server, see the installation instructions at http://download.boulder.ibm.com/ibmdl/pub/software/rationalsdp/v7/rmt/70/docs/install_instruction/install.html .
If you upgrade a script from Manual Tester 6.1.x to Manual Tester 7.0, you cannot use it in Manual Tester 6.1.x anymore. Similarly, you cannot use scripts authored in version 7.0 in earlier versions of Manual Tester.
When upgrading scripts from Manual Tester 6.1.x, you open the script in Manual Tester 7.0 and are presented with options for upgrading the script:
- Click Yes to upgrade the script.
- Click No to cancel the action.
- Click Always to upgrade the current script and any scripts you open subsequently, without seeing a prompt.
If you click Always and later decide you want to be prompted to upgrade, you need to edit a preferences file. Using Notepad, open the following file:
Manual Tester installation directory\workspace\.metadata\.plugins\org.eclipse.core.runtime\.settings\com.ibm.rational.test.mt.prefsDelete the line AlwaysUpgradeDocuments=true. Then save the file and restart Manual Tester.
If a Word document was saved in Word's Outline view, the heading levels in the document will be lost upon import into Manual Tester. Everything from Word will be imported as part of a statement, without groups. This is due to a limitation with the Microsoft Word API. It is recommended not to use the Outline view for documents to be imported into Manual Tester.
When importing a test script from Microsoft Word format, if the Word document contains a table nested within another table, the outer table will be imported as a table, but only the text from the inner table will be imported. Formatting from the inner table is not preserved. Similarly, if there are hyperlinks inside the table, only the text of the hyperlinks from the inner table will be imported.
In order to import test script documents currently saved in IBM Rational Test Manager, Microsoft Word, or Microsoft Excel formats, you must have the .NET framework redistributable package (available from Microsoft) installed on the same computer as Manual Tester. To import test scripts from Test Manager, you also need to have Test Manager installed.
As long as .NET is installed prior to installing Manual Tester, imports should work. However, if you installed the .NET framework redistributable package after installing Manual Tester, you must run the file update_net.bat, located in your Manual Tester install directory. To run this file, simple double-click it in Windows Explorer. You only need to perform this step once.
In order to import scripts from Microsoft Word or Excel, you must have Word or Excel installed on the same computer as Manual Tester. The Import Test Document wizard has these import options enabled, even when Word or Excel is not installed. If you try to import from Word or Excel in this case, the import will fail with an error message.
When importing scripts from Rational TestManager ManualTest, perform your import into an empty folder. In the Import wizard, select the option "Overwrite existing test scripts without warning" and deselect the option "Open test scripts after import". This makes the import process run more quickly.
When you import some scripts from version 6.1.x, the full script may not be visible in the Authoring Editor. Sometimes the last few lines of the script are not shown, but you can see them in the Outline view.
The product tour (available from the Welcome screen) does not play if you are using one of the following national-language versions of Windows:
- Spanish
- Traditional Chinese
- Simplified Chinese
- Brazilian Portuguese
The online help recommends that multiple users can share a reuse file in order to facilitate script authoring in a team environment. However, when multiple users are saving changes to the same reuse file, their changes could overwrite one another. Shared reuse files should be set as read-only, and write permissions for the files should be carefully controlled.
The find and replace feature sometimes ignores the case sensitive setting. In the Find/Replace dialog box, if you select the All Occurrence and Case Sensitive options and then click Replace All, all occurrences of the search string will be found regardless of case.
The following information should have been included in the Accessibility section of the online help:
When navigating a table in the Authoring Editor, use the arrow keys to move forward and back, up and down.
Tables that have been imported or pasted into the Authoring Editor show a line after the table with a little dot at the beginning of the line. If you select this line together with the next statement and then delete the selection, both the table and the selected text will be deleted, even though the table itself was not selected.
To launch a URL embedded in a manual testing script, you must copy and paste the URL into a web browser.
In the Authoring Editor, if you have a very large image that fills your screen, you may not be able to see the end of the current statement. To place your cursor at the end of the statement (especially in order to press Enter to create another statement after it), first place the cursor directly to the left of the image. (Do this by clicking the mouse or using the arrow keys.) Then press the End key or right arrow key.
When you resize an image in a script, make sure to click in the statement that contains the image before resizing it. Otherwise the new size may not be saved.
Sometimes when you open a file that contains images and try to delete an image, the script does not recognize that it has changed. Therefore, Undo and Save are not available, and you are not reminded to save the file when you close it.
The Authoring Editor allows you to select, drag, and drop parts of reused (linked) statements. For example, you can select words or parts of words. However, dragging and dropping these partial reused statements is not supported. The changes are never saved.
When authoring a script, you can create a group with up to 9 levels of nesting. After the ninth subgroup folder is added to a group, no more will be inserted.
If you perform multiple undos and redos of adding a statement to a group, the Outline view and Authoring Editor can get out of synch, so they do not display identical content. To get them back in synch, save the file.
If you drag statements from the Reuse view and then undo your work, and then drag statements into the Authoring Editor and move them around (again, by dragging), the Authoring Editor and Outline view may get out of synch, so they do not display the same content. To get them back in synch, save the file.
When you paste from an external source into a statement that is a group, the following things may happen:
- If you paste something into a group statement, the statement displays a step icon.
- If you paste something into or after a child within a group, the text appears with a "1." in front of it and no statement icon.
You can resolve both problems by saving and closing the file, and then reopening it. The changes that you made by pasting are saved and the statement types are restored.
When copying from and pasting into the Authoring Editor, do not delete any part of the copied text before you paste, or data will be lost. It is important to paste first, then delete from the originally highlighted text that was copied. For example, if you have 3 statements:
1
2
3
You copy all three, then delete the second one, and then paste. Only the first and third statements will be pasted, as follows:1
3
If you copy text from the Help view and paste it into the Authoring Editor, Manual Tester will stop responding. To circumvent this problem, copy the text from the Help view, and then close the Help view before pasting the text into the Authoring Editor.
If you right-click on the frame of the Authoring Editor, you will see a context menu. The last menu item is New Editor. Selecting this item opens a new editor window, but any work you perform using this window cannot be saved reliably. Avoid using this menu item.
Under certain circumstances, you can get blank entries in the Defects tab of the Properties View. You can use the Defects tab of the Properties view to track any kind of ClearQuest record (not strictly defect records). The text that appears in the list of defects on Defects tab is taken from the ID field of the corresponding ClearQuest record. If no ID field exists for that record type, the name will be displayed. If neither an ID nor a name field exists, then the entry in the list will be blank.
Although you can use rich-text formatting (fonts, colors, bold, italics, and so forth), images, and hyperlinks in a table when authoring a script, all table text, including formatted hyperlinks, is displayed as plain text in the Run Test Script window. Images in tables are not displayed in the Run Test Script window. It is a best practice to avoid using text formatting or images in tables.
The Run Test Script window is small by default. Large images placed in scripts may be larger than the window itself, so you are unable to view the full image. The workaround is to resize large images in the Authoring Editor so that they will fit when the script is run.
With transparency turned on in the Run Test Script window, sometimes the "current statement" arrow does not move to the next statement when you click Apply. Also, the window may appear blank, flash, or fail to display images. To solve the issue, turn off transparency:
- Close the Run Test Script window, stopping your test.
- In the main window, click Window > Preferences.
- On the Main tab, set the transparency slider to 0, and then click OK.
This issue affects scripts that are run from within Rational Test Manager. When browsing results in the Test Manager log viewer, you can right-click an event and choose Open Script. If the script name contains a space, you will see an error and the file will not open. The workaround is to browse to and open the file using Manual Tester or Windows Explorer, or to avoid using spaces in filenames.
Customer support will provide instructions for downloading the Rational Agent Controller, which will allow you to run your manual tests remotely.
When installing Manual Tester in a Citrix environment, the installer should run Manual Tester at least once while logged in as an administrator (who has write access). This allows the application to configure itself properly. If you do not do this, Manual Tester will display the wrong script icons when it is run.
When using Manual Tester with Citrix, do not use transparency with the Run Test Script window. Leave the transparency setting at 0.
When using Manual Tester with Citrix, you cannot have more than one admin user logged in simultaneously. Additional admin users will see errors and will not be able to perform their tasks.
If your test log contains double-byte characters, the exported CSV file cannot be read properly with Microsoft Excel, due to Excel limitations with unicode. The workaround is to open and save the CSV file first with Notepad. In Notepad, choose File > Save As. Then in the Save As dialog box, in the Encoding field choose "Unicode" and save the file. Double-byte characters in the newly saved file will display properly in Excel.
The Manual Tester uninstallation does not remove certain configuration files. These files record window size, window position, and so forth. If you later reinstall on top of an old directory where these files remain, you will see the old configuration. To reinstall cleanly, make sure to first delete the old configuration directory and its contents. The directory is located in your Manual Tester installation directory; for example, C:\Program Files\IBM\RMT70\configuration.
IBM Rational Software Support provides you with technical assistance.
For contact information and guidelines or reference materials that you will need when you require support, read the IBM Software Support Handbook.
For FAQs, lists of know problems and fixes, and other support information, visit the IBM Rational Software Support Web site.
For Rational software product news, events, and other information, visit the IBM Rational Software Web site.
Before you contact IBM Rational Software Support, gather the background information that you will need to describe your problem. When describing a problem to an IBM software support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions:
- What software versions were you running when the problem occurred?
- Do you have logs, traces, or messages that are related to the problem?
- Can you reproduce the problem? If so, what steps do you take to reproduce it?
- Is there a workaround for the problem? If so, be prepared to describe the workaround.
Documentation notices for Rational Manual Tester
© Copyright IBM Corporation 2004, 2006.
The XDoclet Documentation included in this IBM product is used with permission and is covered under the following copyright attribution statement:Copyright © 2000-2004, XDoclet Team. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this documentation in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this documentation. The furnishing of this documentation does not give you any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
Licensees of this program who wish to have information about it for the purpose of enabling:
(i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
Intellectual Property Dept. for Rational Software
IBM Corporation
20 Maguire Road
Lexington, Massachusetts 02421-3112
U.S.A.
Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.The licensed program described in this documentation and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.
Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples may include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.
Copyright license
This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing,
using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows:©(your company name) (year). Portions of this code are derived from IBM Corp.
Sample Programs. © Copyright IBM Corp. 2004, 2006.Trademarks and service marks
The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:
ClearCase
ClearQuest
IBM
Lotus Notes
RationalJava and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.
Other company, product or service names, may be trademarks or service marks of others.