ACM Home Page
Please provide us with feedback. Feedback
Improving student performance by evaluating how well students test their own programs
Full text PdfPdf (348 KB)
Source Journal on Educational Resources in Computing (JERIC) archive
Volume 3 ,  Issue 3  (September 2003) table of contents
Article No. 1  
Year of Publication: 2003
ISSN:1531-4278
Author
Stephen H. Edwards  Virginia Tech
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 30,   Downloads (12 Months): 210,   Citation Count: 10
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: 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/1029994.1029995
What is a DOI?

ABSTRACT

Students need to learn more software testing skills. This paper presents an approach to teaching software testing in a way that will encourage students to practice testing skills in many classes and give them concrete feedback on their testing performance, without requiring a new course, any new faculty resources, or a significant number of lecture hours in each course where testing will be practiced. The strategy is to give students basic exposure to test-driven development, and then provide an automated tool that will assess student submissions on-demand and provide feedback for improvement. This approach has been demonstrated in an undergraduate programming languages course using a prototype tool. The results have been positive, with students expressing appreciation for the practical benefits of test-driven development on programming assignments. Experimental analysis of student programs shows a 28% reduction in defects per thousand lines of 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
 
2
 
3
Bagert, D., Hilburn, T., Hislop, G., Lutz, M., Mccracken, M., and Mengel, S. 1999. Guidelines for Software Engineering Education Version 1.0, Technical Report CMU/SEI-99-TR-032, Software Engineering Institute, Pittsburg, PA.
 
4
 
5
 
6
 
7
Boehm, B. 1976. Software engineering. IEEE Transactions on Computers, C-25, 12, 1226-1241.
 
8
Bourque, P., Dupuis, R., Abran, A., and Moore, J.W., eds. 2001. Guide to the Software Engineering Body of Knowledge--Stone Man Trial Version 1.00, IEEE Computer Society, Washington, available at: <http:/www.swebok.org>.
9
 
10
Checkstyle. 2003. Checkstyle home page. Web page last accessed Mar. 21, 2003. <http://checkstyle.sourceforge.net/>.
 
11
Cortex, Inc. 2003. Clover: a code coverage tool for Java. Web page accessed Mar. 21, 2003. <http://www.thecortex.net/clover/>.
12
13
14
15
 
16
17
18
 
19
Jones, E.L 2000b. SPRAE: A framework for teaching software testing in the undergraduate curriculum. In Proc. ADMI 2000, Hampton, VA, 1-4 June 2000.
20
 
21
Jones, E.L. 2001b. An experiential approach to incorporating software testing into the computer science curriculum. In Proc. 2001 Frontiers in Education Conf. (FiE 2001), F3D7-F3D11.
 
22
 
23
JUnit. 2003. JUnit home page. Web page last accessed Mar. 21, 2003. <http://www.junit.org/>.
 
24
25
26
27
 
28
McQuain, W. 2003. Curator: An electronic submission management environment. Web page last accessed July 24, 2003. <http://www.cs.vt.edu/curator/>.
29
 
30
PMD. 2003. PMD home page. Web page last accessed Mar. 21, 2003. <http://pmd.sourceforge.net/>.
31
 
32
Ricadela, A. 2001. The state of software: Quality. InformationWeek, 838, 43, May 21, 2001.
33
34
 
35

CITED BY  10