Identifying opaque behavioural changes

Authors:
Reid Holmes;David Notkin
Affiliations:
University of Waterloo, Waterloo, ON, Canada;University of Washington, Seattle, WA, USA
Venue:
Proceedings of the 33rd International Conference on Software Engineering
Year:
2011

Citing 8
Cited 0

Smalltalk-80: the language and its implementation

Smalltalk-80: the language and its implementation
Adding implicit invocation to traditional programming languages

ICSE '93 Proceedings of the 15th international conference on Software Engineering
Letters to the editor: go to statement considered harmful

Communications of the ACM
Structured exception handling

POPL '75 Proceedings of the 2nd ACM SIGACT-SIGPLAN symposium on Principles of programming languages
Reducing Coupling

IEEE Software
Influences on the design of exception handling: ACM SIGSOFT project on the impact of software engineering research on programming language design

ACM SIGPLAN Notices
Structured programming

Structured programming
Identifying program, test, and environmental changes that affect behaviour

Proceedings of the 33rd International Conference on Software Engineering

Quantified Score

Hi-index	0.00

Visualization

Abstract

Developers modify their systems by changing source code, updating test suites, and altering their system's execution context. When they make these modifications, they have an understanding of the behavioural changes they expect to happen when the system is executed; when the system does not conform to their expectations, developers try to ensure their modification did not introduce some unexpected or undesirable behavioural change. We present an approach that integrates with existing continuous integration systems to help developers identify situations whereby their changes may have introduced unexpected behavioural consequences. In this research demonstration, we show how our approach can help developers identify and investigate unanticipated behavioural changes.