This document discusses testing approaches in agile development. It notes that with agile development using 2 week cycles, there is a shift from bug detection to bug prevention. It outlines the roles of testers and developers in agile teams, with testers focusing on manual testing and rapid feedback while developers rely more on test-driven development and automation. An example is given of how Atlassian uses both developers and testers by having testers focus on domain knowledge and manual testing of primary artifacts while developers concentrate on test automation and infrastructure. The key to their approach is emphasized as test automation within a continuous integration pipeline.

1. TESTING
IN THE NEW WORLD
bug prevention vs. bug detection
MICHAEL PALOTAS
17.06.2014

2. MICHAEL PALOTAS
Email: michael@pragmatic-solutions.ch
Twitter: @michael_palotas
Head of Productivity & Test Engineering
Agile Coach & Trainer – Agile Engineering Practices

3. TESTERS
RAISE
YOUR
HANDS
3

4. DEVELOPERS
RAISE
YOUR
HANDS
4

5. AGILE PEOPLE
RAISE
YOUR
HANDS
5

6. 6

7. 7
BUG
HUNTERS

8. Development
Test
Waterfall
-­‐
6
months
Development
Test
Agile
-­‐
2
weeks
8

9. PRODUCTIVITY
&
TEST ENGINEERING
9

10. HORIZONTAL / VERTICAL
SUPPORT
VERTICAL
VERTICAL
VERTICAL
HORIZONTAL
SUPPORT
TEAM
3
TEAM
2
TEAM
1
10

11. HORIZONTAL SUPPORT
TDD
Automation
Advice
Architecture
Infrastructure
11

12. VERTICAL SUPPORT
Rapid testing / exploratory approach
Focus on fast feedback
Manual testing: Very very very very important
Focus on primary work artifacts
Domain Knowledge
12

13. EXAMPLE: ATLASSIAN
Source:
Andrew
PrenMce,
Atlassian

14. Do we still need testers?
Or developers only?
14

15. 15
AUTOMATION
-­‐
THE
KEY
INGREDIENT

16. CI PIPELINE
VIDEO

17. 17

18. OPEN SOURCE
It is free
Invest into people instead of licenses
Faster innovation
Independence
Employee engagement
Hiring advantage
Requires a different mindset

19. 19
THE BIG GOAL

20. THANK YOU
20