Testing object-oriented programs

Subscribe (Full Service)


	Search: The ACM Digital Library The Guide

	Feedback

Testing object-oriented programs: making it simple

Full text

Pdf (610 KB)

Source

Technical Symposium on Computer Science Education archive
Proceedings of the twenty-eighth SIGCSE technical symposium on Computer science education table of contents

San Jose, California, United States

Pages: 77 - 81

Year of Publication: 1997

ISBN:0-89791-889-4

Also published in ...

Authors

John Rosenberg	Basser Department of Computer Science, University of Sydney, NSW 2006, Australia
Michael Kölling	Basser Department of Computer Science, University of Sydney, NSW 2006, Australia

Sponsor

SIGCSE: ACM Special Interest Group on Computer Science Education

Publisher

ACM New York, NY, USA

Bibliometrics

Downloads (6 Weeks): 6, Downloads (12 Months): 17, Citation Count: 5

Additional Information:

abstract references cited by index terms collaborative colleagues

Tools and Actions:	Request Permissions Review this Article Save this Article to a Binder Display Formats: BibTeX EndNote ACM Ref

DOI Bookmark:	Use this link to bookmark this Article: http://doi.acm.org/10.1145/268084.268115 What is a DOI?

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.

REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

	1	Michael Kölling , Bett Koch , John Rosenberg, Requirements for a first year object-oriented teaching language, ACM SIGCSE Bulletin, v.27 n.1, p.173-177, March 1995
	2	Michael Kölling , John Rosenberg, Blue—a language for teaching object-oriented programming, Proceedings of the twenty-seventh SIGCSE technical symposium on Computer science education, p.190-194, February 15-17, 1996, Philadelphia, Pennsylvania, United States
	3	Michael Kölling , John Rosenberg, An object-oriented program development environment for the first programming course, Proceedings of the twenty-seventh SIGCSE technical symposium on Computer science education, p.83-87, February 15-17, 1996, Philadelphia, Pennsylvania, United States

CITED BY 5

	John Rosenberg , Michael Kölling, I/O considered harmful (at least for the first few weeks), Proceedings of the 2nd Australasian conference on Computer science education, p.216-223, July 1997, The Univ. of Melbourne, Australia
	Herbert L. Dershem , James Vanderhyde, Java class visualization for teaching object-oriented concepts, ACM SIGCSE Bulletin, v.30 n.1, p.53-57, Mar. 1998
	Michael Madden , Desmond Chambers, Evaluation of student attitudes to learning the Java language, 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, June 13-14, 2002, Dublin, Ireland
	Jens Bennedsen , Michael E. Caspersen, Revealing the programming process, ACM SIGCSE Bulletin, v.37 n.1, 2005
	Stephen H. Edwards , Manuel A. Pérez-Quiñones, Experiences using test-driven development with an automated grader, Journal of Computing Sciences in Colleges, v.22 n.3, p.44-50, January 2007