• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Test Driven Development: A Short Introduction
 

Test Driven Development: A Short Introduction

on

  • 1,166 views

A brief introduction to TDD given 8th April 2011 to a group of junior developers. Part of an agile development induction afternoon.

A brief introduction to TDD given 8th April 2011 to a group of junior developers. Part of an agile development induction afternoon.

Statistics

Views

Total Views
1,166
Views on SlideShare
1,164
Embed Views
2

Actions

Likes
0
Downloads
2
Comments
0

1 Embed 2

http://www.linkedin.com 2

Accessibility

Categories

Upload Details

Uploaded via as OpenOffice

Usage Rights

CC Attribution-ShareAlike LicenseCC Attribution-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Test Driven Development: A Short Introduction Test Driven Development: A Short Introduction Presentation Transcript

    • Test Driven Development (a short introduction) (C) John Chandler 2011
    • Perfect Code? First Time? Every Time? (yeah right)
    • Confidence Through Tests Manual Tests = Error Prone Automated Tests = Repeatable
    • Writing Tests After the Code Is Useful
    • Writing Tests Before the Code Helps us...
    • Think about What before we decide How
    • Write code that is easy to test
    • Write small units of code at a time
    • Ensure all code has test coverage
    • Know when to stop writing code
    • First we write a test that fails
    • Then we write code to make the test pass
    • Did we break anything?
    • Are we more confident?
    • Refactor if necessary Refactor with confidence
    • Then repeat until done
    • What else?
    • Fail Fast Early Feedback
    • Easier to learn unfamiliar code
    • Easier to change unfamiliar code
    • Supplementary code documentation
    • Give confidence to Others
    • Continuous Integration
    • Now go write tests!