Abstract: A method of recording user-driven events within a computing system includes receiving at a motion-sensitive display surface at least one user-performed gesture, which includes user movement of an object over the surface that recognizes such user interaction therewith. Touch information is generated corresponding to the at least one user-performed gesture. The touch information is configured to be provided to an application. The touch information is intercepted and recorded before it is provided to the application. The intercepted touch information is grouped into at least one chunk, and the at least one chunk is output to the application.

Abstract: Systems and methods for sending in-product notifications to individual users of a software product or a specifically identified subset of users of the software product selected via their previously observed interactions with the software product. In addition, targeted notifications of bug fixes can be sent to specific users who have encountered an error condition or performance issue that a particular bug fix is designed to correct.

Abstract: Systems and methods for sending in-product notifications to individual users of a software product or a specifically identified subset of users of the software product selected via their previously observed interactions with the software product. In addition, targeted notifications of bug fixes can be sent to specific users who have encountered an error condition or performance issue that a particular bug fix is designed to correct.

Abstract: A method of recording user-driven events within a computing system includes receiving an indication that a user interacted with a first graphical user interface (GUI) user interactive control. The method includes automatically searching at least one vicinity near the first GUI user interactive control for descriptive information associated with the first GUI user interactive control, and automatically recording a user-driven event that represents the user interaction with the first GUI user interactive control and includes the descriptive information.

Abstract: Merging user interface (UI) object trees comprising UI trees from different technologies (e.g., host and one or more guest technologies) can involve registering guest technologies with a technology adapter layer, for example, used to manage UI tree merging. Further, identifying whether a UI object can be switched from a first technology to a second technology can comprise using a host technology provider to identify if a UI object can be switched, when navigating down the UI tree. When navigating up the UI tree, information stored by the technology adapter layer can be used to identify if a UI object can be switched. Additionally, identifying the second technology can comprise having the technology adapter layer request technology switching capability information from registered technologies for the UI object when navigating down the UI tree. When navigating up the UI tree, information stored by the technology adapter layer can be used to identify the second technology.

Abstract: A method includes detecting user interaction with a first control of a user interface, identifying a property of the first control, and storing data representing the property of the first control in a memory. The method further includes dynamically generating an event for the first control by use of the property of the first control upon detecting user interaction with a second control and upon detecting an absence of an event corresponding to the first control being generated with respect to a user interface test program. An action responsive to the dynamically generated event is stored in an event log.

Abstract: A method includes detecting user interaction with a first control of a user interface, identifying a property of the first control, and storing data representing the property of the first control in a memory. The method further includes dynamically generating an event for the first control by use of the property of the first control upon detecting user interaction with a second control and upon detecting an absence of an event corresponding to the first control being generated with respect to a user interface test program. An action responsive to the dynamically generated event is stored in an event log.

Abstract: Automation of actions on a server system (e.g., web server, FTP server) is facilitated by a server system that is ready for actions to be performed upon it. Because there are scenarios when a server system is not in a state to be acted upon (e.g., web page changed due to navigation, script execution, asynchronous request through dynamic web extensions), an automated action needs to be synchronized to when then server system is in a ready state for that action to occur. A wait-for-ready state can be initiated that detects when a server system is ready for a next action.

Abstract: A method of recording user-driven events within a computing system includes receiving an indication that a user interacted with a first graphical user interface (GUI) user interactive control. The method includes automatically searching at least one vicinity near the first GUI user interactive control for descriptive information associated with the first GUI user interactive control, and automatically recording a user-driven event that represents the user interaction with the first GUI user interactive control and includes the descriptive information.

Abstract: A method of recording user-driven events within a computing system includes receiving at a motion-sensitive display surface at least one user-performed gesture, which includes user movement of an object over the surface that recognizes such user interaction therewith. Touch information is generated corresponding to the at least one user-performed gesture. The touch information is configured to be provided to an application. The touch information is intercepted and recorded before it is provided to the application. The intercepted touch information is grouped into at least one chunk, and the at least one chunk is output to the application.

Abstract: Recording of functional steps resulting from actions in an application is desirable for performing functional testing or user interface automation of an application. However, certain events that may result from actions occurring in an application are often difficult to record, which may lead to playback failure. Further, a user's intent when performing an action is difficult to determine. In order to obtain effective playback, a reliable and efficient recording of an application's functional steps needs to occur. Injecting wrapper functions into an application and monitoring an event generator's state before and after an action has occurred may yield more reliable and effective results.

Abstract: Automation of actions on a server system (e.g., web server, FTP server) is facilitated by a server system that is ready for actions to be performed upon it. Because there are scenarios when a server system is not in a state to be acted upon (e.g., web page changed due to navigation, script execution, asynchronous request through dynamic web extensions), an automated action needs to be synchronized to when then server system is in a ready state for that action to occur. A wait-for-ready state can be initiated that detects when a server system is ready for a next action.

Abstract: Automation of actions on a server system (e.g., web server, FTP server) is facilitated by a server system that is ready for actions to be performed upon it. Because there are scenarios when a server system is not in a state to be acted upon (e.g., web page changed due to navigation, script execution, asynchronous request through dynamic web extensions), an automated action needs to be synchronized to when then server system is in a ready state for that action to occur. A wait-for-ready state can be initiated that detects when a server system is ready for a next action.

Abstract: Merging user interface (UI) object trees comprising UI trees from different technologies (e.g., host and one or more guest technologies) can involve registering guest technologies with a technology adapter layer, for example, used to manage UI tree merging. Further, identifying whether a UI object can be switched from a first technology to a second technology can comprise using a host technology provider to identify if a UI object can be switched, when navigating down the UI tree. When navigating up the UI tree, information stored by the technology adapter layer can be used to identify if a UI object can be switched. Additionally, identifying the second technology can comprise having the technology adapter layer request technology switching capability information from registered technologies for the UI object when navigating down the UI tree. When navigating up the UI tree, information stored by the technology adapter layer can be used to identify the second technology.

Abstract: Automation of actions on a server system (e.g., web server, FTP server) is facilitated by a server system that is ready for actions to be performed upon it. Because there are scenarios when a server system is not in a state to be acted upon (e.g., web page changed due to navigation, script execution, asynchronous request through dynamic web extensions), an automated action needs to be synchronized to when then server system is in a ready state for that action to occur. A wait-for-ready state can be initiated that detects when a server system is ready for a next action.

Abstract: Recording of functional steps resulting from actions in an application is desirable for performing functional testing or user interface automation of an application. However, certain events that may result from actions occurring in an application are often difficult to record, which may lead to playback failure. Further, a user's intent when performing an action is difficult to determine. In order to obtain effective playback, a reliable and efficient recording of an application's functional steps needs to occur. Injecting wrapper functions into an application and monitoring an event generator's state before and after an action has occurred may yield more reliable and effective results.

Abstract: Various technologies and techniques are disclosed for providing direct synchronous input. An input monitor determines where an input from a sender that is directed to a target element is about to be delivered. One example for providing an input monitor includes using a system hook. If the input monitor determines that the input is about to be delivered to the target element, the input is delivered to the target element, and the sender is notified that delivery to the target element succeeded. An interface for providing a direct synchronous input is also described. The interface has a start method for monitoring inputs being sent to target elements from a sender. The interface also has a received event for notifying the sender when a particular input is received by the target element.