2009
DOI: 10.1145/1539024.1508921
|View full text |Cite
|
Sign up to set email alerts
|

Implications of integrating test-driven development into CS1/CS2 curricula

Abstract: Many academic and industry professionals have called for more testing in computer science curricula. Test-driven development (TDD) has been proposed as a solution to improve testing in academia. This paper demonstrates how TDD can be integrated into existing course materials without reducing topic coverage. Two controlled experiments were conducted in a CS1/CS2 course in Winter 2008. Following a test-driven learning approach, unit testing was introduced at the beginning of the course and reinforced through exa… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
14
0

Year Published

2010
2010
2024
2024

Publication Types

Select...
4
3
2

Relationship

0
9

Authors

Journals

citations
Cited by 29 publications
(14 citation statements)
references
References 10 publications
0
14
0
Order By: Relevance
“…2 the values next to each study under the column "Point" show the Hedges g summary effect size if the respective study is excluded from the synthesis process. Comparing the values in this column with the overall value in the last row, it can be seen that the [50] and Gupta and Jalote E1 [47]. Therefore, the analysis is most sensitive to, or is most effected by, the inclusion of these two experiments.…”
Section: Standardized Analysismentioning
confidence: 98%
“…2 the values next to each study under the column "Point" show the Hedges g summary effect size if the respective study is excluded from the synthesis process. Comparing the values in this column with the overall value in the last row, it can be seen that the [50] and Gupta and Jalote E1 [47]. Therefore, the analysis is most sensitive to, or is most effected by, the inclusion of these two experiments.…”
Section: Standardized Analysismentioning
confidence: 98%
“…Furthermore, they evaluated the effect of grading the test cases by comparing students whose test cases were graded to those students whose test cases were not graded. As the programming projects increased in difficulty, the code coverage decreased both for the graded test group and for the ungraded test group, although the graded test group did obtain more coverage (65% vs. ~30% on the most difficult project) [7]. In an introductory programming course, Marrero and Settle used TDD by requiring students to submit tests before submitting code.…”
Section: Approach 4: Students Learn To Test Through Use Of Test-drivementioning
confidence: 99%
“…Because of the necessity of testing, more educators are including software testing [1,2] in programming and software engineering courses [3,4]. Current classroom assessment systems (e.g.,Web-CAT, ASSYST, Marmoset) use code coverage to evaluate how well students test their own code.…”
Section: Introductionmentioning
confidence: 99%