AUTOMATED HTTP USER FLOWS SIMULATOR

• US 20180004640A1
• Filed: 06/29/2017
• Published: 01/04/2018
• Est. Priority Date: 06/29/2016
• Status: Active Grant

• Current Assignee: Software Integrity Group Incorporated
• Original Assignee: Synopsys Incorporated
• Inventors: SHAVRO, Tamir, TAMIR, Eran, BLOCHET, Lilian
• Granted Patent: US 10,282,282 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: G06F 11/3672 Test management
• CPC Class Codes: G06F 11/3692 for test results analysis
• CPC Class Codes: G06F 16/95 Retrieval from the web
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: G06F 16/986 Document structures and storage, e.g. HTML extensions

Abstract

A testing method and system for automatic Hypertext Transfer Protocol (HTTP) testing, the system including a memory configured to store sequences of user requests, a program store storing code for emulating a sequence of user requests, and at least one processor coupled to the program store and to the memory for executing the stored code, the code including instructions for generating an emulated request based on a request from a user sequence of requests, transmitting the emulated request to an application, receiving a response to the emulated request from the application, calculating an adapted emulated sequence based on validity of the received response, and instructing transmission of the adapted emulated sequence.

Claims

1. A testing system for automatic Hypertext Transfer Protocol (HTTP) testing, comprising:

a memory configured to store a sequence of user requests;

a program store storing code for emulating the sequence of user requests; and

at least one processor coupled to the program store and to the memory for executing the stored code, the code comprising instructions for;

generating an emulated request based on a request from the sequence of user requests stored in the memory,

transmitting the emulated request to an application coupled to the test system,

receiving a response to the emulated request from the application,

calculating an adapted emulated request sequence based on whether the received response is valid, and

instructing transmission of the adapted emulated request sequence to the application.

2. The testing system of claim 1, wherein the code further comprises instructions for:

comparing the received response to a corresponding pre-recorded response and determining a similarity measure between the received response and the corresponding pre-recorded response; and

deciding based on the similarity measure whether the received response is valid.

3. The testing system of claim 1, wherein the application is in an application server and wherein the code further comprises instructions for sending the adapted emulated request sequence to the application server.

4. The testing system of claim 1, wherein the code further comprises instructions for detecting a dependency between a particular request in the sequence of user requests and a previous request response, and adapting a dependent emulated request corresponding to the particular request by inserting into the dependent emulated request information from the previous request response.

5. The testing system of claim 1, wherein the code further comprises instructions for:

identifying in the user sequence at least one previous response to the emulated request that produce at least one dynamic data item required for the emulated request;

executing the previous request and extracting the at least one dynamic data item from the previous response to the at least one previous request that produces the required at least one dynamic data item; and

inserting the at least one dynamic data item into the emulated request.

6. The testing system of claim 5, wherein the code further comprises instructions for inserting the at least one dynamic data item into the emulated request instead of information copied from a corresponding pre-recorded request.

7. The testing system of claim 1, wherein the system further comprises a token instances repository, and wherein the code further comprises instructions for:

monitoring responses received from an application server in response to the emulated requests;

detecting a token value in a monitored response;

storing the token value in the token instances repository; and

adapting an emulated request by inserting the token value into the emulated request instead of a recorded token value.

8. The testing system of claim 1, wherein the code further comprises instructions for executing a client side code in order to generate a token value and adapting an emulated request by inserting the generated token value into the emulated request instead of a recorded token value.

9. The testing system of claim 1, wherein the code further comprises instructions for producing testing agents and planting the testing agents in the application server.

10. The testing system of claim 9, wherein the testing agents are configured to:

monitor activity items in the tested application;

associate activity items with an accessed application page and store the activity items in correlation with the accessed application page and corresponding user requests; and

identify, based on the association, dependent application pages.

11. The testing system of claim 1, wherein the code further comprises instructions for:

determining a target outcome;

identifying dependent user requests in the emulated request; and

producing a reduced emulated sequence by;

excluding at least one independent request from the emulated request;

executing the emulated sequence without the at least one excluded request and determining the validity of the response, by comparing the response to the target outcome; and

removing the at least one independent request from the emulated sequence when the response is valid.

12. A method for automatic HTTP testing, the method comprising:

generating, by a processor, an emulated sequence of user requests, an emulated request based on a request from a user sequence stored in a memory;

transmitting the emulated request to an application server;

receiving a response to the emulated request from the application server;

calculating, an adapted emulated request sequence based on whether the received response is valid; and

instructing transmission of the adapted emulated request sequence to the application server.

13. The method of claim 12, further comprising:

comparing the received response to a corresponding pre-recorded response;

determining a similarity measure between the received response and the corresponding pre-recorded response; and

deciding based on the similarity measure whether the received response is valid.

14. The method of claim 12, further comprising:

detecting a dependency between a particular request in the sequence of user requests and a previous request response; and

adapting a dependent emulated request corresponding to the particular request by inserting into the dependent emulated request information from the previous request response.

15. The method of claim 12, further comprising:

identifying in the user sequence at least one previous response to the emulated request that produced a dynamic data item;

executing the previous request and extracting the dynamic data item from the previous response to the at least one previous request; and

inserting the dynamic data item into the emulated request.

16. The method of claim 15, further comprising:

inserting the dynamic data item into the emulated request instead of information copied from a corresponding pre-recorded request.

17. The method of claim 12, further comprising:

monitoring responses received from an application server in response to the emulated requests;

detecting a token value in a monitored response;

storing the token value in a token instances repository; and

adapting the emulated request by inserting the token value into the emulated request instead of a recorded token value.

18. The method of claim 12, further comprising:

executing a client side code to generate a token value and adapting the emulated request by inserting the generated token value into the emulated request instead of a recorded token value.

19. The method of claim 12, further comprising:

producing testing agents and planting the testing agents in the application server, wherein the testing agents are configured to;

monitor activity items in the tested application;

associate the activity items with an accessed application page and store the activity items in correlation with the accessed application page and corresponding user requests; and

identify, based on the association, dependent application pages.

20. The method of claim 12, further comprising:

determining a target outcome;

identifying dependent user requests in the emulated sequence; and

producing a reduced emulated sequence by excluding at least one independent request from the emulated sequence and executing the emulated sequence without the at least one excluded request to produce a reduced response;

determining a validity of the reduced response by comparing the reduced response to the target outcome; and

removing the at least one independent request from the emulated sequence when the response is valid.

21. A testing server comprising:

a memory configured to store a sequence of user requests;

a processor to implement a testing engine configured to generate an emulated request based on a request from the sequence of user requests stored in the memory, transmit the emulated request to an application server coupled to the test system, receive a response to the emulated request from the application server, calculate an adapted emulated request sequence based on whether the received response is valid, and to transmit the adapted emulated request sequence to the application server;

the testing engine further configured to detect dependencies between requests in the sequence of user requests and adapt the emulated request dependent on at least one previous request of the sequence of user requests by inserting into the emulated dependent request information from a response to the at least one previous request that the emulated request depends on.