Browse Prior Art Database

Reusable User Interface for Applications and Testcases

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

Publishing Venue

IBM

Related People

Bezviner, DE: AUTHOR

Abstract

Disclosed is a user interface which can present large amounts of data, is easily adapted for different types of data, and is suitable for a wide range of testcases and applications. Currently, applications and testcases all have different user interfaces. The information they give about the application or testcase and its progress ranges from none to very little. The interface described herein increases test productivity and efficiency by providing a reusable, easy-to-read interface that displays large amounts of information about a testcase and its progress. It can also be used just as effectively in application design.

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

Reusable User Interface for Applications and Testcases

      Disclosed is a user interface which can present large amounts
of data, is easily adapted for different types of data, and is
suitable for a wide range of testcases and applications.  Currently,
applications and testcases all have different user interfaces.  The
information they give about the application or testcase and its
progress ranges from none to very little.  The interface described
herein increases test productivity and efficiency by providing a
reusable, easy-to-read interface that displays large amounts of
information about a testcase and its progress.  It can also be used
just as effectively in application design.

      When a testcase or application is designed, the programmer must
also determine what, if any, information to display on the screen.
In a typical test environment, one tester is responsible for many
testcases running simultaneously.  The more information the tester
can get from glancing at the screen, and the easier it is to get it,
the more effi cient the tester can be.  For an application designer,
if many programs have the same "look and feel" then customers will be
able to learn and use the programs much faster.  The challenge is in
designing an inter face that is suitable for many programs or
testcases.

      Currently, many applications print data to a log file, and may
or may not print data to a screen.  Those that print to a screen
often simply scroll the data, so that only a few lines are visible.
This results in a minimal display of information.  The user must be
familiar with the application to know how far along it is.  If the
application repeats, as many testcases in a stress environment do,
much of the time it will be impossible to tell how many repetitions
are complete.  If the user wants to terminate an application or
testcase at a given point, the application must be coded to pause
there, or else the user will not be able to determine when that point
has arrived.  It also makes it much harder to duplicate problems
caused by a particular timing.

      The contents of this disclosure are equally applicable to both
testcases and applications.  For brevity, the remainder of this
disclo sure will specifically mention only testcases.

      The interface contains two parts.  The first contains fixed
infor mation, i.e., information that is desired, and more or less
constant, for all testcases.  This includes the testcase name, number
of repeti tions, number of repetitions completed so far, and the
number of dead locks for this loop.  The second part contains
information that varies from testcase to testcase.  In general, this
will contain at least one line for each major part of the testcase.

      One glance at the top of the display tells the user how many
more times the testcase will repeat, and whether it is involved in
resource conflicts (deadlocks).  One glance at the bottom of the
display tells...