Skip to Content
Test Driven Development: By Example
book

Test Driven Development: By Example

by Kent Beck
November 2002
Intermediate to advanced
240 pages
5h 9m
English
Addison-Wesley Professional
Content preview from Test Driven Development: By Example

Chapter 25

Test-Driven Development Patterns

We need to answer some basic strategic questions before we can talk about the details of how to test:

  • What do we mean by testing?

  • When do we test?

  • How do we choose what logic to test?

  • How do we choose what data to test?

Test (noun)

How do you test your software? Write an automated test.

Test is a verb meaning “to evaluate.” No software engineers release even the tiniest change without testing, except the very confident and the very sloppy. I’ll assume that if you’ve gotten this far, you’re neither. Although you may test your changes, testing changes is not the same as having tests. Test is also a noun, “a procedure leading to acceptance or rejection.” Why does test the noun, a procedure that runs ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Start your free trial

You might also like

Refactoring: Improving the Design of Existing Code

Refactoring: Improving the Design of Existing Code

Martin Fowler
Refactoring: Improving the Design of Existing Code

Refactoring: Improving the Design of Existing Code

Martin Fowler, Kent Beck, John Brant, William Opdyke, Don Roberts

Publisher Resources

ISBN: 0321146530Purchase book