Abstract: Various technologies and techniques are disclosed for supporting globalization in user interface automation. A resource key is provided that contains at least three data elements. A resource type data element contains data representing a resource type, a resource location data element contains data representing a location to a resource file, and a resource identifier data element contains data-representing a resource identifier. During a resource file extraction operation, the resource location data element is used to locate the resource file, and the resource type data element and the resource identifier data element are used to locate a resource within the resource file that matches the resource type and the resource identifier. A process is provided for resolving a full path name to a resource file. A process is provided for performing a post-extraction action on an extracted resource string.

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.

Abstract: Described is the use of query identifiers that provide computer users a method of “bookmarking” (uniquely identifying) any user interface (UI) element in any UI framework. This is useful for testing programs, assistive technologies, and teaching activities. The unique query element identifier is identified for a target UI element to locate within a hierarchy of UI elements. For example, the element's Name, ClassName, Instance, AccessibleName, Role, ControlId and AutomationId may be used to develop the unique query element identifier. From the query elements in the hierarchy of UI elements, a query identifier is generated for the target UI element. The query identifier includes the query element identifier and possibly ancestor query element identifiers, with each ancestor query element identifier corresponding to a higher-level ancestor element relative to the target element in the hierarchy. The query identifier may be used to locate the target element for testing versions of application programs.

Abstract: Using recorder technology for finding defects in software applications by capturing software and/or user-driven events in a computing system. In one implementation, recorder technology is employed in a software defect reporting tool for reporting customer feedback related to software defects or bugs. The recorder can be utilized to capture events and defects for reporting such information to application vendors for defect resolution. A record file can be played back to reproduce the software defect and the steps leading up to the defect, and convert the information into a human readable file format. The recorder can also be used to create regressions scripts. When employed in a beta testing client reporting tool, customers are now able to record reproduce steps automatically, and ship the output file to the software vendor for more comprehensive reporting and hence, effective triage of the software defect.

Abstract: Described is the use of query identifiers that provide computer users a method of “bookmarking” (uniquely identifying) any user interface (UI) element in any UI framework. This is useful for testing programs, assistive technologies, and teaching activities. The unique query element identifier is identified for a target UI element to locate within a hierarchy of UI elements. For example, the element's Name, ClassName, Instance, AccessibleName, Role, ControlId and AutomationId may be used to develop the unique query element identifier. From the query elements in the hierarchy of UI elements, a query identifier is generated for the target UI element. The query identifier includes the query element identifier and possibly ancestor query element identifiers, with each ancestor query element identifier corresponding to a higher-level ancestor element relative to the target element in the hierarchy. The query identifier may be used to locate the target element for testing versions of application programs.

Abstract: Various new and non-obvious apparatus and methods for ensuring a user interface element is visible within an automated user interface test environment are disclosed. One of the disclosed embodiments is a method for locating a parent element of the user interface element and then making the user interface object visible using top-down scrolling, bottom-up scrolling, expanding, or a combination of all three. Top-down scrolling scrolls the parent element until the user interface element becomes visible. Bottom-up scrolling first locates a grandparent element. The parent element then scrolls until the user interface element is within the parent object. The grandparent element is then scrolled until the parent element is visible within the grandparent element, the parent object is then scrolled until the user interface element is visible within the grandparent element.

Abstract: Various new and non-obvious apparatus and methods for synchronizing a request to perform a target action on a user interface element within a user emulation test program are disclosed. The disclosed exemplary apparatus and methods should not be construed as limiting in any way. One of the disclosed embodiments is used when a user emulation test program is unable to access at least one background thread, or is working in an environment where at least one thread may essentially be in a busy state. The method comprises choosing a target element, establishing time-out criteria, a calling entity invoking a target action to be performed on the target element, attempting to perform the target action on the target element, and returning control to the calling entity when either the target action is successfully performed on the target element or when the previously-mentioned time-out criteria is met, in which case a synchronization error condition is generated.

Abstract: Techniques and tools are described for recording input from user actions in a user interface (UI) and replicating the UI activity on a computing device. When recording and replicating UI activity, these techniques and tools improve the readability of the recorded input data and the reliability of playback. The techniques and tools may be used in combination or separately. For example, a recording tool uses a set of filters, which aggregates recorded data into basic, readable primitive methods. The recording tool converts the aggregated data into playback code by converting the playback primitive methods into corresponding computer language instructions. A playback tool may then replicate the initial recorded UI activity by playing back the computer language instructions.