Ca, Inc.

Interactive Tko, Inc.

John Joseph Michelsen

Christopher C Kraus

Jean-David Dahan

James Stephen Kress

Cameron David Bromley

Daniel H Acheff

Steven D LaRocca

The systems and methods described herein can be used to provide virtual service environments. In one embodiment, a virtual service model is generated by detecting one or more transactions, each of which includes a request sent from a requester to a software service and a response sent from the software service to the requester; storing information describing the detected transactions in a virtual service model, where the information describing each transaction includes information identifying a command included in the request and information identifying a response attribute included in the response; and generating information describing an unknown transaction, where the information describing the unknown transaction includes information identifying a first command and information identifying a first response attribute. The first command and the first response attribute are copies of a corresponding command and a corresponding response attribute associated with a corresponding one of the detected transactions.

Service modeling and virtualization

A first set of information is identified, collected by a first agent during monitoring of a first software component. A second set of information is identified, that was collected by a second agent during monitoring of a second software component. It can be determined that the first and second sets of information each include characteristics of a particular transaction involving the first and second software components. A model is generated of the particular transaction based at least in part on the first and second sets of information. The model includes a representation of the involvement of the first and second software components within the particular transaction. In some aspects, characteristics included in the first and second set of information can include timing information for use, for example, in generating a model representing ordering of software components' involvement in one or more transactions.

Modeling and testing of interactions between components of a software system

Various techniques for interacting with a test case via a graphical model are disclosed. For example, one method involves displaying a first icon, which represents a first testing activity within a test case; displaying a second icon, which represents a second testing activity within the test case; and displaying a connector, which couples the first icon and the second icon. An assertion (e.g., against test results obtained by performing the first testing activity) is associated with the connector.

Graphical transaction model

Composite virtual service models can be defined to model various business transactions. A request of a particular component in a first transaction is identified and a composite virtual service model can be identified that corresponds to the particular component. The composite virtual service model models a plurality of transactions comprising the first transaction between the particular component and a first component and a second transaction between the particular component and a second component. The composite virtual service model defines a correlation between the first transaction and the second transaction. A first synthetic response is generated from the composite virtual service model based at least in part on the request, the first synthetic response simulating a response of the first component. A second synthetic response is generated from the composite virtual service model based at least in part on the correlation to simulate a response of the second component.

Composite virtual services

Various systems and methods for are disclosed. For example, a method can involve extracting information from a response. The response is generated in response to a request generated by a test module during execution of a test case. The extracted information describes characteristics of transactions within the test case. The method can then involve generating a display, based upon the extracted information. The display includes information identifying each of the components that participated in at least one of the transactions within the test case. Such a method can be performed by a computing device implementing the test module.

Modeling and testing interactions between components of a software system

Data is identified that represents a path of a transaction that includes a plurality of transaction fragments associated with a plurality of software components. The transaction returns a particular value and a particular one of the plurality of software components is identified as a source of the particular value. A test action is generated that, when executed, is to attempt to verify the particular value from the particular software component.

Automated software system validity testing

One or more test controls within code under test are enabled and then executing the code under test is executed. When enabled, the test control will interact with a tester when the code under test is executed (e.g., by providing data to the tester). The selection to enable the test control can be made based on whether the system accessing the code under test is a tester. If the system is a tester, the test control is enabled. Otherwise, the test control is disabled. The test control can include an execution control, a data definition control, and/or a log control.

Instrumentation system and method for testing software

Data is identified that represents a path of a transaction that includes a plurality of transaction fragments associated with a plurality of software components. The plurality of software components includes a first software component to communicate in the transaction with a second software component over an interface. A transaction boundary is determined between the first and second software components based at least in part on the data. A virtual model is generated to simulate at least a particular one of the plurality of software components based on the identified transaction boundary.

Transactional boundaries for virtual model generation

Various systems and methods are disclosed for automatically generating a spreadsheet template to store information usable to generate one or more data transfer objects for input to a system under test. One such method involves identifying one or more properties of a data transfer object to be input to a software system under test. Identifying the properties of the data transfer object involves inspecting one or more structural requirements of a module within the software system under test that consumes that data transfer object. The method then automatically generates a spreadsheet template corresponding to the data transfer object, such that the spreadsheet template includes a respective column for each of the properties of the data transfer object. The spreadsheet template is configured to store information representing one or more versions of the data transfer object.

Spreadsheet data transfer objects

Graphical model for test case viewing, editing, and reporting

Request data is identified that describes a request of a second program by a first program intercepted by a first exit in the first program. Response data is identified that describes a response by the second program to the request as intercepted by a second exit in the first program. A virtual service configured to model operation of the second program is instantiated based on the request data and response data. In another aspect, a request by the first program to the second program is intercepted by the first exit and the request is redirected to the virtual service. A response is received as generated by the virtual service and the response is returned to the first program using the second exit.

Mainframe virtualization

Systems, methods, apparatus and software can provide object interaction tools and techniques that allow a user to interact with a software object using familiar user interface elements. Information about the target object is provided so that an instance can be constructed. The object is introspect so available data and methods information can be used to populate a corresponding object interaction description and present an object interaction session.

Growing community of inventors

Irving, TX, United States of America

John Joseph Michelsen