# Test-driven development: by example

> 테스트 주도 개발을 소개한 책. 1부의 Money 예시는 자바, 2부의 XUnit 예시는 파이썬이다. 3부는 패턴 모음.

[테스트 주도 개발](https://wiki.g15e.com/pages/Test-driven%20development.txt)을 소개한 책. 1부의 Money 예시는 [자바](https://wiki.g15e.com/pages/Java.txt), 2부의 XUnit 예시는 [파이썬](https://wiki.g15e.com/pages/Python.txt)이다. 3부는 [패턴 모음](https://wiki.g15e.com/pages/Patterns%20for%20TDD.txt).

## 메모

도메인 코드에 다른 내용이 섞여 들어가지 않도록 하기:

> Using classes this way in model code is a bit smelly. We would like to use a criterion that makes sense in the domain of finance, not in the domain of Java objects. --Chapter 7

## See also

- [Clean code that works](https://wiki.g15e.com/pages/Clean%20code%20that%20works.txt)
- [Known to unknown](https://wiki.g15e.com/pages/Known%20to%20unknown.txt)
- [Test coverage](https://wiki.g15e.com/pages/Test%20coverage.txt)
- [Turn fears into broken tests](https://wiki.g15e.com/pages/Turn%20fears%20into%20broken%20tests.txt)
- [Dependency and duplication](https://wiki.g15e.com/pages/Dependency%20and%20duplication.txt)
- [Isolated test](https://wiki.g15e.com/pages/Isolated%20test.txt)
- [Just ask the computer](https://wiki.g15e.com/pages/Just%20ask%20the%20computer.txt)
- [Test-implementation coupling](https://wiki.g15e.com/pages/Test-implementation%20coupling.txt)
- [TDD and design](https://wiki.g15e.com/pages/TDD%20and%20design.txt)
- [What not to test](https://wiki.g15e.com/pages/What%20not%20to%20test.txt)
- [Bad smells in test](https://wiki.g15e.com/pages/Bad%20smells%20in%20test.txt)
- [When to delete tests](https://wiki.g15e.com/pages/When%20to%20delete%20tests.txt)
- [TDD and XP](https://wiki.g15e.com/pages/TDD%20and%20XP.txt)