Abstract: 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.

Abstract: 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.

Abstract: Architecture includes an integrated tool that allows a tester to automatically persist test plan information in association with related content while the tester is interacting with that content in an IDE. The tool further enables the tester to formally associate actions/expectations with specific items of content. In previous solutions, references to existing content are often lost due to inexact or missing descriptions. Formal associations allow for reuse of valuable content and avoid unnecessary recreation. The tool is integrated with the IDE, and thus, does not necessitate that the tester manually type or write descriptions of intent and expectations. This reduces the test plan cost significantly. The tool also persists information in a formal, self-describing format that enables easy consumption by either human testers or secondary software applications (e.g., for the purposes of identifying plans, performing associated actions and verifying expected behavior).