Capture real user traffic
and transform the way you test

General performance-testing tools typically define the user flow to test and then write scripts to execute it. The biggest difference with LoadTester is that it captures real production traffic and uses it as the basis for test scenarios. It obtains API call flows from real traffic and, after personal-data masking and handling of dynamic values such as sessions and tokens, replays them in a test environment. This focuses on reducing the work of analyzing business flows and writing scripts from scratch every time you test.

LoadTester takes a ZERO SCRIPT approach that uses real production traffic to reduce the manual work of coding scenarios. It captures the API traffic needed from the production environment, saves it as a test asset, and uses it to replay load up to your target TPS or concurrent-user count. This reduces the burden of coding test scenarios from scratch. However, ZERO SCRIPT does not mean that no setup work is required at all. Depending on the test purpose and environment, tasks such as selecting the target traffic, personal-data masking, dynamic-data mapping, and setting the target load may still be needed.

Yes. LoadTester provides a dynamic variable mapping (Correlation) feature that, during replay, extracts sessions or authentication tokens newly generated on each run—such as during login—and automatically links them to subsequent API requests. For example, it can extract a newly issued authentication token from a login API response and inject that value into the Header of a payment or lookup API to reproduce a continuous API flow similar to real user requests. This lets you run performance tests based on real business flows that connect multiple APIs, rather than simply calling individual APIs repeatedly.

LoadTester can identify sensitive information such as names, account numbers, and phone numbers during the capture of production traffic and de-identify it by masking or randomization. Also, rather than passing captured traffic directly to an external test environment, it selects the necessary traffic, refines sensitive information and dynamic data, and then stores and replays it as test data. The materials note that a lightweight Capture Agent is designed to keep the production server's CPU usage below 5%, and they also present a structure that performs capture, masking, and storage in an on-premises environment.