Proceedings of the 33rd SIGCSE Technical Symposium on Computer Science Education 2002
DOI: 10.1145/563340.563429
|View full text |Cite
|
Sign up to set email alerts
|

Unit testing frameworks

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
3
0

Year Published

2006
2006
2011
2011

Publication Types

Select...
3
2
2

Relationship

1
6

Authors

Journals

citations
Cited by 17 publications
(3 citation statements)
references
References 2 publications
0
3
0
Order By: Relevance
“…It is our belief that senior-level students are not as capable in this area as desired. This belief is supported by anecdotal information from instructors here at the University of Alabama (UA) and by the literature [20,22]. As a result, the goal of this study is to gather some evidence about the testing ability of seniorlevel students.…”
Section: Goalsmentioning
confidence: 91%
See 1 more Smart Citation
“…It is our belief that senior-level students are not as capable in this area as desired. This belief is supported by anecdotal information from instructors here at the University of Alabama (UA) and by the literature [20,22]. As a result, the goal of this study is to gather some evidence about the testing ability of seniorlevel students.…”
Section: Goalsmentioning
confidence: 91%
“…Noonan and Prosi observed that an important side effect of requiring test case submissions was to increase the quality of students' source code (e.g., lower coupling between classes because higher coupling makes testing more difficult) [20]. In another approach, Goldwasser based a student's grade both on how many faults their test cases identified in the other students' code and on how many of the other students' test cases their own code passed.…”
Section: Approach 1: Students Learn To Test By Submitting Test Cases mentioning
confidence: 99%
“…Such testing could be entirely batch using test scripts, interactive, or a mixture of the two. Assessment may incorporate other checks including: plagiarism detection [1], unit testing [5], test coverage, comment assessment, and code metrics.…”
mentioning
confidence: 99%