Browse Prior Art Database

System and method for multi-user web application load and performance testing Disclosure Number: IPCOM000179959D
Original Publication Date: 2009-Mar-03
Included in the Prior Art Database: 2009-Mar-03
Document File: 3 page(s) / 106K

Publishing Venue



A process is disclosed for recording and generating realistic load to multi-user web applications by inspecting and analyzing actual server-side traffic on a production system. An algorithm automatically correlates traffic into per-user workflows that can be replayed to generate consistent and realistic application usage. This process enables software testers to perform better performance and system testing of web applications.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 77% of the total text.

Page 1 of 3

System and method for multi-user web application load and performance testing

Existing HTTP load generation tools require the tester to manual create individual scenarios that represent a user performing certain requests to the web application. These scenarios can be replicated and played back to generate load to the server. This process has the disadvantage that the scenarios generated by the tester are limited and do not necessarily reflect actual usage of the system in a production environment.

The disclosed process utilizes a packet capture filter installed on the web application server to monitor all traffic to the web application. The process can simultaneously record multiple scenario scripts, creating a separate one for each client currently using the web application.The filter monitors the source of each HTTP request to determine which client made the request, and appends the request to that client's scenario. A scenario may be defined by a set of start and finish actions, so that only relevant requests and full user sessions are recorded. In the case of a web application using a login form, the start action may be the login url and the end action will be the logout url. Using this scheme, a scenario will be created for each user that logs in, and will contain all actions performed by that user until they log out.

The filter can be con...