The tutorial is for all users of Mercury QuickTest Professional. The information presented here will
enable you to begin utilizing interface commands, accessing menu functions, and preparing for
If you have ever tested applications or Web sites manually, you are aware of the
drawbacks. Manual testing is time-consuming and tedious, requiring a heavy investment
in human resources. Time constraints often make it impossible to manually test every
feature thoroughly before the application is released. Serious bugs may have gone
undetected. Automated testing with QuickTest Professional addresses these problems by:
As QuickTest runs tests, it simulates a human user by moving the mouse cursor in
a Web page or application window, clicking Graphical User Interface (GUI) objects,
and entering keyboard input; however, QuickTest does this faster than any human user.
If you are using Internet Explorer as your browser, you should clear the option to use auto
complete for user names and passwords. This will ensure that all of your operations are
accurately recorded while creating your tests.
Before you begin creating tests, take a moment to become familiar with the main QuickTest
window. The image below shows QuickTest window as it would appear after you record a test,
with all toolbars and panes (except the Debug Viewer pane) displayed. Place your mouse over
the titles to display a description of these key elements.
1. Preparing to record
2. Recording a session on your application
3. Enhancing your test
4. Debugging your test
5. Running your test
6. Analyzing the test results
special window pane.
2. Check to see, that your application options are set for the purposes of your test.
3. View the settings in the Test Settings dialog box (Test > Settings) to ensure that data will
4. Review the Options dialog box (Tools > Options) to ensure that QuickTest will record and store information appropriately. For example, you should confirm that the test is set to use the appropriate object repository mode.
A step is any user action that causes or makes a change in your application, such as clicking a
link or image, or entering data in a form. For example, if you wanted to test your course
registration website, you would:
1. Create a new, blank, test file.
2. Click theRECORD button and enter the details about the type of application being tested.
3. Log on to your corporate website and perform the steps to register for a class.
4. Click theSTOP button to end the test.
This action might not be possible to undo. Are you sure you want to continue?