Browse Prior Art Database

Testharness for use in a distributed environment

IP.com Disclosure Number: IPCOM000014796D
Original Publication Date: 1999-Dec-01
Included in the Prior Art Database: 2003-Jun-20
Document File: 3 page(s) / 40K

Publishing Venue

IBM

Related People

Andrew Couchman: AUTHOR

Abstract

The overall problem is a requirement for a test harness to test parts of Java(*) which are designed to run in distributed environments. Such a test will consist of at least two separate programs that communicate with each other. There is however no limit to the number of programs that a test may

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

Page 1 of 3

Testharness for use in a distributed environment

The overall problem is a requirement for a test harness to test parts of Java(*) which are designed to run in distributed environments. Such a test will consist of at least two separate programs that communicate with each other. There is however no limit to the number of programs that a test may
consist of. The most important parts of the specification for such a test harness are as follows: - must be written in a platform independent language (such as Java) that can run on all the platforms Java can run on

- has the ability to start up any number of programs

- has a daemon program running on the machines upon which tests will be run which, once started, will remain in a suitable state to run tests, until it is stopped. This program must not be affected by the success or failure of one particular test. - can detect a failure during the startup or running of any one of the programs

- can detect when the test has successfully run to completion

- can reliably shut down all programs that were started, regardless of whether the test was successful or not. This is particularly important to free up resources that one test uses, ready for another test to reuse them

- must be extremely flexible to cope with the many possible scenarios under which tests need to be run including:

- allowing tests to share data, by supplying a place

on the server where the data can be stored and read back from

- providing a simple API to allow new tests to run under the harness

- allowing full customisation of the environment under which tests will run on a per machine basis.

- keeping the component of the test harness which runs on the test machine to a simple bare minimum - all the configuration information is kept in one place on the server - making the process of moving the test server from one machine to another as simple as possible

- provide a high-level of debugging information for analysing test failures

- if written in Java the test harness must not use the same version of Java that is being tested, as this could be defective to the point that the test harness does not function correctly

1

Page 2 of 3

N.B. with new function now available in Java (namely CORBA support) it will be possible for non-java programs to run in the test harness, as long as the programming languages they are written in support CORBA.

The initial problem was to be able to test the functionality of Java, using testcases which consist of a number of different programs (components). To run the test...