Abstract: Models of certain groups of graphical user interface (GUI) objects (e.g., menu objects, product objects, title objects, etc.) are created. A website is then modeled as a state machine (also called a blueprint), in which states are used to model webpages of the website. Identifying characteristics of the states are specified based on the models of the GUI objects. Certain scanning options are used to reduce the complexity of the state machine and accelerate the state machine creation process, known as the “one per page” and “once per app” scanning options. After the state machine model of the website has been created, test cases are generated as traversals through the state machine. In one embodiment, user logs direct the generation of test cases so that the test cases resemble past user behavior.

Abstract: Models of certain groups of graphical user interface (GUI) objects (e.g., menu objects, product objects, title objects, etc.) are created. A website is then modeled as a state machine (also called a blueprint), in which states are used to model webpages of the website. Identifying characteristics of the states are specified based on the models of the GUI objects. Certain scanning options are used to reduce the complexity of the state machine and accelerate the state machine creation process, known as the “one per page” and “once per app” scanning options. After the state machine model of the website has been created, test cases are generated as traversals through the state machine. In one embodiment, user logs direct the generation of test cases so that the test cases resemble past user behavior.

Abstract: A test script is generated in an automated fashion based on a master key file (and optionally, additionally based on user logs) in order to test a software application. The master key file may include one or more scripts of every (or nearly every) possible interaction (e.g., request, presentation, executed action, and so on) a user may have with the software application under test. Often times, the master key file captures each and every request that could be made from a client device to the software application under test executing at a server.

Abstract: A test script is generated in an automated fashion based on a master key file (and optionally, additionally based on user logs) in order to test a software application. The master key file may include one or more scripts of every (or nearly every) possible interaction (e.g., request, presentation, executed action, and so on) a user may have with the software application under test. Often times, the master key file captures each and every request that could be made from a client device to the software application under test executing at a server.