Test AutomationCanvas

Andrey RebrovScrumTrek

About

COOL STORY

Once upon a time

• Investment bank IT department • 7 integrated projects• Release each 2-3 months• Manual regression testing

Внезапно...

Guys, let’s try Jameleon and automate our regression testing!

2 months later…

Very _simple_ Jameleon script

Summary

• 5 projects stop their autotesting process

• 1 project finished with “pain”• 1 project become Jameleon fans

Time for investigation

Identify the problem

In our case

• Regression takes too much time• Bugs appears during fixture

configuration• Fix one bug – a new one appears• ...

We need metrics

And agree on what “done” means

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

What about testing practices?

In our case

• Unit-testing• Dev integration testing• Automated Functional Testing (UI

and WebService)

Nothing new =)

Quick win!

For example

• Recording tools, i.e. Selenium IDE • Create databse dump and then just

install it

Tools and infrastructure

We prefer to use

• Selenium 2 WebDriver• SoapUI• Linux servers• Jenkins with plugins• JIRA dashboards

Easy, yeah?

Test Automation Canvas

Problems Metrics & DoD Quick wins Tools & Infrastructure

Testing types

So, when we going to get some problems?

When we will separate connections!

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

Conclusion

Thank you!

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