Modern C++ Programming with Test-Driven Development: Code Better, Sleep Better

About this Book

Modern C++ Programming With Test-Driven Development, the only comprehensive treatment on TDD in C++ provides you with everything you need to know about TDD, and the challenges and benefits of implementing it in your C++ systems. Its many detailed code examples take you step-by-step from TDD basics to advanced concepts. As a veteran C++ programmer, you’re already writing high-quality code, and you work hard to maintain code quality. It doesn’t have to be that hard.

In this book, you’ll learn:

• how to use TDD to improve legacy C++ systems
• how to identify and deal with troublesome system dependencies
• how to do dependency injection, which is particularly tricky in C++
• how to use testing tools for C++ that aid TDD
• new C++11 features that facilitate TDD

As you grow in TDD mastery, you’ll discover how to keep a massive C++ system from becoming a design mess over time, as well as particular C++ trouble spots to avoid. You’ll find out how to prevent your tests from being a maintenance burden and how to think in TDD without giving up your hard-won C++ skills. Finally, you’ll see how to grow and sustain TDD in your team.

Whether you’re a complete unit-testing novice or an experienced tester, this book will lead you to mastery of test-driven development in C++.

What You Need

• A C++ compiler running under Windows or Linux, preferably one that supports C++11. Examples presented in the book were built under gcc 4.7.2.
• Google Mock 1.6 (downloadable for free; it contains Google Test as well) or an alternate C++ unit testing tool. Most examples in the book are written for Google Mock, but it isn’t difficult to translate them to your tool of choice.
• A good programmer’s editor or IDE.
• cmake, preferably. Of course, you can use your own preferred make too. CMakeLists.txt files are provided for each project. Examples provided were built using cmake version 2.8.9.
• Various freely-available third-party libraries are used as the basis for examples in the book. These include: – cURL – JsonCpp – Boost (filesystem, date_time/gregorian, algorithm, assign) Several examples use the boost headers/libraries. Only one example uses cURL and JsonCpp.

Contents and Extracts

This book is currently in beta, so the contents and extracts will change as the book is developed.

• Introduction
  • But Can It Work for Me On My System?
  • Who This Book is For
  • What You’ll Need
  • How to Use this Book
  • About “Us”
  • About Me
  • About the C++ Style in this Book
• Global Setup
• Test-Driven Development: A First Example excerpt
  • Set Up
  • The Soundex Class
  • Getting Started
  • Fixing Unclean Code
  • Incrementalism
  • Fixtures and SetUp
  • Thinking and TDD
  • Limiting Length
  • Dropping Vowels
  • Doing What It Takes To Clarify Tests
  • Testing Outside the Box
  • Refactoring to Single Responsibility Functions
  • Finishing Up
  • What Tests Are We Missing?
  • Our Solution
  • The Soundex Class
  • Tear Down
• Test-Driven Development Foundations
  • Set Up
  • Unit Test and TDD Fundamentals
  • The TDD Cycle: Red-Green-Refactor
  • The Three Rules of TDD
  • Getting Green on Red
  • Mindsets for Success
  • Mechanics for Success
  • Tear Down
• Test Construction
  • Set Up
  • Organization
  • Fast Tests, Slow Tests, Filters, and Suites
  • Assertions
  • Inspecting Privates
  • Testing vs. Test-Driving: Parameterized Tests and Other Toys
  • Tear Down
• Test Doubles excerpt
  • Set Up
  • Dependency Challenges
  • Test Doubles
  • A Hand-Crafted Test Double
  • Improving Test Abstraction When Using Test Doubles
  • Using Mock Tools
  • Alternate Dependency Injection Techniques
  • Design Will Change
  • Strategies for Using Test Doubles
  • Miscellaneous Test Double Topics
  • Tear Down
• Incremental Design
  • Set Up
  • Simple Design
  • Where Is the Up-Front Design?
  • Refactoring Inhibitors
  • Tear Down
• Quality Tests
  • Set Up
  • Tests Come FIRST
  • One Assert Per Test
  • Test Abstraction
  • Tear Down
• Legacy Challenges
• Additional TDD Concepts and Discussions
  • Alternate Approaches
  • Triangulation
  • The TPP
  • Performance
  • Integration Testing
  • Threading
• Growing and Sustaining TDD
  • Set Up
  • Explaining TDD to Non-Techies
  • The Bad Test Death Spiral, aka The SCUMmy Cycle
  • Pair Programming
  • Katas and Dojos
  • Using the Code Coverage Metric Effectively
  • Continuous Integration
  • Deriving Team Standards for TDD
  • Keeping up With the Community
  • Tear Down
• Appendix A. Other C++ Unit Testing Tools
• Appendix B. Code Kata: Roman Numeral Converter
  • Set Up
  • Let’s Go!
  • Practice Makes Perfect
  • Tear Down
• Bibliography

About the Author

Jeff Langr wrote Agile in a Flash with Tim Ottinger. It’s a unique set of reference and recommendation cards that you can find tacked to many monitors and walls in agile shops. He has written other books and more than one hundred articles on software development, and trains and consults in software development, including test-driven development.

Latest Topics in the Forums…

• Errata etc.