Abstract: Methods and systems for developing software can perform both compilation operations and read-evaluate-print-loop (REPL) operations on source code. In one embodiment, an integrated development environment can include a source code editor and a compiler and can perform the following operations: receiving source code and performing REPL operations as the source code is received; receiving edits in the source code for which REPL operations have been performed and compiling, by the compiler, the edited source code; and storing results of execution of the edited source code for use in subsequent REPL operations.

Abstract: Methods and systems for developing software can perform both compilation operations and read-evaluate-print-loop (REPL) operations on source code. In one embodiment, an integrated development environment can include a source code editor and a compiler and can perform the following operations: receiving source code and performing REPL operations as the source code is received; receiving edits in the source code for which REPL operations have been performed and compiling, by the compiler, the edited source code; and storing results of execution of the edited source code for use in subsequent REPL operations.

Abstract: In one embodiment, an automated user-level testing tool is enhanced to capture additional information about the state of the automated testing, beyond just a screenshot of the application-under-test. In another embodiment, an automated user-level testing tool is enhanced to capture testing state information for multiple points in time (referred to as “snapshots”), beyond just when the application-under-test crashes. This captured information from one execution of an automated test (one “test run”) is stored in one test log, which can then be viewed using a test log viewer. In one embodiment, the graphical user interface (GUI) for the test log viewer includes four areas: a screenshot area, a test script area, a stack trace area, and a timing area. The content shown in the screenshot area, the test script area, and the stack trace area is specific to a particular point in time during a test (e.g., a particular snapshot).

Abstract: In one embodiment, an automated user-level testing tool is enhanced to capture additional information about the state of the automated testing, beyond just a screenshot of the application-under-test. In another embodiment, an automated user-level testing tool is enhanced to capture testing state information for multiple points in time (referred to as “snapshots”), beyond just when the application-under-test crashes, This captured information from one execution of an automated test (one “test run”) is stored in one test log, which can then be viewed using a test log viewer. In one embodiment, the graphical user interface (GUI) for the test log viewer includes four areas: a screenshot area, a test script area, a stack trace area, and a timing area. The content shown in the screenshot area, the test script area, and the stack trace area is specific to a particular point in time during a test (e.g., a particular snapshot).