Enhanced scenario testing of an application under test
First Claim
1. A scenario testing data processing system comprising:
- an action recorder configured to activate each of recording and playback sessions in a content browser;
an application communicatively coupled to said action recorder and said content browser, said application comprising a plurality of controllers, each controller corresponding to one of said sessions; and
, an action engine disposed in each of said controllers, each said action engine comprising program code enabled both to create and execute actions based upon requests received in a recording session for interactions in said content browser, and also to create and execute actions based upon action descriptors in a playback file identified during a playback session in said content browser.
1 Assignment
0 Petitions
Accused Products
Abstract
Embodiments of the present invention address deficiencies of the art in respect to scenario testing of an application under test and provide a method, system and computer program product for enhanced scenario testing. In one embodiment of the invention, a scenario testing data processing system can include an action recorder configured to activate each of recording and playback sessions in an application user interface. The system also can include an application communicatively coupled to the action recorder and the content browser. The application can include one or more controllers, each controller corresponding to one of the sessions. Finally, the system can include an action engine disposed in each of the controllers, each action engine including program code enabled both to create and execute actions based upon requests received in a recording session for interactions in the application user interface, and also to create and execute actions based upon action descriptors in a playback file identified during a playback session in the application user interface.
29 Citations
20 Claims
-
1. A scenario testing data processing system comprising:
-
an action recorder configured to activate each of recording and playback sessions in a content browser;
an application communicatively coupled to said action recorder and said content browser, said application comprising a plurality of controllers, each controller corresponding to one of said sessions; and
,an action engine disposed in each of said controllers, each said action engine comprising program code enabled both to create and execute actions based upon requests received in a recording session for interactions in said content browser, and also to create and execute actions based upon action descriptors in a playback file identified during a playback session in said content browser. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. A scenario testing method for an application under test comprising:
-
identifying actions within a corresponding set of requests received in said application under test and produced from interactions in an interface to the application under test;
performing said actions in the application under test and returning results from said actions to said interface;
recording said actions in a playback file; and
,playing back said actions in said playback file to perform said recorded actions in the application under test. - View Dependent Claims (12, 13, 14, 15)
-
-
16. A computer program product comprising a computer usable medium having computer usable program code for scenario testing an application under test, said computer program product including:
-
computer usable program code for identifying actions within a corresponding set of requests received in said application under test and produced from interactions in an interface to the application under test;
computer usable program code for performing said actions in the application under test and returning results from said actions to said interface;
computer usable program code for recording said actions in a playback file; and
,computer usable program code for playing back said actions in said playback file to perform said recorded actions in the application under test. - View Dependent Claims (17, 18, 19, 20)
-
Specification