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

A Brief History of Automation

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

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

Agile More affordable enterprise tools. Mobile testing Cross browser testing

Better Agile API testing BDD/TDD

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

BDD?

Difference TDD. Natural language.

Error in syntax on slide.

Why go BDD?

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

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

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.

Automation Tools

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

Automation Process

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

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.

Start to drill down What it means for automation

Future State

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

Contact Michael Pollino michaelpollino@anztb.org