Scenario coverage in test generation
AssigneeCA, Inc.
InventorRich J. Lau
Life of this patent
Estimating the term…
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.
Claims20
A method 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, and each of the flows involves participation of a respective subset of the software components in the plurality of software components;
- determining a plurality of sets of overlapping flows in the plurality of flows;
- determining that a particular one of the plurality of sets of overlapping flows comprises a particular one of a plurality of use scenarios of the system based on an amount of overlapping flows in the particular set of overlapping flows;
- and
- determining a degree to which a set of artifacts modeling the system correspond to the plurality of use scenarios.
A computer program product comprising a computer readable storage medium comprising computer readable program code embodied therewith, the computer readable program code comprising:
- computer readable program code configured to access transaction data generated during monitoring of a plurality of transactions involving a plurality of software components in a system;
- computer readable program code configured to 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 subset of the software components in the plurality of software components;
- computer readable program code configured to identify a plurality of repeated flows in the plurality of flows;
- computer readable program code configured to determine that a particular one of the plurality of repeated flows comprises a particular one of a plurality of use scenarios of the system based on an amount of instances of the particular repeated flow;
- and
- computer readable program code configured to determine a measure of scenario coverage provided by a set of artifacts modeling the system.
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;
- determine that a set of most frequently observed transaction flows in the system comprises the particular transaction flow;
- and
- initiate generation of a test case to model 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.
Dependencies are inferred from the claim text.