# US 2013/0159784 A1 · Systems and methods for recording user interactions within a target application > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2013/0159784 A1 - Document ID: US20130159784A1 - Status: Published application - Kind: A1 - Application number: 13/328,799 - Filed: 2011-12-16 - Published: 2013-06-20 - Earliest claimed: 2011-12-16 - Assignees: Sap SE - Inventors: Claude Rossi - Web page: https://patentgrep.com/patent/US20130159784A1 ## CPC - G06F 11/263: Generation of test inputs, e.g. test vectors, patterns or sequences {; with adaptation of the tested hardware for testability with external testers} - G06F 11/3684: {for test design, e.g. generating new test cases} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A method includes executing instructions recorded on a non-transitory computer-readable storage media using at least one processor. The method includes receiving a notification of a selection of an user interface (UI) element within a UI of a target application, generating a request for an element listener instance, notifying multiple test recorder hooks of the request for the element listener instance, where each of the test recorder hooks is associated with a specific UI format having multiple different element listeners depending on a type of selected UI element, creating the element listener instance by one of the test recorder hooks based on the UI format and the selected UI element, registering, by the element listener instance, for events associated with the UI element and recording the events. ## Claims ### Claim 1 A method including executing instructions recorded on a non-transitory computer-readable storage media using at least one processor, the method comprising: receiving a notification of a selection of an user interface (UI) element within a UI of a target application; generating a request for an element listener instance; notifying multiple test recorder hooks of the request for the element listener instance, wherein each of the test recorder hooks is associated with a specific UI format having multiple different element listeners depending on a type of selected UI element; creating the element listener instance by one of the test recorder hooks based on the UI format and the selected UI element; registering, by the element listener instance, for events associated with the UI element; and recording the events. ### Claim 2 (depends on 1) The method as in claim 1 wherein notifying the multiple test recorder hooks comprises iterating the request for the element listener instance through a list of registered test recorder hooks until one of the registered test recorder hooks returns the element listener instance. ### Claim 3 (depends on 1) The method as in claim 1 wherein creating the element listener instance comprises: collecting information from a current UI context, and using the current UI context to determine the element listener instance. ### Claim 4 (depends on 1) The method as in claim 1 wherein registering the events associated with the UI element comprises collecting information specific to the UI element to enable future playback of actions performed against the UI element in a generated test scenario. ### Claim 5 (depends on 4) The method as in claim 4 further comprising: capturing semantics of the UI element within the UI of the target application; and generating one or more tests having test components using the semantics. ### Claim 6 (depends on 4) The method as in claim 4 further comprising: encapsulating the collected information and creating an instance of the encapsulated collected information; and adding the instance of the encapsulated collected information to a repository to enable generation of the test scenario using the instance of the encapsulated collected information. ### Claim 7 (depends on 1) The method as in claim 1 further comprising highlighting the UI element for which the element listener instance was created. ### Claim 8 A non-transitory computer-readable storage medium storing instructions that when executed cause a processor to perform a process, the instructions comprising instructions to: receive a notification of a selection of an user interface (UI) element within a UI of a target application; generate a request for an element listener instance; notify multiple test recorder hooks of the request for the element listener instance, wherein each of the test recorder hooks is associated with a specific UI format having multiple different element listeners depending on a type of selected UI element; create the element listener instance by one of the test recorder hooks based on the UI format and the selected UI element; register, by the element listener instance, for events associated with the UI element; and record the events. ### Claim 9 (depends on 8) The non-transitory computer-readable storage medium of claim 8 wherein the instructions to notify the multiple test recorder hooks comprise instructions to iterate the request for the element listener instance through a list of registered test recorder hooks until one of the registered test recorder hooks returns the element listener instance. ### Claim 10 (depends on 8) The non-transitory computer-readable storage medium of claim 8 wherein the instructions to create the element listener instance comprise instructions to: collect information from a current UI context, and use the current UI context to determine the element listener instance. ### Claim 11 (depends on 8) The non-transitory computer-readable storage medium of claim 8 wherein the instructions to register the events associated with the UI element comprise instructions to collect information specific to the UI element to enable future playback of actions performed against the UI element in a generated test scenario. ### Claim 12 (depends on 11) The non-transitory computer-readable storage medium of claim 11 further comprising instructions to: capture semantics of the UI element within the UI of the target application; and generate one or more tests having test components using the semantics. ### Claim 13 (depends on 11) The non-transitory computer-readable storage medium of claim 11 further comprising instructions to: encapsulate the collected information and creating an instance of the encapsulated collected information; and add the instance of the encapsulated collected information to a repository to enable generation of the test scenario using the instance of the encapsulated collected information. ### Claim 14 (depends on 8) The non-transitory computer-readable storage medium of claim 8 further comprising instructions to highlight the UI element for which the element listener instance was created. ### Claim 15 A computer system including instructions stored on a non-transitory computer-readable storage medium, the computer system comprising: a recorder interface configured to: receive a notification of a selection of an user interface (UI) element within a UI of a target application, generate a request for an element listener instance, and notify multiple test recorder hooks of the request for the element listener instance; multiple test recorder hooks, wherein each of the test recorder hooks is associated with a specific UI format having multiple different element listeners depending on a type of selected UI element and is configured to create the element listener instance based on the UI format and the selected UI element; and the element listener instance configured to register for events associated with the UI element and to record the events. ### Claim 16 (depends on 15) The computer system of claim 15 wherein the recorder interface is configured to iterate the request for the element listener instance through a list of registered test recorder hooks until one of the registered test recorder hooks returns the element listener instance. ### Claim 17 (depends on 15) The computer system of claim 15 wherein the test recorder hook is configured to: collect information from a current UI context, and use the current UI context to determine the element listener instance. ### Claim 18 (depends on 15) The computer system of claim 15 wherein the element listener instance is configured to collect information specific to the UI element to enable future playback of actions performed against the UI element in a generated test scenario. ### Claim 19 (depends on 18) The computer system of claim 18 wherein the element listener instance is configured to capture semantics of the UI element with the UI of the target application and generate one or more tests having test components using the semantics. ### Claim 20 (depends on 18) The computer system of claim 18 further comprising an entry interface configured to: encapsulate the collected information and create an instance of the encapsulated collected information; and add the instance of the encapsulated collected information to a repository to enable generation of the test scenario using the instance of the encapsulated collected information.