- Web Performance Testing Scenario

Web Performance Testing Scenario

Web Performance Testing Scenario on the fly

• NeoLoad creates automatically your Web Performance Testing Scenario by recording your actions using a simple web browser.

Browse a user-friendly web-based GUI

• NeoLoad groups HTTP requests (HTML, images, CSS, etc.) into web pages to facilitate simulation (frames are treated as pages within a page).

Include dynamic data to create multiple situations

• NeoLoads can replace dynamic test data with character strings, counters, dates, etc. Those can be generated automatically or extracted from a file.
• For example, NeoLoad variables can be used to generate login/password pairs for each virtual user played during the web performance test.

Test your scenario before you launch the test

• Check your Web Performance Testing Scenario, and identify any potential issue before you run the actual web performance test.

Customize test response criteria

• Predefine your own standard of criteria by which you will evaluate your web application responses – content, content size, response time, etc.

Simulate bandwidths depending on users

• NeoLoad can emulate server access over different bandwidths, which affect server load in different ways
• For instance, 56k modems add an overhead on Input/Output buffering and thread pools, while LAN users have a greater impact on the server's CPU.

Define flexible load based on users' activities

• Create user populations with multiple user profiles grouped by type of activity and server load.
• For example, you can simulate 80% of users reading news, 20% purchasing goods online, and 40% of the total using a modem connection.

Define test timeline

• Set the web performance test duration according to time or number of virtual user iterations.

Setup advanced load variation policy

• Increase server load progressively to pinpoint your web application’s limits and flaws.
• The peak load feature can increase the load even further for defined periods.

Native HTTP redirect management

• HTTP redirects and dynamic parameters in URLs are recorded automatically and played back dynamically.

Dynamic links

• NeoLoad can extract a GET or POST link from a response and use it in the following request
• This feature is essential when web applications include dynamic values for GET and POST requests.

Variable extractor

• NeoLoad extracts content from a server response and assigns it to a variable; this value can then be used as a request or assertion parameter elsewhere in your Web Performance Testing Scenario.

Test all objects and controls : Java, Flash, Flex or ActiveX

• NeoLoad records and replays all HTTP activity between your browser and the web server, simulating client-side components such as Java Applets, Macromedia Flash/Flex and ActiveX controls.

Evaluate compressed server response (gzip, deflate)

• With NeoLoad you can test servers using gzip or deflate compression, by uncompressing the server response before validation and/or extraction.

Switch instantly between servers

• Switch between test servers in real time.
• Use the same scenario to test both development and pre-production servers.
• This feature can also be used to compare different servers hosting the same application.

Logical Actions

Dynamic test cases

• After recording the scenario, NeoLoad allows you to add logical actions to your Virtual Users definitions to be able to handle very dynamic test cases.

Manage virtual user's logical actions

Delay : wait for a set of time interval. Loop : loop over actions. While : conditional loop over actions. If...Then...Else : conditional actions. Variable Modifier : change variable value. Container : group actions to extract statistics. Random Container : randomly play actions. Try...Catch : handle errors. Stop virtual user : stop virtual user execution. Fork : play actions in a different execution thread. JavaScript : execute a custom script.