Embed Size (px)
DESCRIPTION
In this engaging experience report, we will present 3 different views – Developer, Tester, Business Analyst – of implementing Acceptance Test Driven Development in a complex, data-driven domain. Hear how we used ATDD for building a ubiquitous language across the entire team, promoting faster feedback, and cultivating a culture where product owners were deeply invested in the quality of both every deliverable and the system as a whole.
Citation preview
Using ATDD to Build
Customers that Care
JEFFREY DAVIDSON consulting business analyst
ThoughtWorks.
@JeffreyGoodReq
goodrequirements.com
www.thoughtworks.com
®
LAV PATHAK software engineer ThoughtWorks. [email protected] @lav_pathak www.thoughtworks.com
®
SAM HOTOP senior test engineer
ThoughtWorks.
[email protected] samueljameshotop.blogspot.com
www.thoughtworks.com
®
Gas Pipelines
Unleash Your Inner Engineer
How does this thing work again?
Somebody should write this down
Humble beginnings…
Whiteboard >>> Scenarios
Accessible, Meaningful Tests
In-process Acceptance Tests
UI Tests
Acceptance Tests
Unit Tests
UI Tests
Acceptance Tests
Unit Tests
Unit (1600)
Acceptance (1250)
UI (100)
~2950 Total Tests
Build Times – Full Suite
16 mins: Pairing stations
35 mins: Unit & Acceptance / CI box
15 mins: UI Tests on CI box
When a Bug is found Bug
confirmed
QA pairing
with BA/PO!
Test(s) written & ignored
Dev pair refactors
Acceptance Test(s) Pass
Bug Killed
Analysts: Don’t be afraid
More whiteboard conversations
Remember Your Unit Tests!
Empower Your Product Owners
? Your Questions
Using ATDD to Build Customers that Care
Jeffrey Davidson
Lav Pathak
Sam Hotop
Skills Matter Agile Testing & BDD eXchange
NYC 2013
