1.0 Introduction
2.0 Installation
3.0 Documentation
4.0 Limitations
Eclipse Test and Performance Tools Platform Project
Getting Started with TPTP's Manual Test Tools
Author: Paul Slauenwhite (paules@ca.ibm.com)
Last Updated:
Getting Started with
TPTP's Manual Test Tools
The
following document provides the necessary information for getting started with
the Manual Test Tools in TPTP.
Table of Contents:
The
Manual Test Tools are used to create, manage, and execute manual test suites
for manually testing applications by human testers based on textual test
descriptions.
1. Extract the Manual Test
Tools archive to the <Eclipse
installation directory>/dropins directory.
2. Start Eclipse with the -clean
option.
3. Regenerate the
configuration file for the Integrated Agent Controller:
1. Open the Integrated
Agent Controller's preferences (Window > Preferences... > Agent
Controller > Integrated Agent Controller).
2. Stop the Integrated
Agent Controller (Disable > Apply).
3. Restart the Integrated
Agent Controller (Enable > OK).
4. For Manual Test execution
using the Agent Controller:
1. Copy the <Eclipse installation
directory>/dropins/eclipse/plugins/org.eclipse.tptp.test.tools.manual_<version> plug-in to the <Agent Controller installation directory>/plugins/ directory.
2. Regenerate the configuration
file for the Agent Controller (see the Agent
Controller documentation).
3. Restart the Agent
Controller (see the Agent
Controller documentation).
For
more information on how to use the Manual Test Tools, see the Manual Test Tools
documentation in the TPTP workbench:
Help
> Help Contents > Testing applications > Testing manually
For
a flash tutorial on creating manual tests, watch Creating manual tests.
For
other TPTP limitations, see the Release Notes for this TPTP release.
1.
[Windows] Manual Test View requires Internet Explorer
When
executing a manual test suite, the Manual Test View requires Internet Explorer
v5 or above to be installed on the Windows host.
2.
[Windows Vista] Manual test suite execution terminates abnormally when running
the Agent Controller (AC) as a Widows Service
Bugzilla
ID: 171416
The
execution of a manual test suite terminates abnormally before the Manual Test
View appears when running the Agent Controller (AC) as a Windows Service on the
Windows Vista host.
This
issue is caused by insufficient privileges to start the Manual Test View when
running the Agent Controller (AC) as a Windows Service on the Windows Vista
host.
To
resolve this issue, execute the manual test suite when running the Agent
Controller (AC) as an application on the Windows Vista host.
For
more information, see Getting started with Agent Controller for Windows Vista.
3.
[Windows 64-bit] Manual tests do not run on 64-bit Windows platforms
Bugzilla
ID: 146102
The
manual test agent requires a 64-bit version of the SWT libraries. These
libraries are not currently packaged with the Agent Controller. If you need to
enable manual testing on these platforms you can copy the SWT jar files from
the 64-bit Eclipse workbench to the $TPTP_AC_HOME/bin directory.
4.
[Linux] Manual Test View requires an installed and configured Web browser
When
executing a manual test suite, the Manual Test View requires one of the follow
Web browsers to be installed on the Linux host:
·
Mozilla v1.4
·
Firefox v1.0 or above.
·
XULRunner v1.8.0.1 or above.
Additionally,
the installed Web browser must be configured by completing the following steps:
·
Set the MOZILLA_FIVE_HOME environment variable to the installation folder for the Web
browser (for example, export
MOZILLA_FIVE_HOME=<Web browser installation directory>).
·
Set the LD_LIBRARY_PATHMOZILLA_FIVE_HOME environment variable (for example, export LD_LIBRARY_PATH=$MOZILLA_FIVE_HOME:$LD_LIBRARY_PATH
5.
[Linux] Intermittent SWT error when executing a manual test suite
Intermittently,
the execution of a manual test suite terminates abnormally before the Manual
Test View appears on the Linux host. The following SWT error is captured as a
message event in the test log:
No more
handles [gtk_init_check() failed]
This
SWT error is caused by one of the following reasons:
·
Connection failure to the X server.
·
Insufficient memory for the Manual Test View process.
To
resolve this issue, complete the following steps:
·
Set the DISPLAY environment variable to the local
host name or IP address (for example, export
DISPLAY=<local host name or IP address>:0.0).
·
Correct the host name and port number in /etc/hosts.
·
Start the X server.
·
Increase the file descriptor limit.
Copyright © 2007, 2008
Author: Paul Slauenwhite