Skip to content

Recording Test Cases

A recording is the raw material for everything Load Tester does. You browse your application in Chrome, the extension captures every HTTP request and response, and the result is a test case you can inspect, configure, replay, and eventually load-test against. In v7.0 the capture mechanism is a Chrome extension that uses the debugger API, not a proxy, which means no SSL warnings, no certificate juggling, and localhost recording works out of the box.

The goal of this section is to get you from "I have a workflow I want to load test" to "I have a clean recording of that workflow" without spending an hour fighting browser configuration.

In This Section

  • Your First Recording: Step-by-step walkthrough from clicking Record to inspecting the captured test case. Covers the Recording Control dialog, Force Page Break for single-page apps, and what to do (and not do) while a recording is active.
  • Browser Configuration: One-time Chrome extension installation, picking the right browser, multiple-profile setups, and dealing with corporate developer-mode restrictions.
  • Recording Settings: Domain blocking and page grouping algorithms. The defaults work for most sites. This page is here for when they don't.
  • Inspecting a Recording: How to verify the recording captured what you expected before you spend an hour configuring it.

If this is your first recording, start with Browser Configuration to install the extension, then Your First Recording. After that, Inspecting a Recording tells you whether the result is worth configuring or whether you should re-record.