Browse Prior Art Database

A system and method to apply system testing based on real time production activity

IP.com Disclosure Number: IPCOM000247146D
Publication Date: 2016-Aug-10
Document File: 5 page(s) / 88K

Publishing Venue

The IP.com Prior Art Database

Abstract

Software testing and specifically system testing and performance testing are a common practice; typically a test harness will attempt to simulate some of the normal actions of real users playing back recordings repeatedly against a test system, These load tests are synthetic and typically do not give a good representation of the pattern of real use of a system. When changes to a system are rolled into a production system it is often found that the system behaves in unexpected ways that were not apparent during the system test.

This article introduces a new system & method that monitors the real world actions of an abundance of users in real time and maps those actions to a distributed set of proxy users that apply the actions to a test system. Effectively allowing for a test that shows how the system being tested behaves in the real world scenario prior to it being deployed into production.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 32% of the total text.

Page 01 of 5

A system and method to apply system testing based on real time production activity

Software testing and specifically system testing and performance testing are a common practice; typically a test harness will attempt to simulate some of the normal actions of real users playing back recordings repeatedly against a test system, These load tests are synthetic and typically do not give a good representation of the pattern of real use of a system. When changes to a system are rolled into a production system it is often found that the system behaves in unexpected ways that were not apparent during the system test.

    This article introduces a new system & method that monitors the real world actions of an abundance of users in real time and maps those actions to a distributed set of proxy users that apply the actions to a test system. Effectively allowing for a test that shows how the system being tested behaves in the real world scenario prior to it being deployed into production.

    User activity is monitored by examining the request flow going into the production system, each request as it enters the production system is copied and sent to a test manager; this has minimal impact on the production system as the request is pushed out and a response is not expected.

    The test manager makes any required changes to the request and then distributes it to one of the acting "proxy user"; an actor or proxy user is an instance of a process running on a volunteer PC or on a pool of designated test machines. The actor then applies the requested action to the test system. There will be one actor active in the test system for each real user in the production system. The test manager is responsible for session tracking to make sure that requests are distributed correctly to the actors.

    By monitoring production and distributing the requests to actors and those actors loading the test system, the test system is subjected to a real world load and usage scenario;


Page 02 of 5

    The production system acts in the normal way with users interacting via the request response mechanism; for example using the HTTP protocol via a web browser, this is business as usual!

    Requests are copied and pushed to the test manager, there are no other changes to the production system to support this.

    The test manager determines the user that initiated the request and checks the session manager to see if this is an already active user or a new one. In the case this is a new user the test manager creates an instance of a session and designates an actor "proxy user" to that session. A proxy user instance is allocated from one of the volunteer or designated test machines and a session created on that machine to represent the test user.

In the case where the request if from a user that is already established in the session manager the existing session is used.

    The test manager passes the request and the details of the session to the request mapper. The request mapper changes the request...