1,000,000 Concurrent Virtual Users

Load Tester PRO™ was designed from the ground up to generate massive amounts of load accurately and efficiently. At the base is a completely rewritten byte-level I/O library optimized for load testing. On top of that is a massively scalable application architecture combined with a highly optimized user interface. Load generation is from a network of internal or external load balanced computers that continually monitor the accuracy of the simulated users.

No Coding Test Cases

Load Tester PRO™ automatically detects and configures the test cases for most situations. No muss. No fuss. The automated record and configuration process means no complicated hand-coding, and no scripting languages to learn. And no reverse-engineering and hand-programming code for complicated dynamic and state variables. All of which leaves you with more time to write new code.

Works with Your Technology

Load Tester PRO™ works with your technology on most platforms including:

• AJAX
• Mobile Devices
• Apache and httpd
• PHP
• Java and J2EE
• ASP and .NET
• Virtualized Servers

Generate Load from The Cloud

At the push of a button you can generate load from outside your network to test the entire application stack, including the firewall, or generate load from inside your test lab to concentrate on server performance by itself.

Click to Configure

Configuring user input such as login credentials, search terms, and other user-entered fields is as easy as clicking on the field; no coding required.

For most fields, simply bring up the page in the Content View and then click the field - the Field Editor dialog will appear. You are just a few clicks away from filling the field with the values needed to customize the scenario.

Automatic Error Detection

A test is only valid if it works correctly, which is why Load Tester™ automatically configures sophisticated logic to detect application and logic errors. When an error does happen, not only is the page captured, but you get a visual comparison showing not only the rendered page, but the HTML that triggered the error.