Testing object-oriented programs: making it simple

Authors:
John Rosenberg;Michael Kölling
Affiliations:
Basser Department of Computer Science, University of Sydney, NSW 2006, Australia;Basser Department of Computer Science, University of Sydney, NSW 2006, Australia
Venue:
SIGCSE '97 Proceedings of the twenty-eighth SIGCSE technical symposium on Computer science education
Year:
1997

Citing 3
Cited 5

Requirements for a first year object-oriented teaching language

SIGCSE '95 Proceedings of the twenty-sixth SIGCSE technical symposium on Computer science education
An object-oriented program development environment for the first programming course

SIGCSE '96 Proceedings of the twenty-seventh SIGCSE technical symposium on Computer science education
Blue—a language for teaching object-oriented programming

SIGCSE '96 Proceedings of the twenty-seventh SIGCSE technical symposium on Computer science education

Java class visualization for teaching object-oriented concepts

SIGCSE '98 Proceedings of the twenty-ninth SIGCSE technical symposium on Computer science education
I/O considered harmful (at least for the first few weeks)

Proceedings of the 2nd Australasian conference on Computer science education
Evaluation of student attitudes to learning the Java language

PPPJ '02/IRE '02 Proceedings of the inaugural conference on the Principles and Practice of programming, 2002 and Proceedings of the second workshop on Intermediate representation engineering for virtual machines, 2002
Revealing the programming process

Proceedings of the 36th SIGCSE technical symposium on Computer science education
Experiences using test-driven development with an automated grader

Journal of Computing Sciences in Colleges

Quantified Score

Hi-index	0.00

Visualization

Abstract

One of the major difficulties facing anyone trying to teach the first programming course is how to encourage students to thoroughly test their programs. We would argue that the main reasons for this are the lack of suitable tools for testing and the need to write extra "debug" code in order to verify correct operation. We further argue that the problem is even worse with object-oriented languages because of multiple classes and encapsulation. In this paper we describe the testing tools within the Blue programming environment which allow object-oriented programs to be thoroughly tested without writing a single line of new code.