Editing a test

You can inspect and modify a test prior to compiling and running it.

By default, when you have finished recording an interaction with a browser-based application, the HTTP Proxy Recorder automatically starts the HTTP Test Generator, which produces a test from the recording. (You can modify this behavior - specify that a different test generator be started, or that none be started - by editing the HTTP Proxy Recorder preferences.) The test is not yet executable. You can immediately make the test executable by right-clicking it in the Test Navigator and selecting Generate. Or you can first edit the test by right-clicking it and selecting Open.

From Hyades, three types of test suite can be created and edited. The type created by the HTTP Test Generator is named Http Test Suite. The following figure illustrates what you see when you open an Http Test Suite. You see a slightly different organization when you open other types of tests.

The test opens in the Overview tab (see the bottom border) with the three edit areas (General Information and Source Information on the left and Http Requests on the right) expanded. You switch to the other edit panes by clicking the appropriate tab.

The General Information 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 Name box under General Information displays the name of the test. Initially, this is the same as the Test file name that you specified during recording, but 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 Test Navigator and displayed in the Name box, was originally b - same as the recording file name, without the suffix. The tester has decided to change the name to something more descriptive of the task that the test emulates, searchEmployeeDB.

The Source Information area displays the Java package name that will contain the test's executable Java code when it is generated, and the Java class implementing the test - same as the recording file name, without the suffix, with the initial character upper-cased. You can relocate the code to a different package by clicking the Browse button under the Package Name: box.

The Http Requests area on the right lists all HTTP requests in the test. Clicking one of these requests takes you to the Http Requests view, shown below.

You can also get to this edit pane by clicking the Http Requests tab along the bottom. When you click a request on the left, you see that request's properties on the right. You can:

Clicking the Behavior tab opens the behavior edit pane, shown below.

The HTTP requests initially recorded by the test are listed by page,, as invocations, inside a loop construct initially named Loop 1. With this loop selected, you can rename the loop, describe what it does, or change the Number of Iterations. With Synchronous checked and more than one iteration specified, the loop iterations execute in sequence. With Synchronous unchecked and more than one iteration specified, the loop iterations execute simultaneously. Inside Loop 1, you can:

With the Add button, you can create a new loop. Then, by right-clicking that new loop and selecting Invocation, you can populate the new loop with invocations of other test suites or test suite instances. You can also nest loops, and create invocations that are outside of any loop.

Parent topic: Performance Testing with TPTP

(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.