Sometimes it is necessary to inspect or modify a recorded or replayed session by itself. Session Inspector is a tool for browsing and editing session content.

    There are several ways to open Session Inspector,

    • double-click Recorded or Replayed session in the verification tree.
    • double-click Recorded session in the Test Case tree.
    • double-click a session bar in the Waterfall.

    A new tab with the following information will open:

    1. The request is displayed on the top.

    2. The response is displayed on the bottom.

    3. The recorded and replayed session inspectors are marked accordingly. Replayed session display VU number, iteration and a test case associated was the replayed session.

    4. You can search the request and the response independently using the Find boxes.

    5. To edit the session, click Unlock for Editing.

    6. To save changes, click Save.

    7. To quickly auto size the request and response panes, use resize buttons:

        • Split the window at 1/4
        • Split the window at 1/2
        • Split the window at 3/4

     

    Icon

    Note: To open Session Inspector, session content must be saved in storage accessible from the controller. This information is available in tests that ran from the controller without agents. In distributed  tests, when SQL Server is used as storage, this information is also available on the controller as well. However, in distributed tests with SQL Server CE-based storage, the sessions initiated on the agents are stored on the agents. You still can open such sessions in the Session Inspector, if Save sessions from agents property in Other Options -> Test Result Storage section is set to Yes (default) because this setting will force replicating minimum necessary data from the agents to the controller.

     

    8.   During test run, a significant amount of performance information collected on agents. The only part of this data, which is most important for consolidated reports, is mirrored to the controller. Some of the data is exclusively stored on the agent. For example, if the session was initiated on the agent and is opened on the controller, its response will display some session metadata, such as host, URL, and response code.  However, detailed response body information will not be presented.  Instead, directions will be provided to access complete request and response content on the agent by Opening an SQL CE file on the agent.

     

     

    The request and response inspectors have the following views:

    • Text View: Shows the request/response headers and body as text.
    • Hex View: Shows the request/response headers and body in hexadecimal format. This is especially helpful when the content of the session is binary.
    • Web View: Shows how the response will look in the browser (only in the response inspector)
    • Image View: Shows the image. This view is only available for image responses.

     

     

     

     

     

     

    • No labels