Abstract: A system and method for testing a software application, comprising: a structure of actions to be executed by the software application; a visual interface of the software application comprising a plurality of components; and a first link between one of the actions and a corresponding one of the components in the visual interface.

Abstract: A system and a method of providing a visual interface for creating, maintaining, and reviewing the results of, automated functional tests of software applications that includes screen views for each window automated within the application under test. The system and method provide a visual interface for creating and modifying functional tests of software applications geared for novice users. The visual interface includes a screen preview, test steps, properties and a storyboard. A test logic builder interface enables novice users to add logic, including verification and synchronization, to their visual test transactions without having to understand programming concepts.

Abstract: Tracking resource use includes determining when the resource is allocated, determining when the resource is first used, determining when the resource is last used, and determining when the resource is deallocated. The resource may be a software object. Deallocating the resource may be performed automatically by a run time system when there are no remaining references to the object in run time code or variables. Deallocating the resource may include at least one of: setting a flag for the resource and adding an identifier for the resource to a list of resources to be deallocated. Time measurements may correspond to a count of garbage collection cycles. Tracking resource use may also include determining additional resource usage metrics.

Abstract: A method of developing software capable of performing a task, the task comprising at least one task step required to perform the task. The task step has a resultant effect. The method comprises recording a use case comprising one or more scenarios, that comprise one of more further steps; recording the scenario or one of the scenarios as a main success scenarios such that the resultant effect of the main success scenario is the same as the resultant effect of the task step. Use cases which have been stripped of context-specific information may be re-used. Such information may be included in a reference to the re-used use case.

Abstract: Computation of a metric, termed “memory pressure,” provides an indication of software application scalability, in terms of memory, when making changes to multi-user applications. The memory pressure metric may be measured on a single user application run and does not require running the application under load tests. Since the metric can be measured on single user application runs, software testing and assessment takes considerably less time, resulting in developer productivity increase.