Test Driven Development for Embedded C

Table of contents

1. Foreword by Jack Ganssle
2. Foreword by Robert C. Martin
3. Acknowledgments
4. Preface
   1. Who Is This Book For?
   2. How to Read This Book
   3. The Code in This Book
   4. Online Resources
5. Chapter 1: Test-Driven Development
   1. Why Do We Need TDD?
   2. What Is Test-Driven Development?
   3. Physics of TDD
   4. The TDD Microcycle
   5. TDD Benefits
   6. Benefits for Embedded
6. Part I. Getting Started
   1. Chapter 2: Test-Driving Tools and Conventions
      1. What Is a Unit Test Harness?
      2. Unity: A C-Only Test Harness
      3. CppUTest: A C++ Unit Test Harness
      4. Unit Tests Can Crash
      5. The Four-Phase Test Pattern
      6. Where Are We?
      7. Put the Knowledge to Work
   2. Chapter 3: Starting a C Module
      1. Elements of a Testable C Module
      2. What Does an LED Driver Do?
      3. Write a Test List
      4. Writing the First Test
      5. Test-Drive the Interface Before the Internals
      6. Incremental Progress
      7. Test-Driven Developer State Machine
      8. Tests Are FIRST
      9. Where Are We?
      10. Put the Knowledge to Work
   3. Chapter 4: Testing Your Way to Done
      1. Grow the Solution from Simple Beginnings
      2. Keep the Code Clean—Refactor as You Go
      3. Repeat Until Done
      4. Take a Step Back Before Claiming Done
      5. Where Are We?
      6. Put the Knowledge to Work
   4. Chapter 5: Embedded TDD Strategy
      1. The Target Hardware Bottleneck
      2. Benefits of Dual-Targeting
      3. Risks of Dual-Target Testing
      4. The Embedded TDD Cycle
      5. Dual-Target Incompatibilities
      6. Testing with Hardware
      7. Slow Down to Go Fast
      8. Where Are We?
      9. Put the Knowledge to Work
   5. Chapter 6: Yeah, but...
      1. We Don’t Have Time
      2. Why Not Write Tests After the Code?
      3. We’ll Have to Maintain the Tests
      4. Unit Tests Don’t Find All the Bugs
      5. We Have a Long Build Time
      6. We Have Existing Code
      7. We Have Constrained Memory
      8. We Have to Interact with Hardware
      9. Why a C++ Test Harness for Testing C?
      10. Where Are We?
      11. Put the Knowledge to Work
7. Part II. Testing Modules with Collaborators
   1. Chapter 7: Introducing Test Doubles
      1. Collaborators
      2. Breaking Dependencies
      3. When to Use a Test Double
      4. Faking It in C, What’s Next
      5. Where Are We?
      6. Put the Knowledge to Work
   2. Chapter 8: Spying on the Production Code
      1. Light Scheduler Test List
      2. Dependencies on Hardware and OS
      3. Link-Time Substitution
      4. Spying on the Code Under Test
      5. Controlling the Clock
      6. Make It Work for None, Then One
      7. Make It Work for Many
      8. Where Are We?
      9. Put the Knowledge to Work
   3. Chapter 9: Runtime-Bound Test Doubles
      1. Testing Randomness
      2. Faking with a Function Pointer
      3. Surgically Inserted Spy
      4. Verifying Output with a Spy
      5. Where Are We?
      6. Put the Knowledge to Work
   4. Chapter 10: The Mock Object
      1. Flash Driver
      2. MockIO
      3. Test-Driving the Driver
      4. Simulating a Device Timeout
      5. Is It Worth It?
      6. Mocking with CppUMock
      7. Generating Mocks
      8. Where Are We?
      9. Put the Knowledge to Work
8. Part III. Design and Continuous Improvement
   1. Chapter 11: SOLID, Flexible, and Testable Designs
      1. SOLID Design Principles
      2. SOLID C Design Models
      3. Evolving Requirements and a Problem Design
      4. Improving the Design with Dynamic Interface
      5. More Flexibility with Per-Type Dynamic Interface
      6. How Much Design Is Enough?
      7. Where Are We?
      8. Put the Knowledge to Work
   2. Chapter 12: Refactoring
      1. Two Values of Software
      2. Three Critical Skills
      3. Code Smells and How to Improve Them
      4. Transforming the Code
      5. But What About Performance and Size?
      6. Where Are We?
      7. Put the Knowledge to Work
   3. Chapter 13: Adding Tests to Legacy Code
      1. Legacy Code Change Policy
      2. Boy Scout Principle
      3. Legacy Change Algorithm
      4. Test Points
      5. Two-Stage struct Initialization
      6. Crash to Pass
      7. Characterization Tests
      8. Learning Tests for Third-Party Code
      9. Test-Driven Bug Fixes
      10. Add Strategic Tests
      11. Where Are We?
      12. Put the Knowledge to Work
   4. Chapter 14: Test Patterns and Antipatterns
      1. Ramble-on Test Antipattern
      2. Copy-Paste-Tweak-Repeat Antipattern
      3. Sore Thumb Test Cases Antipattern
      4. Duplication Between Test Groups Antipattern
      5. Test Disrespect Antipattern
      6. Behavior-Driven Development Test Pattern
      7. Where Are We?
      8. Put the Knowledge to Work
   5. Chapter 15: Closing Thoughts
9. Part IV. Appendixes
   1. Appendix 1: Development System Test Environment
      1. Development System Tool Chain
      2. Full Test Build makefile
      3. Smaller Test Builds
   2. Appendix 2: Unity Quick Reference
      1. Unity Test File
      2. Unity Test main
      3. Unity TEST Condition Checks
      4. Command-Line Options
      5. Unity in Your Target
   3. Appendix 3: CppUTest Quick Reference
      1. The CppUTest Test File
      2. Test Main
      3. TEST Condition Checks
      4. Test Execution Order
      5. Scripts to Create Starter Files
      6. CppUTest in Your Target
      7. Convert CppUTest Tests to Unity
   4. Appendix 4: LedDriver After Getting Started
      1. LedDriver First Few Tests in Unity
      2. LedDriver First Few Tests in CppUTest
      3. LedDriver Early Interface
      4. LedDriver Skeletal Implementation
   5. Appendix 5: Example OS Isolation Layer
      1. Test Cases to Assure Substitutable Behavior
      2. POSIX Implementation
      3. Micrium RTOS Implementation
      4. Win32 Implementation
      5. Burden the Layer, Not the Application
   6. Appendix 6: Bibliography
10. You May Be Interested In...