1. Automation: Waterfall to BDD
Move your traditional automated testing into the new world of Agile and BDD.
Michael Pollino

3. A Brief History of Automation

4. Highly technical
Reliant on gurus
Ad hoc
Poor ROI
Specific functions or areas
Automation of process, rather than testing

5. The internet a factor (SQAForums)
Automation communities
Long test execution cycles
Proprietary programming languages

6. Agile
More affordable enterprise tools.
Mobile testing
Cross browser testing

7. Better Agile
API testing
BDD/TDD

8. Normalisation of automation. Becomes SDLC standard.
Death of GUI testing in ST/SIT. Still need manual element to UAT

9. BDD?

10. Difference TDD. Natural language.

11. Error in syntax on slide.

12. Why go BDD?

13. Driver at Organisational level.
Driver won’t be automation testing.
Business agility: freedom to adapt product roadmap, patch quickly and release quickly.
Move to more, smaller releases
Remove ‘hardening’ sprint

14. People, Culture and Change
Zoom out a bit. Talk on organisational level.

15. Most important slide
TOP DOWN
Need the right resources. Agile coach. Person to lead change. Doesn’t have to be people manager.
Skills. Automation engineers. Manual testers are not automated testers. Entry criteria for manual testers to train as automated testers.
Planning must reflect change. Velocity will decrease. Time must be allocated for training, peer reviews, R&D
Owners responsible for automation assets, execution and results must be identified.
Includes process. No retro? Not doing it properly.

16. Automation Tools

17. Must support tech roadmap. Moving to web platform?
Are there sufficient licenses? Can it be run in multiple environments?
Integrable is a word!
Able to be integrated with build tools? CI? TFS?
Portable? Linux build platform?
Can a BDD layer be added?
Will this layer be visible to the team to get the max benefits of BDD

18. Automation Process

19. New requiements. Review TCs, frameworks, result and delivery methods
New requiements. Review TCs, frameworks, result and delivery methods. External review?
Target your regression. When to run complete regression? Daily? Weekly?
Identify business critical test cases to run in ~5 minutes to integrate with CI.
Add BDD Layer. Cucumber. Specflow. Spock.
Merge dev and test code
Rollout across organisation

20. Run tests more
Run more often
Get the team invested in the daily automation results
Make automation part of the build process through CI
Can’t bring myself to say shift left.

21. Start to drill down
What it means for automation

22. Future State

23. Better intra and inter team collaboration
Peer reviews
Vigilance to defend process and asset quality
Be open to improvement and don’t fear change

24. Contact
Michael Pollino