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.

1. Using ATDD to Build
Customers that Care

2. JEFFREY DAVIDSON consulting business analyst
ThoughtWorks.
jeffrey.davidson@thoughtworks.com
@JeffreyGoodReq
goodrequirements.com
www.thoughtworks.com
®
LAV PATHAK software engineer
ThoughtWorks.
lav.pathak@thoughtworks.com@lav_pathak
www.thoughtworks.com
®
SAM HOTOP senior test engineer
ThoughtWorks.
shotop@thoughtworks.com
samueljameshotop.blogspot.com
www.thoughtworks.com
®

3. Gas Pipelines

6. Unleash Your Inner Engineer

8. How does this thing work again?

9. omebody should write this down

10. Humble beginnings…

11. Whiteboard >>> Scenarios

12. Accessible, Meaningful Tests

13. In-process Acceptance Tests

15. UI
Tests
Acceptance
Tests
Unit Tests

16. UI
Tests
Acceptance
Tests
Unit Tests

17. Unit (1600)
Acceptance
(1250)
UI (100)
~2950
Total Tests

18. Build Times – Full Suite
16 mins: Pairing stations
35 mins: Unit & Acceptance / CI box
15 mins: UI Tests on CI box

19. 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

20. Analysts: Don’t be afraid

21. More whiteboard conversations

22. Remember Your Unit Tests!

23. Empower Your Product Owners

24. ?Your
Questions

25. Using ATDD to Build
Customers that Care
Jeffrey Davidson
Lav Pathak
Sam Hotop
Skills Matter
Agile Testing & BDD eXchange
NYC 2013