Abstract: A test environment may include qualitative evaluations of the test code used to test application code. Several qualitative evaluations may be determined from analysis of test code in compiled or source form, including evaluating descriptive assertions made by the test code, dependency evaluations, cyclomatic complexity evaluations, return value assertions, mutable parameter assertions, and test effectiveness history. The qualitative evaluations may also include analysis of the test code in relation to the application code, including exception capturing, boundary conditions, assertions for returned values, and other evaluations. The test code evaluations may be presented in a user interface along with the test code and may be used to manage testing progress of an application. The test code evaluations may be integrated into a code development application with a graphical user interface.

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: A test environment may include qualitative evaluations of the test code used to test application code. Several qualitative evaluations may be determined from analysis of test code in compiled or source form, including evaluating descriptive assertions made by the test code, dependency evaluations, cyclomatic complexity evaluations, return value assertions, mutable parameter assertions, and test effectiveness history. The qualitative evaluations may also include analysis of the test code in relation to the application code, including exception capturing, boundary conditions, assertions for returned values, and other evaluations. The test code evaluations may be presented in a user interface along with the test code and may be used to manage testing progress of an application. The test code evaluations may be integrated into a code development application with a graphical user interface.

Abstract: Non-public software constructs within a portion of code may be made accessible by analyzing the code, locating non-public items such as classes, objects, data structures, methods, interfaces, arrays, and other items, and creating a public call for the item in an executable code. In some instances, a call may reference one or more non-public items and such a call may be a static call created at the same time as the function, or may be a dynamically created at runtime. The calls may handle non-public arrays within calls, generic calls, as well as calls using a non-public interface.