Browse Prior Art Database

Method and System for Defining a Stack Model and Tracking Changes to a Test Execution Stack

IP.com Disclosure Number: IPCOM000199695D
Publication Date: 2010-Sep-15
Document File: 3 page(s) / 49K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method and system for defining a stack model and tracking changes to a test execution stack to validate adherence to prerequisites for subsequent test executions is disclosed.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 3

Method and System for Defining a Stack Model and Tracking Changes to a Test Execution Stack

Disclosed is a method and system for defining a stack model and tracking changes to a test execution stack.

Many test frameworks call clean-up scripts as a prerequisite before running test cases in order to ensure that the after effects of the already run test cases are removed. Some of these cleanup activities might not be required as the previously run test cases might not have changed the "test elements" concerned.

A test environment may include an Operating System of a particular version, a Database Server, and an Application Server.

The method and system disclosed herein, involves describing a test environment and elements of the test environment using a Stack Model. The Stack Model may be described in an XML file. The Stack Model is updated with intercepts to Stack Parameter changes received during the test runs. The Stack Parameter changes are determined by comparing the Stack Model with default factory settings which are considered as the baseline.

The Stack Model is represented through a hierarchical data structure which can be segmented to levels and sub-levels of granularity as required. The hierarchy can be traversed to identify only those elements which have changed, and look for parameters which have been changed. Only the changed parameters may be reset. Alternatively, the test case may be continued without changes based on the prerequisite conditions of the test case.

In an exemplary implementation of the method and system disclosed, a test environment might consist of a DB2* data server and a WebSphere** Application Server on an AIX*** operating system. Both DB2 and the WebSphere Application Server are deployed on the system with factory settings. In addition, a Message Queue (MQ) may also be deployed, although the MQ is not a prerequisite for running the tests.

The hierarchy of the test environment may be:

1

Page 2 of 3

Here, the indicative XML Stack Model file defines the scope of the test environment. Only the parameters mentioned in the hierarchy are considered for executing the test cases. Although the AIX parameters and MQ parameters may change, they are not considered to be elements in the test environment as they are not mentioned in the hierarchical list...