Renaming Pages, Connections, and Requests

By default, names of recorded Page operations look like Page Page_ID (Page_Name) where Page_Name is the URL of the first request on that page.

For custom web pages that you add to the scenario during the recording or manually in the scenario editor, page name is the name you specify.

You can rename both recorded pages and pages you add to the scenario:

• Click Pages on the Scenario editor’s toolbar to group requests in the scenario by pages.

• Select the needed page in the scenario.

• Right-click the page and then click Rename.

  – or –

  Press F2.

  – or –

  Click the page twice (not a double click).

• Enter the needed name and press Enter to confirm the changes. Press ESC to discard the changes.

Connection names have the following format: Connection Connection_ID (Host_Name:Port). The Host_Name is the URL of the host, traffic to which LoadComplete will simulate through that connection.

To change the connection name:

• Click Connections on the Scenario editor’s toolbar to group operations by connections.

• Select the needed connection in the scenario.

• Right-click the connection and then click Rename.

  – or –

  Press F2.

  – or –

  Click the connection twice (not double-click).

• Enter the needed name for the connection. Press Enter to confirm the changes. Press ESC to discard the changes.

HTTP request headers have the format: Request Request ID (Resource_Name), where Resource_Name is the name of the requested resource or sent data.

The header of WebSocket requests has the following format: Request ID (Client Message) (for client messages) or Request ID (Server Message) (for server responses).

You can rename requests in scenarios:

• Select the needed request in the Scenario editor.

• Right-click the request and then click Rename.

  – or –

  Press F2.

  – or –

  Click the request twice (not a double click).

• Enter the needed name for the request. Press Enter to confirm the changes. Press ESC to discard the changes.