13
Gil Zilberfeld The Empire Tests First

The Empire Strikes First

Embed Size (px)

Citation preview

Page 1: The Empire Strikes First

Gil Zilberfeld

The Empire Tests First

Page 2: The Empire Strikes First

Who Am I

Agile helperSoftware improverAuthor of “Everyday Unit Testing”

www.gilzilberfeld.comwww.everydayunittesting.com@gil_zilberfeld

Page 3: The Empire Strikes First

Darth Vader

Director

The Making of:

The Force Awakens With New Hope To Revenge The Last Three Movies

Page 4: The Empire Strikes First

Test Driven Development

Page 5: The Empire Strikes First

What we’re going to do:

• Define what we expect to get• Including a pass/fail criteria• Build the movie• Retrospect• Tweak if needed

Page 6: The Empire Strikes First

darkFunction Studio Editor

• Demo

Page 7: The Empire Strikes First

Chapter IV: A New Hope

• Build a starting team movie– Define who should be there– In what order they join– Where they are placed– Present it to everyone

Page 8: The Empire Strikes First

Chapter V: The Empire Strikes Back

• The bad guys arrive– Define how long we wait for them– Who are the bad guys (hint: Ewoks)– Tweak to make more dramatic

Page 9: The Empire Strikes First

Chapter VI: The Return of the Jedi

• The final showdown– Define a stare down– And who wins (Hint: Not Ewoks)– Sword fight!– Great victory image!

Page 10: The Empire Strikes First

Chapter VII: The Force Awakens

• Iterate!– Redefine the requirements– Add titles– Tweak for a better movie

Page 11: The Empire Strikes First

Summary

• TDD is great for all kind of projects

• Incremental phases allow us to change and improve on the

way without breaking things

Page 12: The Empire Strikes First

Yoda

Executive Producer, Retired Master Jedi

“DO MORE STAR WARS TDD,

YOU SHOULD. HMMM”

Yoda.

TOMORROW at 9:50

Page 13: The Empire Strikes First

@gil_zilberfeldhttp://www.gilzilberfeld.comhttp://www.everydayunittesting.com

May The Force Be With You!