Browse Prior Art Database

Software Testing Automation Framework (STAF)

IP.com Disclosure Number: IPCOM000014017D
Original Publication Date: 1999-Dec-01
Included in the Prior Art Database: 2003-Jun-19
Document File: 2 page(s) / 31K

Publishing Venue

IBM

Related People

Charles Rankin: AUTHOR [+2]

Abstract

A program is disclosed which provides a testing framework designed with reuse in mind and which is easy to use and extend from a variety of programming languages. The Software Tesing Automation Framework (STAF) provides a set of reusable modules (called services) which greatly increase the ability to create automated testcases and test environments. In so doing, the framework had to handle the following constraints. *Compact *Differing operating system codepages *Multiple programming language support *Location transparency *Providing a robust and extensible set of software services When, sending messages between processes, and more importantly, when sending messages to different systems on a network, the possibility that the processes may be using different codepages becomes a distinct possibility. The likelihood increases when sending messages between different operating systems, and it is almost a certainty in a testing environment where multiple national language versions of an application may be being tested simultaneously. STAF handles this problem by converting data to and from Unicode (actually the UTF-8 encoding of Unicode) when a message is sent between processes (on the same system or across the network).

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

Page 1 of 2

Software Testing Automation Framework (STAF)

A program is disclosed which provides a testing framework designed with reuse
in mind and which is easy to use and extend from a variety of programming
languages.

      The Software Tesing Automation Framework
(STAF) provides a set of reusable modules (called
services) which greatly increase the ability to
create automated testcases and test environments.
In so doing, the framework had to handle the
following constraints.

*Compact
*Differing operating system codepages
*Multiple programming language support
*Location transparency
*Providing a robust and extensible set of
software services

      When, sending messages between processes, and
more importantly, when sending messages to
different systems on a network, the possibility
that the processes may be using different codepages
becomes a distinct possibility. The likelihood
increases when sending messages between different
operating systems, and it is almost a certainty in
a testing environment where multiple national
language versions of an application may be being
tested simultaneously. STAF handles this problem
by converting data to and from Unicode (actually
the UTF-8 encoding of Unicode) when a message is
sent between processes (on the same system or
across the network).

      In most test environments, multiple
programming languages will be in use. An important
aspect of this is that individual programmers are
rarely skilled in all the programming languages
that are in use around them. This leads to an
issue when a programmer in one language wants to
use a set of functions created by a programmer in
another language. STAF bridges these programming
language boundaries and allows programmers using
one language to easily invoke functions created by
a developer in another language. This is
accomplished by simply having the functions be
expressed in a textual manner, whereby only strings
are passed back and forth. STAF then handles the
transition of these strings from one programming
language...