beer & beta by flockler - feb 4th 2016
TRANSCRIPT
Beer & Beta 4.2.2016
Speed up development with automated testing
Eero Heino
Why test at all?
Why test at all?
Spend less time debugging→
know when it breaks
Why test at all?
Spend less time debugging→
know (early) when it breaks
Why test at all?
Real feedback comes after release→
know when to release
2 unit tests. 0 integration tests.
Good test automation?
Fast test cycle→
nobody is going to wait for results
Good test automation?
Reusable test cases→
Fast maintenance
Good test automation?
Whole team can understand it→
works as a communication channel
How to test?
How to test?
Find right tools & methods→
Defines time usage later
How to test?
Start with 1 automated test→
Most important thing for your user
How to test?
Find the right balance of how much to test
→ 10-170 tests on average
How to test?
Automate them→
Hook with code pushes or schedule
Usetrace as an example
Usetrace as an example
50 tests launched through CI →
runs for 8 minutes
Usetrace as an example
New feature or bug in production→
Under testing
Usetrace as an example
New feature or bug in production→
Under testing
Usetrace as an example
Without test automation releases every 2 weeks
→Now in 15min when tasks
completed
