1.
Agile Technical Practices
Sandy Mamoli
@smamol
www.nomad8.com

2.
user stories
acceptance testing unit testing
TDD
refactoring
load testing
coding standards whole team
collective code ownership
pair programming
continuous integration

3.
Quality
• Overview of Agile
• Agile Acceptance Testing
• Deployment pipeline (CI)

4.
Agile

5.
What is Agile?
• Software development framework
• Based on adaptive planning
• Used since 1995 (Scrum)

6.
Responding to change
Features: 6 months
As Defined
In Changed Form
Not Wanted Anymore
In Changed Form Not Wanted Anymore As Defined
Standish
Group,
Chaos
Report

7.
How does it work?

8.
Incrementing one bit at a time
1 2 3 4 5
© Jeff Patton, all rights reserved, www.AgileProductDesign.com

9.
Vertical slices - feedback & innovation
© Johnathan Rasmussen, The Agile Samurai

10.
Working, shippable software

11.
Build important things first

12.
Technical excellence

13.
Continuous improvement

14.
Agile Quality

15.
Cost of bugs

16.
A more scientific way of saying this ...
>150
150.0
112.5
75.0
50x
37.5
20x
5x 10x
1x
0
Source: Standish Group
Reqs Design Code DevT AccT Ops

17.
Agile Testing Quadrants
Agile Acceptance Test
Functional Test
Story Test
Unit Tests

18.
The dev’s view
exploratory testing
acceptance testing
unit
testing

19.
User Stories

20.
“incrementing” builds one bit at a time
1 2 3 4 5
© Jeff Patton, all rights reserved, www.AgileProductDesign.com

21.
Story&ID:& Priority:
high
Photo album privacy
Size:
Descrip/on: 13
As&a&...
photographer
I&want&to&...
make some photo albums private
So&that&...
I can have a backup of my personal
photos online

22.
Acceptance(Criteria
1. I can set the privacy of photo albums
2. I can see my private albums
3. My private albums are not visible to others

23.
Agile Acceptance
Testing

24.
Agile Testing Quadrants
Agile Acceptance Test
Functional Test
Story Test
Unit Tests

25.
Acceptance tests
• Check that the implementation
matches the intent
• Focus on shared understanding by
developers, testers and business people
• End to end

26.
Scenarios
• Create a new private album
• Make a public album private
• Make a private album public
<vertical slices through the acceptance criteria>

27.
Examples
Given I create an album named “My holiday”
When I choose to make it private
Then I can see the album “My holiday”
But Kai cannot see the album

28.
Examples
Given ... <something we accept to be true>
When ...<indicates the event in a scenario>
Then ...<indicates the expected outcome>

29.
<Melomel API>

30.
Cucumber
• Features
• Scenarios
• Steps
• Cucumber command

31.
cucumber: example

32.
cucumber: example
Features

33.
cucumber: example
Scenarios

34.
cucumber: example
Steps

35.
cucumber: example
Cucumber command

36.
cucumber: example
Cucumber command

37.
cucumber: example
Cucumber command

38.
Good practices
• Hide unnecessary detail
• Make tests independent
• Don’t test absolutely everything

39.
Declarative vs. imperative style
Scenario: transfer money (imperative)
Given I have $100 in checking
And I have $20 in savings
When I go to the transfer form
And I select "Checking" from "Source Account"
And I select "Savings" from "Target Account"
And I fill in "Amount" with "15"
And I press "Execute Transfer"
Then I should see that I have $85 in checking
And I should see that I have $35 in savings

40.
Declarative vs. imperative style
Scenario: transfer money (declarative)
Given I have $100 in checking
And I have $20 in savings
When I transfer $15 from checking to savings
Then I should have $85 in checking

41.
Make tests independent
• Maintenance
• Where did it fail?
• Parallelise

42.
Don’t test absolutely everything
GUI
Tests
Acceptance
Tests
Unit Tests

43.
Why I like ATDD
• Ensures the intent is well understood
• Ensures the implementation matches the
intent
• Ensures the implementation keeps matching
the intent

44.
Living documentation

45.
Unit testing

46.
Agile Testing Quadrants
Agile Acceptance Test
Functional Test
Story Test
Unit Tests

47.
Unit tests
• Check that the program behaves as the
developer thinks it should
• Tend to be focussed on the structural
(internal) quality of the code
• Hard for testers and business people to
understand

48.
Unit tests/TDD
• FlexUnit
• MXUnit

49.
Deployment
Pipeline

50.
Agile Testing Quadrants
Agile Acceptance Test
Functional Test
Story Test
Unit Tests

51.
As often as possible to get
early and instant feedback

52.
Deployment pipeline
Deployment pipeline: Jez Humble, www.continuousdelivery.com

53.
Agile deployment pipeline
Deployment pipeline: Jez Humble, www.continuousdelivery.com

54.
Deployment pipeline: Commit stage
• Create deployable artifacts
• Or fail fast and notify the team
• Triggered by CI server
• 5 minutes or less to run
• Jenkins, TeamCity, etc

55.
Continuous integration is a practice not a tool
• Commit regularly (at least once a day)
• Fix any broken build immediately
• Write automated tests

56.
Deployment pipeline: Acceptance test stage
• Verify acceptance criteria have been met
• Verify business value
• Run in parallel
• Refactor

57.
How to get started
• Create a walking skeleton with placeholders
• Automate the build and deploy process
• Automate unit tests and code analysis
• Automate acceptance tests
• Evolve the pipeline

58.
Recommended reading
+ +

59.
Call to action
• Work on Melomel & Cucumber
• Participate in CI projects (Jenkins)
• Steal from Ruby on Rails :-)

60.
Contact me
Sandy Mamoli
@smamol
sandy@nomad8.com