Abstract: A JIT compiler is debugged by comparing the native code it generates with the native code generated from a reliable JIT compiler. The different compilations are performed using the same input data. The input data is recorded by intercepting the communication exchanges between a runtime environment and the reliable JIT compiler during the compilation of a program. The input data of each communication is stored using a key based on at least one parameter in an API call from a JIT compiler to the runtime environment. A debugging tool is then used to initiate the compilation of a method using a JIT compiler under test using the previously recorded input data.

Abstract: A JIT compiler is debugged by comparing the native code it generates with the native code generated from a reliable JIT compiler. The different compilations are performed using the same input data. The input data is recorded by intercepting the communication exchanges between a runtime environment and the reliable JIT compiler during the compilation of a program. The input data of each communication is stored using a key based on at least one parameter in an API call from a JIT compiler to the runtime environment. A debugging tool is then used to initiate the compilation of a method using a JIT compiler under test using the previously recorded input data.

Abstract: Methods, systems, and computer-readable media to test user interfaces (UIs) in multiple execution environments are disclosed. A particular method includes selecting one or more UI tests and one or more execution environments in which to run the UI tests. One of the execution environments is designated as a driver execution environment. A driver UI corresponding to the driver execution environment is displayed. When a UI action is received at the driver UI, a data representation of the UI action is transmitted from the driver execution environment to each of the other execution environments. The UI action is substantially concurrently repeated at each of the other execution environments.

Abstract: Code morphing includes rewriting at least one underlying control structure of known code without affecting an intended context of the code.

Abstract: The exposure and usage of one or more particular physical and logical resources by methods within an isolation boundary may be annotated so as to preempt resource usage conflicts. Further described are tools, contracts, and collaborative processes for at least identifying potential resource usage conflicts. More particularly, the example tools, contracts, and collaborative processes may be used to annotate at least one of exposure and consumption of one or more particular physical and logical resources by methods within an isolation boundary.

Abstract: An exemplary media implementation precipitates a device to perform actions including: determining if an instruction of a line of common intermediate language (CIL) code meets a predetermined exception-related criterion; and if so, injecting a decision point in association with the instruction of the line of CIL code, the decision point enabling a decision as to whether an exception is to be thrown with respect to the instruction. An exemplary device implementation includes: instrumented CIL code that includes a test couplet corresponding to a decision point and an associated instruction, the associated instruction capable of causing a fault; a decision runtime library that is adapted to evaluate the test couplet to selectively decide whether to throw an exception with respect to the associated instruction; and a common language runtime component that interprets the decision point so as to call the decision runtime library prior to executing the associated instruction.