Abstract: Techniques are described herein that are capable of generating mock-based unit test(s) for an end-to-end test of a code snippet (a.k.a. system to test (STT)). For instance, method(s) in a code snippet that have a designated functionality are replaced with a wrapper function that has the designated functionality. Shims and/or stubs are inserted in the wrapper function to replace behavior of the method(s) with regard to callback method(s) from one or more dependencies of the method(s). Inputs that are included in the callback method(s) and that are intended for the code snippet are simulated to provide simulated inputs for the code snippet.

Abstract: Techniques are described herein that are capable of generating mock-based unit test(s) for an end-to-end test of a code snippet (a.k.a. system to test (STT)). For instance, method(s) in a code snippet that have a designated functionality are replaced with a wrapper function that has the designated functionality. Shims and/or stubs are inserted in the wrapper function to replace behavior of the method(s) with regard to callback method(s) from one or more dependencies of the method(s). Inputs that are included in the callback method(s) and that are intended for the code snippet are simulated to provide simulated inputs for the code snippet.

Abstract: Described is a technology in which test case content in the form of a web application is provided to a client browser from a test case management system over a web server. Results of running the test case are similarly communicated back. This allows different web application test harnesses to be run on whatever Internet browser the client computing device is running, and is independent of any operating system. The client registers with the test case management system through the website, and receives a browser identifier for use in future communications. In one protocol, the client uses the identifier in heartbeats sent to the test case management system, including a heartbeat indicating when the client is available to run a test case, when the test case is complete, and the results of performing the test case. Also described are various interfaces that facilitate component communication.

Abstract: Described is a technology in which test case content in the form of a web application is provided to a client browser from a test case management system over a web server. Results of running the test case are similarly communicated back. This allows different web application test harnesses to be run on whatever Internet browser the client computing device is running, and is independent of any operating system. The client registers with the test case management system through the website, and receives a browser identifier for use in future communications. In one protocol, the client uses the identifier in heartbeats sent to the test case management system, including a heartbeat indicating when the client is available to run a test case, when the test case is complete, and the results of performing the test case. Also described are various interfaces that facilitate component communication.