Browse Prior Art Database

Software Validation Test Facilitator "test_scripts"

IP.com Disclosure Number: IPCOM000109734D
Original Publication Date: 1992-Sep-01
Included in the Prior Art Database: 2005-Mar-24
Document File: 4 page(s) / 158K

Publishing Venue

IBM

Related People

Cooper, R: AUTHOR [+3]

Abstract

The "test_scripts" test tool is a Bourne shell script which contains general subroutines used by tests for executing commands and reporting results. By including "test_scripts" in a test case file, an environment is created in which setup and cleanup steps are automated. The focus of the testcase programmer is on the command being tested, not record-keeping details. Introduction

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 38% of the total text.

Software Validation Test Facilitator "test_scripts"

       The "test_scripts" test tool is a Bourne shell script
which contains general subroutines used by tests for executing
commands and reporting results.  By including "test_scripts" in a
test case file, an environment is created in which setup and cleanup
steps are automated.  The focus of the testcase programmer is on the
command being tested, not record-keeping details.
Introduction

      "Test_scripts" best serves command-oriented test suites, whose
functional validation can be determined by predictable output or
execution return codes.  The tool also works well in a distributed
environment.  Several combinations of sub-tests may be executed,
simultaneously, making the test suite more portable to other
environments.

      The command-line orientation of the tool reflects the original
goals of the tool.  Execute as many commands of the system as
possible, emulating what customers might do in their own
environments.  Customers see standard output, standard error
messages, and they check the return codes from their commands.  The
tool provides an interface for these types of tests.

      The test tool provides an integrated testing environment in
which to execute testcases.  A unique directory structure is created
for each test, based on testcase name, test iteration and process id,
allowing simultaneous executions of a test suite without file
dependence.  This directory structure is automatically removed once
testcase execution has completed, unless the user requests to have it
saved.  User-saved temporary files must be manually removed.

      Log, status and results files are created for each execution of
a testcase.  These files are stored in a directory structure based on
the test suite, the command being tested, the process id and the test
repetition number.  Two levels of data are kept:  high level test
pass/fail status and detailed test output.

      Some commands may only be executed by the "root" user.  These
commands must be listed in file "root_cmds" for each test suite in
the test suite directory.  This file is checked before command
execution to ensure that the user has the required privileges.
Testcase Specification

      Use of the "test_scripts" tool requires the testcases to be
organized in a consistent manner.  The testcase script must have the
following parts:
   a. shell parameter (CASE_PARAMETERS) specification for default
test sequencing,
   b. main shell procedure which brings in the test_script shell
procedures followed by a call to the driver function (main_exec),
   c. shell procedures for local setup and cleanup, if required,
   d. shell procedures for each individual test of the command in the
testcase, and
   e. shell procedures for other testcase functions, as required.
Each of these parts is briefly explained.
   a. testcase shell parameter "CASE_PARAMETERS"
      This shell variable is spe...