Test Driven Development for Embedded C

Subtitle

Why Debug? Use Test Driven Development!

Takeaways

Attendees learn how to avoid bugs and build code that can stand the test of time. Attendees experience TDD and see how to apply it in the challenging environment of embedded C.

Prerequisites

C programming experience. Attendees bring a laptop computer; one for every two attendees. Attendees without a laptop, no worries, someone will be happy to pair with you. See http://renaissancesoftware.net/esc/ for setup instructions.

Abstract

Test-Driven Development helps software developers improve product quality and schedule predictability. How? By eliminating bugs before they make the bug list or disrupt the plan. Too much code goes into products without adequate testing. Software is fragile; make a change, it works; you don't even realize that some formerly working feature is not broken. This class describes the problems addressed by TDD, as well as the additional challenges and benefits of applying TDD to embedded software.

This class is not just a show and tell. The second half of this session is hands-on, so bring your laptop. See http://renaissancesoftware.net/esc/ for setup information.

Revised for hands on

Test-Driven Development helps software developers improve schedule predictability and product quality. How? By eliminating bugs before they make the bug list or disrupt the plan. This class describes the problems addressed by TDD, as well as the additional challenges and benefits of applying TDD to embedded software. This class is not just a show and tell. The second half of this session is hands-on, so bring your laptop. See http://renaissancesoftware.net/esc/ for setup information.

Too much code goes into products without adequate testing. This class shows how to get code tested, and keep bugs out. But, TDD is more than a bug prevention technique, it helps steer the design so developers can avoid the mess that often happens as a system evolves. Attendees will see valuable lessons for doing TDD in the hostile environment of embedded C.

Wednesday (November 20th, Workshop day) - 09:00 - 11:45 on Embedded, Agile / PC

About the speakers

James Grenning

James -grenning James Grenning’s trains, coaches and consults worldwide. With more than thirty years of software development experience, both technical and managerial, James brings knowledge, skill, and creativity to software development teams and their management.

As his professional roots are in embedded software, James’ mission is to bring state-of-the-art technical and management practices to embedded development teams.

He is the author of Test-Driven Development for Embedded C.

He invented Planning Poker, an estimating technique used around the world, and participated in the creation of the Manifesto for Agile Software Development.

Blog: http://www.renaissancesoftware.net/blog/

Website: www.renaissancesoftware.net

Twitter: @jwgrenning

Story testing paper: http://bit.ly/story_testing

Mike Long

Mikelong Mike Long is a software architect currently working on improving development practices in large scale software development teams, based in Beijing, China. His previous experience working with embedded systems development in Norway and England have instilled a great passion for test driven development, code craft, and avoiding oscilloscope debugging as much as humanly possible.