Tweet
Tweet

Slide 1

Slide 1 text

TEST DRIVEN DEVELOPMENT

Slide 2

Slide 2 text

i’m @qrush

Slide 3

Slide 3 text

@ i live here

Slide 4

Slide 4 text

c i work at 37signals

Slide 5

Slide 5 text

TESTING!

Slide 6

Slide 6 text

2/4/12

Slide 7

Slide 7 text

4/13/12

Slide 8

Slide 8 text

test-driven!

Slide 9

Slide 9 text

what is testing?

Slide 10

Slide 10 text

REFRESHING COMPILING FOR SOMEONE ELSE TO DO not:

Slide 11

Slide 11 text

TESTING DEFINES HOW YOUR CODE WORKS

Slide 12

Slide 12 text

why should i test?

Slide 13

Slide 13 text

PREDICTABILITY

Slide 14

Slide 14 text

TIGHTER FEEDBACK LOOPS

Slide 15

Slide 15 text

DEPENDABILITY

Slide 16

Slide 16 text

LOOSE COUPLING

Slide 17

Slide 17 text

how do you test something?

Slide 18

Slide 18 text

PICK ANY LANGUAGE

Slide 19

Slide 19 text

PICK ANY FRAMEWORK

Slide 20

Slide 20 text

SAME STEPS SAME PATTERNS

Slide 21

Slide 21 text

4 PHASE TEST

Slide 22

Slide 22 text

setup exercise verification teardown

Slide 23

Slide 23 text

what is TDD?

Slide 24

Slide 24 text

WRITE TESTS FIRST

Slide 25

Slide 25 text

WRITE NEW CODE ONLY ON TEST FAILURE

Slide 26

Slide 26 text

write a test watch it fail make it pass repeat

Slide 27

Slide 27 text

RHYTHM

Slide 28

Slide 28 text

red green refactor

Slide 29

Slide 29 text

No content

Slide 30

Slide 30 text

does this take longer?

Slide 31

Slide 31 text

YES

Slide 32

Slide 32 text

INITIALLY, BUT IT CAUSES LESS BUGS* * http://bit.ly/nugeo

Slide 33

Slide 33 text

does this suck sometimes?

Slide 34

Slide 34 text

YES

Slide 35

Slide 35 text

BUT IT PROVIDES CONFIDENCE

Slide 36

Slide 36 text

is it ok not to test?

Slide 37

Slide 37 text

YES

Slide 38

Slide 38 text

JUST SPIKE IT

Slide 39

Slide 39 text

BUT THROW IT AWAY

Slide 40

Slide 40 text

finally,

Slide 41

Slide 41 text

FIND A JOB* THAT HELPS YOU TEST

Slide 42

Slide 42 text

ASK ABOUT POLICIES ON TESTING

Slide 43

Slide 43 text

GO TEST YOUR CODE!