Abstract: Controls of a graphical user interface (GUI) in an application under test (AUT) can be tested where the AUT utilizes an accessibility support framework. An accessibility application programming interface (API) can be used to expose controls in the GUI along with their properties. Using an identified control's properties, a set of valid events can be determined for a desired control. Based on the events, parameters for input data for a desired control can be defined, for example, to include data types and data type limitations. Equivalence partitions can be determined for the input data based on the defined parameters, and events can be passed to the accessibility API, along with corresponding input data from the equivalence partitions, to be performed in the desired control of the AUT.

Abstract: A technique for determining the impact of multiple users' actions is described. According to this technique, information specifying multiple users' actions is aggregated. This information includes linkages that indicate the initiators of the multiple users' actions. Then, the impacts of the multiple users' actions are determined based on the aggregated information. In particular, the impact of a given user's action includes a direct component performed by the given user and an indirect component performed by other users in a social graph in response to the given user's action, where the social graph includes relationships between the other users and the given user. For example, the multiple users' actions and the social graph may be associated with a website, and the determined impacts may allow traffic and/or revenue of the website to be increased.

Abstract: Controls of a graphical user interface (GUI) in an application under test (AUT) can be tested where the AUT utilizes an accessibility support framework. An accessibility application programming interface (API) can be used to expose controls in the GUI along with their properties. Using an identified control's properties, a set of valid events can be determined for a desired control. Based on the events, parameters for input data for a desired control can be defined, for example, to include data types and data type limitations. Equivalence partitions can be determined for the input data based on the defined parameters, and events can be passed to the accessibility API, along with corresponding input data from the equivalence partitions, to be performed in the desired control of the AUT.