HTTP Recording into the Clip Editor

Document created by Chris Sommerstad Employee on Jul 20, 2017Last modified by Jijius Jabez on Aug 11, 2017
Version 2Show Document
  • View in full screen mode

HTTP Recording can be performed into the Clip Editor without the necessity to then convert the recording to a test clip. Messages are created inline in the Clip Editor.

Note: When using this feature note that the clip is created as if it were recorded in the Recording Editor and then converted using ALL THE wizard conversion DEFAULTS.

HTTP(S) Recording requires the SOASTA Conductor on the desktop client machine. Download it from the CloudTest, Resources page. Refer to Installing SOASTA Conductor for further instructions.

HTTP Recording sessions are started using the Record drop-down, HTTP Recording command and will capture data from both HTTP and HTTPS streams. If you are creating an HTTPS recording, note the following prerequisites:

  • HTTP(S) recording requires that the website being recorded has a valid SSL certificate. Refer to Creating an HTTP(S) Recording for more information on HTTP(S) recording. This means that:
    • The certificate has not expired.
    • The certificate is assigned to the host name that is being used when creating the recording. In other words, if the SSL certificate is issued to mysite.com, the recording cannot be created using the IP address or an internal host name.
  • Self-signed certificates are supported, provided that these two requirements are met.

TIP:  Users interested in packet-level recording that captures non-secure HTTP along with other packet types (i.e. UDP) will continue to use the Recording Editor to do so. Refer to Creating a Packet-Level Recording.

Recording in the Clip Editor

  1. Start the browser to record from, being sure to drop cache if necessary (i.e. if this is a site you frequently use with the given browser then you'll want a clean cache when you record).
  2. Start the SOASTA Conductor you will use to record. Once successfully logged on, the Conductor's status will be running.

  1. In CloudTest, select Central > Clips, and click the New icon. A new Untitled Test Clip opens in a Clip Editor tab. The Clip Editor, Record pop-up identifies the Record drop-down.

  1. Click the Record drop-down and select the Record HTTP command.

When you do so, the Choose a Conductor dialog box appears.

  1. Select your Conductor and ensure that its status is "connected," which is also visually indicated by the green font color. This will activate the Record button in the box.

TIP:  If the Conductor doesn't appear or isn't shown "Connected" ensure that it is connected as well as pointed to your CloudTest instance (in Conductor Preferences). Refer to Changing SOASTA Conductor for OS-specific instructions to do so on Macintosh, Windows, and Linux Conductors.

    1. Click Record to begin. The Choose a Conductor box will disappear and the Clip Editor goes into Record mode, which is indicated by the Clip Editor toolbar, Record drop-down button.

While recording, the Status Indicator will appear (upper right) to indicate the status of various recording tasks.

    • In the browser to record from, open the target site. Position the CloudTest window in such a way that you can easily view the Clip Editor while you interact with the target site in the second browser.
    • Perform the test actions on the target site. When you do so, the resulting messages will appear in the Clip Editor.

For example, in our clip we opened the Safari browser to the SOASTA Store sample site (http://www.soastastore.com/) and positioned it over the CloudTest browser window (which in this case is running Chrome).

The clip elements shown above are those recorded by the Clip Editor for the shown page.

HTTP(S) recordings into the Clip Editor will also create an underlying recording object (shown below), which is stored in the same folder that the clip was in at the time of the recording session.In general, HTTP(S) recording should be done from any supported browser other than the one running CloudTest.

While the Clip Editor is in Record mode, sessions can be paused and resumed according to need. While the Clip Editor is in Record mode, two commands will appear on the Record menu. Pause Recording – If a recording session is in progress, the user can choose this command to suspend recording.

While recording is paused, the Clip Editor's Status Indicator (top right) confirms this status.

A Clip Editor HTTP recording session lasts until Stop Recording is chosen from the menu. When Pause Recording is chosen, the recording session will be suspended until resumed or stopped.

      • Resume Recording – If recording is paused, the user can choose this command to restart the recording session.

Recording Locator

As of SOASTA 57, the recording locator red button indicates the insertion point of the next message that is received.

In previous builds, you could record directly into containers by adding and selecting the transaction, which would place the recording inside the container. However, in an effort to prevent accidentally changing record location and moving freely within the clip, this method will no longer be available. To record-into, right-click and select Record from here.

There is a difference between wanting to record into the container you marked, and after it.

  • You record into the container by expanding it so you can see the contents.
  • You record after the container by collapsing.

The image below shows a recording within a container. Everything will be recorded into that container until you select otherwise. Please note that the recording locator red button is on the inside.

In the case below, where recording is taking place after a container, the next recorded item will go right between Transaction1 and Delay2. Please note that the recording locator red button on the outside.

Attachments

    Outcomes