Description

This is the only comprehensive treatment on TDD in == C++ == that 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
• 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++ ==.

<b>Q&A with Jeff Langr, author of Modern == C++ == Programming with Test-Driven Development</b>

Why did you write Modern == C++ == Programming with Test-Driven Development?
I’d been working with a number of == C++ == development teams recently that were very interested in using test-driven development (TDD) to get their source under control and whip it into a better shape. I thought, “If any language needs a way to safely accommodate continual, incremental change, it’s == C++ == .” There’s a dearth of material written on TDD in == C++ ==, and I figure I’d see what I could do to help.

Aren’t you being a bit bold with that book title?
Thanks for noticing. Sure, TDD isn’t the only way to do things, but I believe it’s the best technique we have in 2013 to help you succeed with programming, whether your language is == C++ == or something else. " Modern == C++ == " to me is about harnessing the great power of the language (including some nice, new C++11 features) with a mechanism that will allow you to do so safely and help you to craft a great design along the way.

If I already know TDD, what might I get out of this book?
I wanted Modern == C++ == Programming with Test-Driven Development to be the most up-to-date, comprehensive source of information on TDD. It covers just about everything you might expect, and adds a few up-to-date topics such as the Mikado Method and the Transformation Priority Premise (TPP). I incorporate my experiences throughout, so you’ll get a bunch of hard-won wisdom based on having practiced TDD for over a dozen years. You’ll also pick up some ideas for growing and sustaining TDD in your team.

Is the TDD material in the book book accessible to someone who isn’t familiar with == C++ ==?
While there’s plenty of code in the book, you should have no trouble following the examples if you’ve had any exposure to a C-based object-oriented language (such as Java, C#, or Objective-C). One of the goals in TDD is to structure your code to be expressive, and I strove to ensure the code in the book met that goal. I focus on TDD concepts and techniques that you can apply equally well to other languages.

What if I use a different unit testing tool?
The exercises use a mix of Google Test/Google Mock and CppUTest. However, once you’ve seen a couple unit testing tools, you’ve seen them all—it’s pretty easy to translate tests written in one tool into another (such as CppUnit, CxxTest, or Boost.Test). In the book, you’ll find an appendix that gives you some criteria to help you choose an appropriate unit testing tool for your team.

Contents and Extracts

• Foreword
• 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