A talk I gave at Sela on 10/7/2019

1. © Copyright SELA Software & Education Labs Ltd. | 14-18 Baruch Hirsch St Bnei Brak, 51202 Israel | www.selagroup.com
SELA DEVELOPER PRACTICE
May 20th-22nd, 2019
Arnon Axelrod
ATDD – Acceptance Test Driven
Development
The overlooked agile practice

2. Arnon Axelrod
ArnonAxelrod
@ArnonAxelrod
@ArnonAxelrod
Expert for:
Test Automation
Agile
Defect-free software
development

3. Agile
Daily
standups
Sprints
Backlog
Planning
Scrum
master

4. Agile processes promote sustainable development.
The sponsors, developers, and users should be able
to maintain a constant pace indefinitely.
Source: https://agilemanifesto.org/principles.html

5. But two things stand in our way…

6. Technical debt ≈ Accidental Complexity
Inherent Complexity Accidental Complexity

7. Complexity
Inherent Complexity Accidental Complexity
Complexity
Adding
features
Complexity
Adding
features

8. Refactoring
Complexity
Adding features

9. Test Coverage

10. Types (causes) of Bugs
Coding mistakes
Design or architectural flaw
Misunderstood requirements
Requirements don’t meet user expectations

11. User Stories

12. How do you perceive User Stories?
Only the Product Owner writes the user stories
The User Story should be well defined and detailed
A big feature should be split into small user stories before it's ready for development
Developers should implement the user story exactly as defined
A user story should follow this format:
As a <role>
In order to <solve a problem>
I want <the specified solution>

13. User Stories – the essence
As a <Role>
In order to <solve a problem>

14. User Story
=
Request for solution to a problem

15. ATDD – Acceptance Test Driven Development
PO defines the problem (User Story)
PO & team collaborate on simplest solution
Define Acceptance Criteria
Implement automated test
Implement Code & Refactor
Exploratory testing
Get customer feedback

16. Benefits
of ATDD

17. Eliminating bugs
Coding mistakes
Design or architectural flaw
Misunderstood requirements
Requirements don’t meet user expectations
Test coverage
Refactoring
Collaborative Acceptance
Criteria
Fast feedback
cycle

18. It’s a mindset
Prevent regression
Fix every new defect immediately
Perform RCA
Prevent similar faults
Break down complex problems
Fast feedback
Easy to test
Monitor and measure
Continuous learning, improvement and simplification

19. Challenges
People resist changes…
Legacy code and lack of automated
tests
Skills:
Breaking down features into small
user stories
Defining Acceptance Criteria
Writing automated-tests
Clean code & Refactoring

20. Coping with the challenges
Vision and persistence
Improve gradually and adjust
Low-hanging fruits
Practice
Get assistance!

21. How can help you?
Building a roadmap
Mentoring & Coaching
Defining user stories
Defining acceptance criteria
Clean code & Refactoring
Root cause analysis
Retrospectives
CI/CD
Test Automation
Courses
TDD & ATDD
Clean code & Refactoring
Advanced Test Automation
Practices

22. Questions