Abstract: A representation of plural alternative interpretations of a user action is provided. Automation code containing the representation is executable to replay the user action.

Abstract: Executable software specification generation can include recording interactions with a user-interface (UI) mockup for a particular program and generating a number of executable software specification for the particular program based on the interactions with the UI mockup.

Abstract: A system and method of automating software testing is provided. The system and method may determine whether some of a plurality of anchor points within application instructions is triggered in response to input from a current operation within operation instructions. If some of the plurality of anchor points is triggered, one of the triggered anchor points may be selected. Instructions may be generated that configure a given processor to pause after the current operation until the selected one of the triggered anchor points completes.

Abstract: Techniques for rule-based automation of an application are disclosed herein. In one embodiment, a system includes an event processor, a rule engine, and a plurality of rules. The event processor is configured to detect events affecting execution of an application being monitored by the automation system. Each rule is configured to analyze at least one of the detected events and to provide a result of the analysis that is further analyzed by a different one of the rules. The rule engine is coupled to the event processor and the plurality of rules. The rule engine is configured to apply each rule to at least one of the detected events based on a value of the rule that determines an event type that the rule is configured to analyze.

Abstract: Executable software specification generation can include recording interactions with a user-interface (UI) mockup for a particular program and generating a number of executable software specification for the particular program based on the interactions with the UI mockup.

Abstract: In one implementation, a stream client emulator includes a stream access module and a monitor module. The stream access module receives stream data from a streaming service and consumes the stream data according to an output rate of a stream without outputting the stream data. The monitor module determines that buffer events have occurred relative to the stream data and a buffer characteristic.

Abstract: A system can comprise a memory to store machine readable instructions. The system can also comprise a processing unit to execute the machine readable instructions. The machine readable instructions can comprise an event extractor to parse a packet capture (pcap) file that includes a packet transmitted via a network between an application under test (AUT) executing on a mobile device and a server to determine a network event based on the packet. The event extractor can also generate an application programming interface (API) command file that includes an API command generated based on the network event.

Abstract: Transport script generation based on a user interface script is disclosed herein. An example apparatus comprises a processor and a memory comprising machine-readable instructions. When executed by the processor, the machine-readable instructions cause the processor to monitor network requests in response to execution of a user interface script. The processor is to modify a transport script based on the network requests by determining whether a first one of the network requests corresponds to a user interface script command of the user interface script, and, when the first network request corresponds to the user interface script command, inserting the user interface script command as a comment to the transport script.

Abstract: A system can comprise a memory to store machine readable instructions. The system can also comprise a processing unit to execute the machine readable instructions. The machine readable instructions can comprise an event extractor to parse a packet capture (pcap) file that includes a packet transmitted via a network between an application under test (AUT) executing on a mobile device and a server to determine a network event based on the packet. The event extractor can also generate an application programming interface (API) command file that includes an API command generated based on the network event.

Abstract: A representation of plural alternative interpretations of a user action is provided. Automation code containing the representation is executable to replay the user action.

Abstract: A system and method of automating software testing is provided. The system and method may determine whether some of a plurality of anchor points within application instructions is triggered in response to input from a current operation within operation instructions. If some of the plurality of anchor points is triggered, one of the triggered anchor points may be selected. Instructions may be generated that configure a given processor to pause after the current operation until the selected one of the triggered anchor points completes.

Abstract: In one implementation, a stream client emulator includes a stream access module and a monitor module. The stream access module receives stream data from a streaming service and consumes the stream data according to an output rate of a stream without outputting the stream data. The monitor module determines that buffer events have occurred relative to the stream data and a buffer characteristic.

Abstract: A script specifies a script action and an expected reaction in response to the script action. When one of the script actions is executed, a failure is detected indicating that the expected reaction did not occur. In response to the failure, a fallback action is executed.

Abstract: Techniques for rule-based automation of an application are disclosed herein. In one embodiment, a system includes an event processor, a rule engine, and a plurality of rules. The event processor is configured to detect events affecting execution of an application being monitored by the automation system. Each rule is configured to analyze at least one of the detected events and to provide a result of the analysis that is further analyzed by a different one of the rules. The rule engine is coupled to the event processor and the plurality of rules. The rule engine is configured to apply each rule to at least one of the detected events based on a value of the rule that determines an event type that the rule is configured to analyze.