Test Driven Development

Mythology

github.com/bryzaguy - twitter: @bryzaguy

What is TDD?:

Steps: Red, Green, Refactor.

Why TDD?

Testing and Refactoring

Why TDD?

Design and Confidence

Skeptical?

Common Myths Debunked

Myth #1: Takes Too Long

because I must TDD everything

Myth #2: Takes Too Long

because I must refactor everything first

Myth #3: Takes Too Long

because it's hard

Myth #4: TDD == Unit Testing

In object-oriented languages, each class is seen as a single unit. For the sake of separation of concerns, a unit test should always test only the functions of this single class.

Myth #5: Unit > Integration Tests

but unit tests don't test as much

Myth #6: TDD induced damage

dependency injection, duplicate tests

Myth #6: TDD induced damage

randomized tests, 90% code coverage

Myth #7,8,9: I can't because ...

need manager/product approval, no place to put them, fix failing tests first

Conclusion

TDD for testing, refactoring, design, confidence

Conclusion

Debunked some major myths

The End

Micro JavaScript Testing Framework: