book

Test Driven Development: By Example

by Kent Beck

November 2002

Intermediate to advanced

240 pages

5h 9m

English

Addison-Wesley Professional

Read now

Unlock full access

Courage

What’s Next?MetaphorJUnit UsageCode MetricsProcessTest QualityOne Last Review
Test (noun)Isolated TestTest ListTest FirstAssert FirstTest DataEvident Data
One Step TestStarter TestExplanation TestLearning Test1Another TestRegression TestBreakDo OverCheap Desk, Nice Chair
Child TestMock ObjectSelf ShuntLog StringCrash Test DummyBroken TestClean Check-in
Fake It (’Til You Make It)TriangulateObvious ImplementationOne to Many
AssertionFixtureExternal FixtureTest MethodException TestAll Tests
CommandValue ObjectNull ObjectTemplate MethodPluggable ObjectPluggable Selector3Factory MethodImposterCompositeCollecting ParameterSingleton
Reconcile DifferencesIsolate ChangeMigrate DataExtract MethodInline MethodExtract InterfaceMove MethodMethod ObjectAdd ParameterMethod Parameter to Constructor Parameter
How large should your steps be?What don’t you have to test?How do you know if you have good tests?How does TDD lead to frameworks?How much feedback do you need?When should you delete tests?How do the programming language and environment influence TDD?Can you test drive enormous systems?Can you drive development with application-level tests?How do you switch to TDD midstream?Who is TDD intended for?Is TDD sensitive to initial conditions?How does TDD relate to patterns?Why does TDD work?What’s with the name?How does TDD relate to the practices of Extreme Programming?Darach’s Challenge
Feedback

Content preview from Test Driven Development: By Example

Chapter 24 xUnit Retrospective

If the time comes for you to implement your own testing framework, then the sequence presented in Part II of this book can serve as your guide. The details of the implementation are not nearly as important as the test cases. If you can support a set of test cases like the ones given here, then you can write tests that are isolated and can be composed, and you will be on your way to being able to develop test-first.

xUnit has been ported to more than 30 programming languages as of this writing. Your language is likely to have an implementation already. But there are a couple of reasons for implementing xUnit yourself, even if there is a version already available: