Scenario coverage in test generation

• US 10,341,214 B2
• Filed: 03/30/2016
• Issued: 07/02/2019
• Est. Priority Date: 03/30/2016
• Status: Active Grant

• Current Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Original Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Inventors: Lau, Rich J.
• Primary Examiner(s): Park, Jeong S
• Application Number:
  US15/085,789
• Publication Number:
  US 20170289008A1
• Time in Patent Office: 1,189 Days
• CPC Class Codes: G06F 11/3447 Performance evaluation by modeling
• CPC Class Codes: G06F 11/3457 Performance evaluation by simulation
• CPC Class Codes: G06F 2201/865 Monitoring of software
• CPC Class Codes: G06F 2201/87 Monitoring of transactions
• CPC Class Codes: H04L 41/046 comprising network management agents or mobile agents therefor
• CPC Class Codes: H04L 43/14 using software, i.e. software packages network security related monitoring H04L63/1408
• CPC Class Codes: H04L 43/50 Testing arrangements

Abstract

Transaction data is generated during monitoring of a plurality of transactions in a system and a respective flow is determined, from the transaction data, for each of the plurality of transactions. Each of the determined flows involves participation of a respective subset of software components of the system. A plurality of sets of overlapping flows in the plurality of flows are determined and a particular one of the plurality of sets of overlapping flows is determined to correspond to a use scenario of the system. A measure of the degree to which a set of artifacts modeling the system corresponds to the use scenarios of the system is determined.

Claims

1. A method comprising:

accessing, from computer memory, transaction data generated during monitoring of a plurality of transactions involving a plurality of software components in a system;

determining, from the transaction data using at least one data processing apparatus, a respective flow of each of the plurality of transactions, wherein the determined flows of the plurality of transactions comprise a plurality of transaction flows, each transaction flow in the plurality of transaction flows involves participation of a respective subset of the software components in the plurality of software components, and each transaction flow in the plurality of transaction flows comprises a respective plurality of transaction fragments;

determining, using at least one data processing apparatus, one or more overlapping flows between the determined flows, wherein determining an overlapping flow comprises identifying one or more common transaction fragments shared between two or more different transaction flows in the plurality of transaction flows;

detecting, using at least one data processing apparatus, a number of instances of a particular one of the one or more overlapping flows;

determining that the particular overlapping flow corresponds to a particular one of a plurality of use scenarios of the system based on the number of instances of the particular of overlapping flow; and

generating an artifact executable by a computer to simulate operation of a particular software component involved in the particular use scenario based on transaction data describing transactions involved the particular overlapping flow.

2. The method of claim 1, further comprising determining a degree to which an existing set of artifacts modeling the system correspond to the particular use scenarios, wherein the artifact is automatically generated in response to determining that the degree indicates that the existing set of artifact inadequately covers the particular use scenario.

3. The method of claim 2, wherein determining a degree to which a set of artifacts modeling the system correspond to the plurality of use scenarios comprises determining a scenario coverage measure for the system.

4. The method of claim 1, wherein the system comprises a production system and generation of the artifact comprises monitoring a non-production version of the system.

5. The method of claim 4, wherein the transaction data is generated during monitoring of transactions using the production system.

6. The method of claim 5, wherein the transaction data indicates requests and responses in transaction fragments of the plurality of transactions, but excludes contents of the requests and responses.

7. The method of claim 1, wherein the artifact comprises a test case and simulates request generation behavior of the particular software component.

8. The method of claim 7, wherein the test case is configured to generate simulated requests during a test.

9. The method of claim 8, wherein the test case is one of a plurality of test cases, and each test case in the plurality of test cases further includes information describing an expected response to a corresponding request for use in verifying performance of a system under test.

10. The method of claim 1, wherein the artifact comprises a virtual service model to model responses of the particular software component to requests generated by other software components of the system.

11. The method of claim 10, wherein the virtual service model are executable to instantiate a virtual service to generate simulated responses of the particular software component.

12. The method of claim 1, wherein the plurality of use scenarios comprise a set of most frequently observed transaction flows of the system.

13. The method of claim 1, wherein the plurality of software components are hosted on a plurality of different server devices.

14. The method of claim 1, wherein determining the flow of a particular transaction from the transaction data comprises:

determining, from the transaction data, a plurality of fragments of the particular transaction;

determining relationships between the plurality of fragments; and

stitching the plurality of fragments based on the relationships to define the flow of the particular transaction.

15. The method of claim 14, wherein each of the plurality of fragments comprises a respective request and a corresponding response to the request.

16. The method of claim 1, wherein at least a portion of the transaction data comprises data generated by an agent instrumented on a particular one of the software components and used to monitor fragments of transactions involving the particular software component.

17. A non-transitory computer readable medium having program instructions stored therein, wherein the program instructions are executable by a computer system to perform operations comprising:

accessing transaction data generated during monitoring of a plurality of transactions involving a plurality of software components in a system;

determining, from the transaction data, a respective flow of each of the plurality of transactions, wherein the determined flows of the plurality of transactions comprise a plurality of transaction flows, each transaction flow in the plurality of transaction flows involves participation of a respective subset of the software components in the plurality of software components, and each transaction flow in the plurality of transaction flows comprises a respective plurality of transaction fragments;

identifying one or more repeated flows between the determined flows, wherein determining a repeated flow comprises identifying one or more common transaction fragments shared between two or more different transaction flows in the plurality of transaction flows;

detecting a number of instances of a particular one of the one or more repeated flows;

determining that the particular repeated flow corresponds to a particular one of a plurality of use scenarios of the system based on the number of instances of the particular repeated flow; and

generating an artifact executable by a computer to simulate operation of a particular software component involved in the particular use scenario based on transaction data describing transactions involved the particular repeated flow.

18. A system comprising:

a data processing apparatus;

a memory device;

a software transaction analysis engine executable by the data processing apparatus to;

access transaction data generated during monitoring of a plurality of transactions involving a plurality of software components in a system;

determine, from the transaction data, a respective flow of each of the plurality of transactions, wherein the determined flows of the plurality of transactions comprise a plurality of transaction flows, and each of the flows involves participation of a respective set of software components in the plurality of software components;

determine that a subset of the flows comprise recurring instances of a particular transaction flow;

detecting a frequency of the recurring instances of the particular transaction flow;

determine that the particular transaction flow is one of a set of most frequently observed transaction flows in the system based on the frequency of the recurring instances; and

generate a test case to simulate operation of a particular one of the plurality of software components involved in at least a portion of the particular transaction flow based on determining that the set of most frequently observed transaction flows in the system comprises the particular transaction flow.

19. The system of claim 18, further comprising a test system to use the test case to generate simulated requests to a system under test, wherein the simulated requests correspond to requests in the particular transaction flow.

20. The system of claim 18, further comprising a scenario coverage calculator executable to determine a scenario coverage measure based on a percentage of the set of most frequently observed transaction flows for which a test case has been generated.