Browse Prior Art Database

Cross-Platform Testing Automator

IP.com Disclosure Number: IPCOM000114349D
Original Publication Date: 1994-Dec-01
Included in the Prior Art Database: 2005-Mar-28
Document File: 4 page(s) / 96K

Publishing Venue

IBM

Related People

Elder, DB: AUTHOR [+3]

Abstract

A method for platform independent automated testing is disclosed. The implementation of test scripts for an application can occur on any platform supported by that application and can be executed unchanged on any of these platforms.

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

Cross-Platform Testing Automator

      A method for platform independent automated testing is
disclosed.  The implementation of test scripts for an application can
occur on any platform supported by that application and can be
executed unchanged on any of these platforms.

      This article requires that the application to be tested has
been written using an API that is independent of the display device.
This could be one of many windowing systems, since these systems
typically have the ability to run on various sized display devices
with varying resolutions.  This method also applies to API's that
support multiple presentation services (as well as a plurality of
display devices).
  Examples of APIs in a typical system are :
    o  assign_data - assigns a value to a data entry control
    o  selfld_select - selects a choice from a selection field
control
    o  handle - (application provided) method to process actions
invoked
        against a control

      All user interactions with a windowing system application
involve updating controls and the invocation of actions.  This
article describes how these interactions can be recorded (on any
platform) and played back (on any platform).

      To record the user's actions, the script contains two types of
entries: updates to controls, and the names of application actions
that the user invoked.  When a platform independent action is invoked
by the user, the contents of the controls of the window are written
to a file, followed by the name of the action.  The same task
executed on two different platforms will be recorded identically.
The fact that on one platform the user initiated an action via a
pull-down choice, or a push-button does not matter - the system in
either case processed the interrupt by invoking "handle" on the
application.  Because the user interactions are captured in terms of
the API and not the physical display, the script is robust against
changes to the external appearance of the application due to the
application being translated, personalized, etc.

      The playback facility is simply an application that reads the
script and invokes window system APIs to update controls and invoke
actions.
  This article:
  o  Introduces a platform-independent test script facility - the
      script can be recorded and played back on different platforms
      without change.
  o  Provides a script facility that is robust against:
     -  National Language Support
     -  Personalization
     -  New features across versions
     -  Cosmetic changes

      The following scenario will illustrate how the same application
task can be recorded on a text base windowing system, p...