Microsoft Technology Licensing, LLC

Ryan J Cavanaugh

Eric I Maino

Dmitri A Klementiev

Scott M Louvau

Kristopher Makey

Xuechun Li

Zhanliang Chen

Vijaya K Upadya

Young Kun Joo

Christopher A Smith

Kyrylo Osenkov

Gabriel Esparza-Romero

Damon C Tivel

Eric J Gruber

A generated object model engine abstracts actions, used in test cases, in a manner to produce new object model types that are independent of an underlying code implementation. The generated object model engine analyzes action classes to aggregate a set of actions having similarly-related class types. Action classes having similarly-related class types are then used to form a new object model type. The new object model type may be used in a test case to hide the action's code implementation from the test case.

Generated object model for test automation

A test case can be run with actions from the test case being executed in multiple execution paths. This can be done with the aid of an action broker. For example, the broker may identify available automation implementations for the actions and use a priority list to select between available automation implementations for executing an action from the test case. The broker may also perform conversions of results of actions for use by implementations executing other actions in different execution paths, as well as passing results between implementations in different execution paths.

Multi-path brokered test automation execution

A test case is abstracted into a re-useable script or other declarative form that expresses the intent of a task rather that defining how the test will be performed. Tools translate the declarative test into a series of steps corresponding to code that implements the action indicated in the declarative test. The schema for the tests can be dynamic. New forms of test cases can take advantage of new actions so that the library of actions can be extended. Libraries are interchangeable. Test cases can be generated using a state machine. New test cases can be composed dynamically using a state machine to create new test cases.

Using a DSL for calling APIS to test software

A development system is provided. The system includes a workspace component to visually display one or more model components. A separation component automatically segments the model components into two or more project components. A synchronization component can be provided to automatically update at least one of the project components in view of changes made to at least one other project component.

N-tiered applications support via common interface

Software failures are processed by categorizing images associated with the failures into groups based on similarities in the images. The categorizing of the images may be performed by a software failure analysis tool. The images may include full or partial screenshots of a computer at the time of the software failure. An image may be part of the output of a test, or may be part of a report of a software failure from an end user of the software. The software failure analysis tool may be part of a larger software test management system.

Categorizing images of software failures

Growing community of inventors

Bellevue, WA, United States of America

Ryan J Cavanaugh