Peer testing in Software Engineering Projects

For the last six years, students in the Software Engineering Project course at the University of Tasmania have undertaken projects in teams of four or five members. Since 1998 peer testing sessions have been conducted in two different formats: paired peer code reviews and group peer inspections. The critique that the testers perform can help the development team to identify problems before assessment hence increasing the quality of the work submitted. The peer testing sessions also provide many different, but valuable, benefits such as serving as milestones, increasing learning, and increasing collaboration between students in different teams.

[1]  Michael E. Fagan Design and Code Inspections to Reduce Errors in Program Development (Reprint) , 2002, Software Pioneers.

[2]  Thomas B. Hilburn,et al.  Inspections of formal specifications , 1996, SIGCSE '96.

[3]  Mark Guzdial,et al.  Introducing testing practices into objects and design course , 2003, Proceedings 16th Conference on Software Engineering Education and Training, 2003. (CSEE&T 2003)..

[4]  Gerald M. Weinberg,et al.  Reviews, Walkthroughs, and Inspections , 1984, IEEE Transactions on Software Engineering.

[5]  Sarah L. Sullivan Reciprocal peer reviews , 1994, SIGCSE '94.

[6]  Brian Hanks,et al.  Can we influence students' attitudes about inspections? Can we measure a change in attitude? , 2003, Proceedings 16th Conference on Software Engineering Education and Training, 2003. (CSEE&T 2003)..

[7]  Watts S. Humphrey,et al.  Introduction to the Personal Software Process , 1996 .

[8]  Nancy J. Wahl Student-run usability testing , 2000, Thirteenth Conference on Software Engineering Education and Training.

[9]  Andreas Zeller,et al.  Making students read and review code , 2000, ITiCSE '00.

[10]  James S. Collofello Teaching technical reviews in a one-semester software engineering course , 1987, SIGCSE.