Browse Prior Art Database

Method for automating space constraint testing for GUI applications

IP.com Disclosure Number: IPCOM000172893D
Original Publication Date: 2008-Jul-18
Included in the Prior Art Database: 2008-Jul-18
Document File: 2 page(s) / 82K

Publishing Venue

IBM

Abstract

Method for automating space constraint testing for GUI applications

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

Page 1 of 2

Method for automating space constraint testing for GUI applications

Background of the invention

GUI testing commonly involves verifying whether text

,

controls

,

                                          and images fit into their designated spaces within displayed windows. A typical defect found during such testing might involve

,

for

       a text string that's truncated because it doesn't fit within a window's boundaries. Another possible defect is the use of a large space for the display of only small items

,

example

,

a waste of otherwise useful

screen real estate.

Most GUI testing involves manually inspecting each window that can be displayed by the application. This is often done multiple times to encompass every form of content that can be displayed in each window. A person doing this sort of testing must recognize when certain items are missing from the display because of space constraints. This is sometimes challenging. For example

,

when a text string is

truncated at the space between words

,

                         the person running a manual test may not immediately notice that additional words in the string are missing. That problem becomes even more of a challenge for internationalized GUI testing. For GUI testers who are not multilingual

,

there may be no easy way to tell

when text displayed in a foreign language has been truncated.

Summary of the invention

Problems like these are amenable to runtime (or dynamic) analysis. Runtime analysis techniques are used to monitor software applications as they run. Runtime analysis is often used to detect various runtime errors. The user of a runtime analysis tool must generally run an "instrumented" version of his or her program. That is

,

                an instrumentation process adds checks with which the instrumented program can be monitored when it runs. IBM Rational Purify is an example of a runtime analysis tool that can detect conditions in which certain boundary conditions are violated. However

,

                                                   Purify does not currently detect conditions in which text or controls do not fit into a displayed window.

To enable detection of these conditions

,

                          the application to be tested can be instrumented in such a way that the runtime analysis tool intercepts the creation of dialog boxes and other windows. The runtime analysis tool can also intercept the display of GUI controls

,

text strings

,

and images. Given those

intercepts

,

when displayed items such as text strings are output by the instrumented application

,

                                                              the runtime analysis tool can recognize the dialog or window spaces in which those text strings will be displayed. The runtime analysis tool can then compare the items' size with the available space. The runtime analysis tool can perform a similar size comparison for GUI controls when they are displayed. It can perform a similar analysis for displayed images. If any displayed object does not fit into its allotted space

,

the runtime analysis tool can present a message indicating which items (text strings

,

for exampl...