Scheduled System Maintenance on May 29th, 2015:
IEEE Xplore will be upgraded between 11:00 AM and 10:00 PM EDT. During this time there may be intermittent impact on performance. We apologize for any inconvenience.
By Topic

Practice and Research Techniques, 2008. TAIC PART '08. Testing: Academic & Industrial Conference

Date 29-31 Aug. 2008

Filter Results

Displaying Results 1 - 25 of 26
  • [Front cover]

    Publication Year: 2008 , Page(s): C1
    Save to Project icon | Request Permissions | PDF file iconPDF (211 KB)  
    Freely Available from IEEE
  • [Title page i]

    Publication Year: 2008 , Page(s): i
    Save to Project icon | Request Permissions | PDF file iconPDF (32 KB)  
    Freely Available from IEEE
  • [Title page iii]

    Publication Year: 2008 , Page(s): iii
    Save to Project icon | Request Permissions | PDF file iconPDF (78 KB)  
    Freely Available from IEEE
  • [Copyright notice]

    Publication Year: 2008 , Page(s): iv
    Save to Project icon | Request Permissions | PDF file iconPDF (93 KB)  
    Freely Available from IEEE
  • Table of contents

    Publication Year: 2008 , Page(s): v - vi
    Save to Project icon | Request Permissions | PDF file iconPDF (101 KB)  
    Freely Available from IEEE
  • Message from General Chair(s)

    Publication Year: 2008 , Page(s): vii - viii
    Save to Project icon | Request Permissions | PDF file iconPDF (115 KB) |  | HTML iconHTML  
    Freely Available from IEEE
  • Program Committee

    Publication Year: 2008 , Page(s): ix
    Save to Project icon | Request Permissions | PDF file iconPDF (55 KB)  
    Freely Available from IEEE
  • Invited Talk: The Role of Empiricism in Improving the Reliability of Future Software

    Publication Year: 2008 , Page(s): x
    Cited by:  Papers (1)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (113 KB) |  | HTML iconHTML  

    This talk first bemoan the general absence of empiricism in the evolution of software system building and then go on to show the results of some experiments in attempting to understand how defects appear in software, what factors affect their appearance and their relationship to testing generally. It challenge a few cherished beliefs on the way and demonstrate in no particular order at least the following: 1) the equilibrium state of a software system appears to conserve defect; 2) there is strong evidence in quasi-equilibrated systems for xlogx growth in defects where x is a measure of the lines of code; 3) component sizes in OO and non-OO software systems appear to be scale-free, (this is intimately related to the first two bullet points); 4) software measurements, (also known rather inaccurately as metrics) are effectively useless in determining the defect behaviour of a software system; 5) most such measurements, (including the ubiquitous cyclomatic complexity) are almost as highly correlated with lines of code as the relationship between temperature in degrees Fahrenheit and degrees Centigrade measured with a slightly noisy thermometer. In other words, lines of code are just about as good as anything else when estimating defects; 6) 'gotos considered irrelevant'. The goto statement has no obvious relationship with defects even when studied over very long periods. It probably never did; 7) checklists in code inspections appear to make no significant difference to the efficiency of the inspection; and 8) when you find a defect, there is an increasing probability of finding another in the same component. This strategy is effective up to a surprisingly large number of defects in youthful systems but not at all in elderly systems. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Invited Talk: Software Testing for the Home Entertainment Industry: We Know Where We Started, but Where is It Going?

    Publication Year: 2008 , Page(s): xi
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (113 KB)  

    This article is an invited talk regarding the software testing for home entertainment and multimedia. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Web Services Composition Testing: A Strategy Based on Structural Testing of Parallel Programs

    Publication Year: 2008 , Page(s): 3 - 12
    Cited by:  Papers (4)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (920 KB) |  | HTML iconHTML  

    Web Services have been used in the development of loosely coupled applications. Several Web Services are usually combined to create new services by a mechanism named Web Services Composition. In this paper, we present a strategy for Web Services Composition structural integration testing. Structural testing coverage criteria for services written in BPEL are also described. The concept of required element groups is defined to improve the accuracy of criteria coverage. We present a case study for assessing the applicability of proposed strategy. ValiBPEL-Web, a tool that supports the test strategy is also presented. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Exploring the Relationship of a File's History and Its Fault-Proneness: An Empirical Study

    Publication Year: 2008 , Page(s): 13 - 22
    Cited by:  Papers (1)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (364 KB) |  | HTML iconHTML  

    Knowing which particular characteristics of software are indicators for defects is very valuable for testers in order to allocate testing resources appropriately. In this paper, we present the results of an empirical study exploring the relationship between history characteristics of files and their defect count. We analyzed nine open source Java projects across different versions in order to answer the following questions: 1)Do past defects correlate with a filepsilas current defect count? 2) Do late changes correlate with a filepsilas defect count? 3) Is the file's age a good indicator for its defect count? The results are partly surprising. Only 4 of 9 programs show moderate correlation between a file's defects in previous and in current releases in more than the half of analysed releases. In contrast to our expectations, the oldest files represent the most fault-prone files. Additionally, late changes influence filepsilas defect count only partly. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Alternating GUI Test Generation and Execution

    Publication Year: 2008 , Page(s): 23 - 32
    Cited by:  Papers (5)  |  Patents (1)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (290 KB) |  | HTML iconHTML  

    Users of today's software perform tasks by interacting with a graphical user interface (GUI) front-end via sequences of input events. Due to the flexibility offered by most GUIs, the number of event sequences grows exponentially with length. One ubiquitous challenge of GUI testing is to selectively generate those sequences that lead to potentially problematic states. This paper presents ALT, a new technique that generates GUI test cases in batches, by leveraging GUI run-time information from a previously run batch to obtain the next batch. Each successive batch consists of "longer" test cases that expand the state space to be explored, yet prune the "unimportant" states. The "alternating" nature of ALT allows it to enhance the next batch by leveraging certain relationships between GUI events (e.g., one enables the other, one alters the other's execution) that are revealed only at run-time and non-trivial to infer statically. An empirical study on four fielded GUI-based applications demonstrates that ALT is successful at identifying complex failure-causing interactions between GUI events. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Testing Challenges of Maritime Safety and Security Systems-of-Systems

    Publication Year: 2008 , Page(s): 35 - 39
    Cited by:  Papers (4)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (127 KB) |  | HTML iconHTML  

    Maritime Safety and Security systems represent a novel kind of large-scale distributed component-based systems in which the individual components are elaborate and complex systems in their own right. Two distinguishing characteristics are their ability to evolve during runtime, that is, joining and leaving of components, and the need for high reliability of the system. In this paper, we identify the challenges that will have to be addressed, given the current state of the art in component-based software engineering in order to build such system-of-systems. In particular, we highlight the specific difficulties regarding acceptance and testing. A first group of testing challenges is raised by the need of accepting the integration of such large systems, and the ability to reconfigure them at runtime. A second group of testing challenges comes from the fact that, generally, not all the sub-systems are designed along the same kind of architecture (e.g. client-server vs. publish-subscribe architecture). Devising an integration testing process for such hybrid architecture is inherently harder than for a homogeneous one. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Test Axioms as Thinking Tools

    Publication Year: 2008 , Page(s): 40 - 44
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (242 KB) |  | HTML iconHTML  

    Is it possible to define a set of axioms that provide a framework for software testing that all the variations of test approach currently being advocated align with or obey? In this respect, an axiom would be an uncontested principle; something self-evidently and so obviously true and not requiring proof. What would such test axioms look like? This paper summarises some preliminary work on defining a set of Test Axioms. Some applications of the axioms that would appear useful are suggested for future development. It is also suggested the work of practitioners and researchers is on very shaky ground unless we refine and agree these Axioms. This is a work in progress. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Selection, Evaluation and Generation of Test Cases in an Industrial Setting: A Process and a Tool

    Publication Year: 2008 , Page(s): 47 - 51
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (318 KB) |  | HTML iconHTML  

    The test phase in safety-critical systems industry is a crucial phase of the development process. Some companies of these industries have their own test methods which do not reuse the notions available in the theory of software testing or model driven engineering. This paper reports on an experience in a testing process improvement made inside a safety-critical systems company in order to improve the quality of the test phase improvement. We present the initial situation, the objectives, the proposed process and the tools that are used to support it. In particular, we show that the most efficient improvements were achieved concerning the test process definition and in allowing a tailored and precise delimitation of the systempsilas elements to be tested. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Abandoning Proprietary Test Tools for Graphical User Interface Verification

    Publication Year: 2008 , Page(s): 52 - 56
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (129 KB) |  | HTML iconHTML  

    Graphical user interfaces have become an expected, and often desired, interface providing access to the functionality of a given piece of software. It is therefore necessary to place the interface through a series of verification and validation processes. The increased application of and reliance upon graphical user interfaces has corresponded with a perceived increase in interface complexity, and therefore, a paralleled increase in the complexity of the verification and validation process. To aid this process a commercial tool, with associated proprietary language, was selected. After some relatively successful regression runs we decided to re-evaluate this approach, and on examination, felt that a change had become necessary to continue parallel development of the test code and the interface itself. We detail the successful transition from a proprietary tool to a fully open source solution, taking advantage of the benefits offered by a general purpose programming language. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • ESTP: An Experimental Software Testing Platform

    Publication Year: 2008 , Page(s): 59 - 63
    Cited by:  Papers (3)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (185 KB) |  | HTML iconHTML  

    Most commercial software testing tools used in industry do not automatically generate test data even though many testing strategies have been proposed in academia. In this paper, we introduce a prototype software testing platform that we developed to automatically generate test data from tabular specifications. This method of documenting software specifications has been used successfully in industry to help produce reliable software. This platform can also be used to measure the effectiveness of new testing strategies. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Supporting Security Testers in Discovering Injection Flaws

    Publication Year: 2008 , Page(s): 64 - 68
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (673 KB) |  | HTML iconHTML  

    We present a platform for software security testing primarily designed to support human testers in discovering injection flaws in distributed systems. Injection is an important class of security faults, caused by unsafe concatenation of input into strings interpreted by other components of the system. Examples include two of the most common security issues in Web applications, SQL injection and cross site scripting. This paper briefly discusses the fault model, derives a testing strategy that should discover a large subset of the injection flaws present, and describes a platform that helps security testers to discover injection flaws through dynamic grey-box testing. Our platform combines the respective strengths of machines and humans, automating what is easily automated while leaving to the tester the artistic portion of security testing. Although designed with a specific fault model in mind, our platform may be useful in a wide range of security testing tasks. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Feedback-Based Specification, Coding and Testing with JWalk

    Publication Year: 2008 , Page(s): 69 - 73
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (405 KB) |  | HTML iconHTML  

    JWalk is a lazy systematic unit-testing tool for Java, which supports dynamic inference of specifications from code and systematic testing from the acquired specification. This paper describes the feedback-based development methodology that is possible using the JWalk Editor, an original Java-sensitive editor and compiler coupled to JWalk, which helps programmers to prototype Java class designs, generating novel test cases as they code. Systematic exploratory testing alerts the programmer to unusual consequences in the design; and confirmed test results become part of the evolving specification, which adapts continuously to modified classes and extends to subclasses. The cycle of coding, inferring and testing systematically exposes test cases that are often missed in other test-driven development approaches, which rely on programmer intuition to create test cases. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Improving Fault Injection of Soft Errors Using Program Dependencies

    Publication Year: 2008 , Page(s): 77 - 81
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (291 KB) |  | HTML iconHTML  

    Research has shown that modern micro-architectures are vulnerable to soft errors, i.e., temporary errors caused by voltage spikes produced by cosmic radiation. Soft-error impact is usually evaluated using fault injection, a black-box testing approach similar to mutation testing. In this paper, we complement an existing evaluation of a prototype brake-by-wire controller, developed by Volvo Technology, with static-analysis techniques to improve test effectiveness. The fault-injection tests are both time- and data-intensive, which renders their qualitative and quantitative assessment difficult. We devise a prototype visualization tool, which groups experiments by injection point and provides an overview of both instruction and fault coverage, and the ability to detect patterns and anomalies. We use the program-dependence graph to identify experiments with a priori known outcome, and implement a static analysis to reduce the test volume. The existing pre-injection heuristic is extended with liveness analysis to enable an unbiased fault-to-failure probability. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Enhancing Test Driven Development with Model Based Testing and Performance Analysis

    Publication Year: 2008 , Page(s): 82 - 86
    Cited by:  Papers (1)  |  Patents (1)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (249 KB) |  | HTML iconHTML  

    This paper suggests a holistic design and development method combining test-driven and model-driven development for SOA architectures. It uses test-driven development on component level and model-based testing on system level. Moreover, monitored performance parameters during test execution serve as input for a model-driven performance analysis of the business application, providing early indication of possible performance issues. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • WebVizOr: A Visualization Tool for Applying Automated Oracles and Analyzing Test Results of Web Applications

    Publication Year: 2008 , Page(s): 89 - 93
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (436 KB) |  | HTML iconHTML  

    Web applications are used extensively for a variety of critical purposes and, therefore, must be reliable. Since Web applications often contain large amounts of code and frequently undergo maintenance, testers need automated tools to execute large numbers of test cases to determine if an application is behaving correctly. Evaluating the voluminous output-typically Web pages full of content-is tedious and error-prone. To ease the difficulty, testers can apply automated oracles, which have tradeoffs in false positives and false negatives. In this paper, we present the design, implementation, and evaluation of WebVizOr, a tool that aids testers byapplying a set of oracles to the output from test cases and highlighting the symptoms of possible faults. Using WebVizOr, a tester can compare the test results from several executions of a test case and can more easily determine if a test case exposes a fault. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • MILU: A Customizable, Runtime-Optimized Higher Order Mutation Testing Tool for the Full C Language

    Publication Year: 2008 , Page(s): 94 - 98
    Cited by:  Papers (21)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (209 KB) |  | HTML iconHTML  

    This paper introduces MILU, a C mutation testing tool designed for both first order and higher order mutation testing. All previous mutation testing tools apply all possible mutation operators to the program under test. By contrast, MILU allows customization of the set of mutation operators to be applied. To reduce runtime cost, MILU uses a novel 'test harness' technique to embed mutants and their associated test sets into a single-invocation procedure. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • GUI Testing Made Easy

    Publication Year: 2008 , Page(s): 99 - 103
    Cited by:  Papers (3)
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (230 KB) |  | HTML iconHTML  

    Despite its importance, testing graphical user interfaces (GUIs) is frequently seen as a difficult activity. The challenges present in GUI testing may discourage developers and testers, to the point that they may eventually stop writing tests. This paper describes the common problems that make creation and maintenance of GUI tests complex. Our intention is to present a GUI testing strategy that includes writing robust GUI tests, creating testable GUIs and testing legacy/existing GUIs. Simultaneously, we discuss the features that a tool should offer to simplify GUI testing. We cover the intricacies that developers and testers face when writing, maintaining and troubleshooting GUI tests, and offer practical solutions to each of them.The ideas explained in this paper have been successfully implemented in the open source project FEST, a GUI testing library for Java Swing GUIs. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Author index

    Publication Year: 2008 , Page(s): 104
    Save to Project icon | Request Permissions | PDF file iconPDF (57 KB)  
    Freely Available from IEEE