Browse Prior Art Database

Multi Media Customer-Based Test Automation using State Machine Paradigm

IP.com Disclosure Number: IPCOM000104083D
Original Publication Date: 1993-Mar-01
Included in the Prior Art Database: 2005-Mar-18
Document File: 4 page(s) / 126K

Publishing Venue

IBM

Related People

Clement, JD: AUTHOR [+2]

Abstract

Existing art focuses on tools to bridge test coverage and completeness relative to technical functional specifications. This level of detail is not easily reviewed by Customers nor does it lend itself to higher level abstraction for usability and cross platform discussion. Conversely, actual concatenation of test cases (which may be very well done individually) into customer-based scenarios often is delayed by errors in setup and environmental assumptions.

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

Multi Media Customer-Based Test Automation using State Machine Paradigm

      Existing art focuses on tools to bridge test coverage and
completeness relative to technical functional specifications.  This
level of detail is not easily reviewed by Customers nor does it lend
itself to higher level abstraction for usability and cross platform
discussion.  Conversely, actual concatenation of test cases (which
may be very well done individually) into customer-based scenarios
often is delayed by errors in setup and environmental assumptions.

      Overview:  This disclosure trisects the System Test problem
with tools and procedures to address each area independently.

1.  Customer scenarios can be constructed by selecting a sequence of
    basic function descriptions.  This sequence is independent of the

    keystrokes used to execute and can be reviewed by customers and
    usability for appropriateness.

2.  Manual, Automated, and Multi Media task definitions can be
    constructed and tested.  Their 100% reuse is ensured by
    conformance to standards.  Multidimensional description of the
    Entry and Exit 'states' can be tested.

3.  Primitives can be created to 'bridge' between the output state of
    one task and the input state of the next.  These primitives are
    the 'glue' that eliminates problems associated with setup for
    traditional testing.

This problem decomposition allows the customer scenarios (part 1) to
be reusable across multiple platforms reducing cycle time, resources,
and error injection rates.

Component Description Refer to the figure.

1.  The User Task Table-UTT (10) consist of a row for each common
    user task.  It also contains the variables required for execution
    of the tasks.  Tasks can contain sub-tasks which have variables
    to be selected (or default accepted).  SEND NOTE Could expand to:

    o   ADDRESS Note (&LIST or &USER1)

    o   SUBJECT (&Line1 or &Default)

    o   TEXT (&Para1 or &Para2)

    o   OTHER_NAME (&CCLIST or &USER2)

2.  After the Customer Scenario is built by selecting a series of
    tasks from the UTT, the Customer Scenario Builder-CSB (20) guides
    the operator thru a series of Questions to resolve variables
    called out in support of the tasks selected.

3.  The output of the CSB is an Edited User Scenario-EUS (30) which
    is a common source for testing in ANY related environment.

4.  The Task Description Table-TDT (40) contains the keystrokes
    and/or manual steps required to execute a selected task.  The
    preferred implementation will be Multi Media containing:

    o   Automated Keystrokes if applicable

    o   Verbal instructions ("Check that ...  and press Y...)
        requiring human judgment or steps not adaptable to
        automation)

    o   Backup script for printing of instructions

    o   Pointer to State Variable Vector-SVV

  ...