No abstract

No abstract

In recent years, Web applications have grown rapidly

No abstract

The object-oriented (OO) paradigm is rapidly gaining acceptance in the software industry. However, the powerful features of this new paradigm also introduce a new set of OO software testing and maintelrance problems. The pioneering work in identifying the.se new problems includes [7, 10-12, 14, 16, 18]. The problems can be summarized as: 1) the understanding problem; 2) the complex interdependency problem; 3) the object state behavior testing pr'ol> lem; and 4) the tool sirpport problem. Detailed di.scussions of these problems will be provided later. Our industrial experience confirms these discoveries.In an attempt to solve these problems, the Software Engineering Center for Telecommunications at the University of Texas at Arlington (UTA) and Fujitsu Network Transmission Systems, Inc., have undertaken a major effort in the past three years to develop a methodology for OO .software testing and maintenance. The results we have obtained .so far include: 1) an OO test model and a reverse engineering approach to recovering the designs of C++ programs, 2) a three level .scherrra and algorithriis for data flow testing of OO pr'ograms, 3) definition and identification of class firewalls and a test strateg)' lor regression testing of C++ programs, 4) a program-based rrrethod for object state behavior testing, and .^i) a scenariobased method for integration and acceptance testing. Parts of these results have been implemented in an integrated object-oriented testing and maintenance (OOTM) environment.Currently, most software development or'ganizations are still in the process of observing and/or making the transition to the OO paradigm; only a few have experienced the difficirlties of testing and maintaining 75

One approach to testing concurrent programs is called reachability testing, which derives test sequences automatically and on‐the‐fly, without constructing a static model. Existing reachability testing algorithms are exhaustive in that they are intended to exercise all possible synchronization sequences of a concurrent program with a given input. In this paper, we present a new testing strategy, called t‐way reachability testing, that adopts the dynamic framework of reachability testing but selectively exercises a subset of synchronization sequences. The selection of the synchronization sequences is based on a combinatorial testing strategy called t‐way testing. We present an algorithm that implements t‐way reachability testing, and report the results of several case studies that were conducted to evaluate its effectiveness. The results indicate that t‐way reachability testing can substantially reduce the number of synchronization sequences exercised during reachability testing while still effectively detecting faults. Copyright © 2007 John Wiley & Sons, Ltd.

No abstract

In recent years, Web applications have grown rapidly because of their abilities to provide online information access to anyone at anytime around the world. As Web applications become complex, there is a growing concern about their quality and reliability. This paper extends traditional data flow testing techniques to Web applications. Several data flow issues about analyzing HyperText Markup Language (HTML) documents in Web applications are discussed. An object-based data flow testing approach is presented. The approach is based on a test model that captures data flow test artifacts of Web applications. In the test model, each entity of a Web application is modeled as an object. The data flow information of the functions within an object or across objects is then captured using various flow graphs. Based on the object-based test model, data flow test cases for a Web application can be systematically and selectively generated in five different levels.