SIGCSE '94 Proceedings of the twenty-fifth SIGCSE symposium on Computer science education
SIGCSE '97 Proceedings of the twenty-eighth SIGCSE technical symposium on Computer science education
Software quality: a curriculum postscript?
Proceedings of the thirty-first SIGCSE technical symposium on Computer science education
Software engineering education: a roadmap
Proceedings of the Conference on The Future of Software Engineering
Integrating testing into the curriculum — arsenic in small doses
Proceedings of the thirty-second SIGCSE technical symposium on Computer Science Education
Communications of the ACM
A gimmick to integrate software testing throughout the curriculum
SIGCSE '02 Proceedings of the 33rd SIGCSE technical symposium on Computer science education
Rethinking computer science education from a test-first perspective
OOPSLA '03 Companion of the 18th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Introducing unit testing with BlueJ
Proceedings of the 8th annual conference on Innovation and technology in computer science education
Using software testing to move students from trial-and-error to reflection-in-action
Proceedings of the 35th SIGCSE technical symposium on Computer science education
Testing first: emphasizing testing in early programming courses
ITiCSE '05 Proceedings of the 10th annual SIGCSE conference on Innovation and technology in computer science education
Test-driven learning: intrinsic integration of testing into the CS/SE curriculum
Proceedings of the 37th SIGCSE technical symposium on Computer science education
Designing an adaptive learning module to teach software testing
Proceedings of the 37th SIGCSE technical symposium on Computer science education
An experiential approach to incorporating software testing into the computer science curriculum
FIE '01 Proceedings of the Frontiers in Education Conference, 2001. 31st Annual - Volume 02
Computer Engineering 2004: Curriculum Guidelines for Undergraduate Degree Programs in Computer Engineering
Mutation analysis vs. code coverage in automated assessment of students' testing skills
Proceedings of the ACM international conference companion on Object oriented programming systems languages and applications companion
Using a web-based repository to integrate testing tools into programming courses
Proceedings of the ACM international conference companion on Object oriented programming systems languages and applications companion
Secret ninja testing with HALO software engineering
Proceedings of the 4th international workshop on Social software engineering
Bug Wars: a competitive exercise to find bugs in code
Journal of Computing Sciences in Colleges
Running students' software tests against each others' code: new life for an old "gimmick"
Proceedings of the 43rd ACM technical symposium on Computer Science Education
An empirical study of programming bugs in CS1, CS2, and CS3 homework submissions
Journal of Computing Sciences in Colleges
Bug catcher: a system for software testing competitions
Proceeding of the 44th ACM technical symposium on Computer science education
Using a real world project in a software testing course
Proceedings of the 45th ACM technical symposium on Computer science education
Hi-index | 0.00 |
Software testing efforts account for a large part of software development costs. However, as educators, we struggle to properly prepare students to perform software testing activities. This struggle is caused by multiple factors: 1) it is challenging to effectively incorporate software testing into an already over-packed curriculum, 2) ad-hoc efforts to teach testing generally happen too late in the students' career, after bad habits have already been developed, and 3) these efforts lack the necessary institutional consistency and support to be effective. To address these challenges we created Bug Hunt, a web-based tutorial to engage students in learning software testing strategies. In this paper we describe the most interesting aspects of the tutorial including the lessons and feedback mechanisms, and the facilities for instructors to configure the tutorial and obtain automatic student assessment. We also present the lessons learned after two years of deployment.