• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
TDD - Test Driven Development
 

TDD - Test Driven Development

on

  • 1,596 views

 

Statistics

Views

Total Views
1,596
Views on SlideShare
1,546
Embed Views
50

Actions

Likes
0
Downloads
24
Comments
0

4 Embeds 50

http://chanmannlim.wordpress.com 40
http://www.slideshare.net 8
http://webcache.googleusercontent.com 1
http://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as OpenOffice

Usage Rights

© All Rights Reserved

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

    TDD - Test Driven Development TDD - Test Driven Development Presentation Transcript

    • TDD Test-Driven Development
    • Why is“testing”important?
      • Prove your system behaviors meet the requirements / specifications
      • Give you confidence
      • Lead your project to success
    • Understand TDD
      • Testing ≠ TDD
      • Repetition of short development cycle
      • Based-on specification
      • The goal is to write clean code that works
      • Tests are your first users
    • Perspectives around TDD
      • Test Driven Development?
      • Test Oriented Development?
      • Test Driven Design?
      • Test Driven Development and Design?
    • Why TDD?
      • Keeps you focus on required behavior
      • Improves quality (code design)
      • Provides and facilitates documentation
      • Being confident to change
      • Early identifies system defects
      • Comforts future maintenance
    • How to do TDD?
      • TDD Tools
      • TDD Cycle
      • Choosing the first test
    • TDD Tools JSSpec Mosquito RSpec
    • TDD Cycle
    • Choosing the first test
      • The simplest
      • The essense
      • If you need to write code that is untested, choose a simpler test .
      • If the essence approach takes to much time to implement, choose a simpler test .
    • Test should be
      • Small and focused
      • Intention revealing
      • Repeatable
      • Independent
      • Have no side-effects
    • Demo
    • Resources
      • http://en.wikipedia.org/wiki/Test-driven_development
      • http://www.agiledata.org/essays/tdd.html
      • http://www.amazon.com/exec/obidos/ISBN=0321146530
      • http://www.amazon.com/exec/obidos/ASIN/0131016490/ambysoftinc
      • http://www.slideshare.net/samnang.chhun/test-driven-development-2094018
    • Thank You! Lim Chanmann Software Developer, InSTEDD iLab [email_address] lchanmann http://chanmannlim.wordpress.com