Record. Don’t script.
WPLoadTester records HTTP traffic from real browser sessions and replays it at scale. No scripting language. No XPath selectors. No manual correlation code. You drive the application like a user; the recorder captures the underlying HTTP, and that is the test case.
What "recording" actually means.
WPLoadTester sits between your browser and the application as an HTTP proxy. You click through the scenario you want to load-test in any browser. Every request the browser makes (and every response the server returns) is captured. When you stop, what you have is a complete, replayable HTTP test case.
The captured test case is the protocol traffic, not a script that describes the protocol traffic. There is no transcription step where someone has to translate browser actions into Java method calls or JavaScript closures. The recording is the test case.
Real-browser support: any browser that respects the system HTTPS proxy works (Chrome, Safari, Firefox, Edge). WebDriver / Selenium scripts are also supported for scenarios that need scripted browser automation, but the more common pattern is one human, one browser session, one recording.
What about dynamic values?
The legitimate concern with raw recording is replay correctness. Modern web apps fill every request with session tokens, CSRF nonces, OAuth2 Bearer tokens, and per-session correlated values. A naive replay of recorded traffic fails the moment any of those expires or rotates.
That is what Automatic State Management (ASM) handles. ASM scans the recorded session up-front and configures the well-known dynamic-value patterns automatically. The AI Assistant catches the long tail by watching replays for runtime errors, identifying the failure pattern, and generating a new detection rule on the spot. From a real engagement: an OAuth login flow that previously took 2 hours of manual correlation typically configures in around 4 minutes with the AI Assistant.
Configuration Wizards for the common shapes.
Some test patterns need more than a recording. The User Identity Wizard is the canonical example: a single recorded login becomes a parameterized test that exercises thousands of distinct usernames and passwords. You hand the wizard a CSV (or a database query) and it does the substitution everywhere those credentials appear in the recorded traffic.
Similar wizards exist for parameterizing form data, randomizing per-VU values, configuring file uploads, and shaping per-tier think time. For genuinely unusual patterns that no wizard ships for, custom detection rules use plain .properties configuration files. No code changes, no recompile, no restart.
Record your first test in under five minutes.
The recorder and ASM ship with every edition of WPLoadTester 7, including the free single-machine edition. Download to evaluate locally, or request the 7.0 beta to run cloud-scale tests against your application.
Comparing tiers? See the Free vs Pro split.