TU Darmstadt / ULB / TUbiblio

Automatic testing of sequential and concurrent substitutability

Pradel, Michael ; Gross, Thomas R. (2013)
Automatic testing of sequential and concurrent substitutability.
San Francisco, CA, USA
doi: 10.1109/ICSE.2013.6606574
Conference or Workshop Item, Bibliographie

Abstract

Languages with inheritance and polymorphism assume that a subclass instance can substitute a superclass instance without causing behavioral differences for clients of the superclass. However, programmers may accidentally create subclasses that are semantically incompatible with their superclasses. Such subclasses lead to bugs, because a programmer may assign a subclass instance to a superclass reference. This paper presents an automatic testing technique to reveal subclasses that cannot safely substitute their superclasses. The key idea is to generate generic tests that analyze the behavior of both the subclass and its superclass. If using the subclass leads to behavior that cannot occur with the superclass, the analysis reports a warning. We find a high percentage of widely used Java classes, including classes from JBoss, Eclipse, and Apache Commons Collections, to be unsafe substitutes for their superclasses: 30% of these classes lead to crashes, and even more have other behavioral differences.

Item Type: Conference or Workshop Item
Erschienen: 2013
Creators: Pradel, Michael ; Gross, Thomas R.
Type of entry: Bibliographie
Title: Automatic testing of sequential and concurrent substitutability
Language: German
Date: May 2013
Publisher: IEEE Press
Book Title: Proceedings of the 2013 International Conference on Software Engineering
Series: ICSE '13
Event Location: San Francisco, CA, USA
DOI: 10.1109/ICSE.2013.6606574
Abstract:

Languages with inheritance and polymorphism assume that a subclass instance can substitute a superclass instance without causing behavioral differences for clients of the superclass. However, programmers may accidentally create subclasses that are semantically incompatible with their superclasses. Such subclasses lead to bugs, because a programmer may assign a subclass instance to a superclass reference. This paper presents an automatic testing technique to reveal subclasses that cannot safely substitute their superclasses. The key idea is to generate generic tests that analyze the behavior of both the subclass and its superclass. If using the subclass leads to behavior that cannot occur with the superclass, the analysis reports a warning. We find a high percentage of widely used Java classes, including classes from JBoss, Eclipse, and Apache Commons Collections, to be unsafe substitutes for their superclasses: 30% of these classes lead to crashes, and even more have other behavioral differences.

Uncontrolled Keywords: Generators, Runtime, Computer bugs, Java, Programming, Libraries
Identification Number: TUD-CS-2013-0482
Divisions: Profile Areas > Cybersecurity (CYSEC)
Profile Areas
Date Deposited: 28 Aug 2017 12:58
Last Modified: 15 May 2018 10:33
PPN:
Export:
Suche nach Titel in: TUfind oder in Google
Send an inquiry Send an inquiry

Options (only for editors)
Show editorial Details Show editorial Details