Test Automation Canvas

1. Test Automation
Canvas
Andrey Rebrov
ScrumTrek

2. About

3. COOL STORY

4. Once upon a time
• Investment bank IT department
• 7 integrated projects
• Release each 2-3 months
• Manual regression testing

5. Внезапно...
Guys, let’s try Jameleon and
automate our regression
testing!

6. 2 months later…

7. Very _simple_ Jameleon script

8. Summary
• 5 projects stop their autotesting process
• 1 project finished with “pain”
• 1 project become Jameleon fans

9. Time for investigation

10. Identify the problem

11. In our case
• Regression takes too much time
• Bugs appears during fixture configuration
• Fix one bug – a new one appears
• ...

12. We need metrics

13. And agree on what “done”
means

14. Let`s choose metrics and DoD
• Regression should take 4 hours
• No more 5 open bugs in Jira
• Zero configuration related bugs

15. What about testing practices?

16. In our case
• Unit-testing
• Dev integration testing
• Automated Functional Testing (UI and
WebService)

17. Nothing new =)

18. Quick win!

19. For example
• Recording tools, i.e. Selenium IDE
• Create databse dump and then just install
it

20. Tools and infrastructure

22. We prefer to use
• Selenium 2 WebDriver
• SoapUI
• Linux servers
• Jenkins with plugins
• JIRA dashboards

23. Easy, yeah?

24. Test Automation Canvas
Problems Metrics & DoD Quick wins Tools &
Infrastructure
Testing types

25. So, when we going to get some
problems?
When we will separate
connections!

26. In our case
• Jameleon didn`t give us any quick win:
broke link Quick wins -
Tools&Infrastructure
• We defined metrics without DoD
• AFT can’t help with detecting incoming
bugs after fixing old ones: Problems -
Testing types link broken

27. Conclusion

28. Thank you!
•
• Email: arebrov@scrumtrek.ru
• Skype: rebrov.andrey
• Twitter: @andrebrov
• http://andrebrov.net
• http://codecrafting.pro