The document appears to be a presentation about building a mobile app for ordering from Ohio City Burrito. It discusses using an agile approach with acceptance test-driven development (ATDD) and continuous collaboration between developers and product owners. Live coding is demonstrated for writing automated tests and code to display menu items and prices in the app.

1. The whole enchilada
Inception to delivery in
just 2 weeks
1

2. We write code... and we
write it well
Oh... And we’re ON A
BOAT!
2

3. Steve Jackson Dave Shah
@stevejxsn @daveshah
steve.jackson@leandogsoftware.com dave.shah@leandogsoftware.com
3

4. WE LOVE BURRITOS...
4

5. We love apps....
5

6. We LOVE FEEDBACK!
6

7. Making assumptions explicit
7

8. Features
8

9. Low Fidelity Prototyping
9

10. We Wrote a cuke...
Feature: Getting directions to Ohio City Burrito
As a hungry burrito lover
I want to drive to OCB
So I can get a Brother’s Burrito
Scenario: Directions button should take us to Google
Maps
Given I'm hungry for some OCB
When I touch the map icon
Then Google maps should provide me with directions
10

11. What’s A CUKE?...
Feature:
As a hungry burrito lover
I want to drive to OCB
So I can get a Brother’s
Scenario: Directions butt
take us to Google Maps
Given I'm hungry for some
When I touch the map icon
Then Google maps should p
with directions
CUKES ARE TESTS
11

12. Why test first?
(MORE ON THIS LATER...)
12

13. Why test first? (CONVINCING YOUR BOSS)
CapersJones, SoftwareAssessments, Benchmarks, andBestPractices- Addison- Wesley, 2000
13

14. ATDD
Acceptance Test Developer Test
Define
Def Fail
Def Fail
Def
TDD
Pass
Def
Pass
Def Refactor
Def
14

15. Three amigos
 Knows what to build
 Knows how to build it
 Knows how to verify it
15

16. Our First cuke
Feature: Getting directions to Ohio City Burrito
As a hungry burrito lover
I want to drive to OCB
So I can get a Brother’s Burrito
Scenario: Directions button should take us to Google
Maps
Given I'm hungry for some OCB
When I touch the map icon
Then Google maps should provide me with directions
16

17. Why ATDD?
 Constant Collaboration
 Improved Understanding
 Eliminates Waste
 Move Risk Forward
 Bake Quality In
17

18. Sounds great in theory... lets see some
code!
18

19. time travel
19

20. @Override
protected void onStart() {
super.onStart();
ListView menuListView = (ListView) findViewById(id.menu_list_view);
menuListView.setAdapter(new ArrayAdapter<String>(
this,android.R.layout.simple_list_item_1,
Arrays.asList("Burritos","Tacos","Choices and Additions")));
}
20

21. Scenario: Checking pricesGiven I want to see what Ohio City Burrito
serves
When I touch the menu signThen I should see the prices:
| Brother’s Burrito | $6.15 || Baby Burrito | $1.85 |
|
21

22. Then /^I should see the prices:$/ do |expected_items|
actual_items = []
expected_items.raw.each do |item, expected_price|
price = on(MenuScreen).price item
actual_items << [item, price]
end
expected_items.diff! actual_items
end
22

23. class MenuScreen
class MenuScreen
include Gametel
include Gametel
ITEM = 0
button(:directions, :id => "directions_button")
DESCRIPTION = 1
button(:call, :id => "call_button")
PRICE = 2
end
button(:directions, :id => "directions_button")
button(:call, :id => "call_button")
def price(item)
Gametel::Views::ListItem.new(platform, :text => item).text[PRICE]
end
end
23

24. And Now...
LIVE
CODING!!!!
24

25. So we mentioned science...
25

26. So we mentioned science...
26

27. So we mentioned science...
Acceptance Test Developer Test
Define
Def Fail
Def Fail
Def
TDD
Pass
Def
Pass
Def Refactor
Def
27
12

28. So we mentioned science...
Write a Test == Experiment
Hypothesis Fail
Def
Results
Repeat Pass
Def
Conclusion
Refactor
Def
28
12

29. Thanks!
Michael Lemley
@audienceofnone
29

30. Happy hacking!
https://github.com/leandog/OCBMobile
Steve Jackson Dave Shah
@stevejxsn @daveshah
steve.jackson@leandogsoftware.com dave.shah@leandogsoftware.com
30