Test Driven Development: By Example
Test Driven Development: By Example
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
Agile Methods Applied to Embedded Firmware Development
ADC '04 Proceedings of the Agile Development Conference
Fit for Developing Software: Framework for Integrated Tests (Robert C. Martin)
Fit for Developing Software: Framework for Integrated Tests (Robert C. Martin)
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
E-TDD – embedded test driven development a tool for hardware-software co-design projects
XP'05 Proceedings of the 6th international conference on Extreme Programming and Agile Processes in Software Engineering
Making fit / fitnesse appropriate for biomedical engineering research
XP'06 Proceedings of the 7th international conference on Extreme Programming and Agile Processes in Software Engineering
An experimental laboratory environment for teaching embedded operating systems
Proceedings of the 39th SIGCSE technical symposium on Computer science education
Nexos: a next generation embedded systems laboratory
ACM SIGBED Review
A novel embedded system curriculum with portable hands-on labs in a box
Proceedings of the 48th Annual Southeast Regional Conference
| Hi-index | 0.00 |
Learning embedded programming is a highly demanding exercise. The beginner is bombarded with complexity from the start: embedded production based around a myriad of C++ constructs with low-level elements integrated onto ever more complicated processor architectures. The picture is further compounded by tool support having unfamiliar roles and appearances from previous student experiences. This demanding situation often has the student bewildered; seeking for "a crutch" or the simplest way forward regardless of the overall consequences. To control this potentially chaotic picture, the instructor needs to introduce devices to combat this complexity. We argue that test driven development (TDD) should become the instructor's principal weapon in this fight. Reasons for this belief combined with our, and the students', experiences with this novel approach are discussed.