Upload
knowit-oy
View
219
Download
1
Embed Size (px)
DESCRIPTION
Tomi Nurmi gave Suunto Agile Testing Case presentation at Knowit's seminar Agile Testing Challenges 22.5.2014
Citation preview
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Agile testing at Suunto Tomi Nurmi
Test Manager
Suunto
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Agenda
• As I experienced it
– Agile and Agile System Testing at Suunto
– Test Automation
I am a Test Manager at Suunto and have been working with Agile/Scrum and test
automation for half of my testing career. I have long background in SW testing started at
Nokia Networks/NSN and now due to my work in Suunto I have also entered into the
world of mechanics, HW and related testing e.g. environmental testing. My interest to
test automation started from my work as testing engineer who wanted to do more. And
the interest to Agile/Scrum started as a natural evolution after understanding the
continuous changes in programs.
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Agile/Scrum at Suunto: Why?
• Maybe too obvious
– We face changes • World and customer keeps changing
• Plans change from internal reasons
• Reality has strong influence on the original intention
– We want fast feedback and reaction • Fast feedback leads to fast corrections
• Test all the time to get concrete feedback
• Need to know the challenges as soon as possible to get the correct fix
• Put the cat on the table
– We want to do the things that count • Be ready on time with the most valuable outcome
– Current process • Hard to plan
• Reaction to the change
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
The path as I see it
• Started Agile/Scrum from one corner – Web SW development
– I also had an Agile/Scrum back ground,
it was easy to start to use it
• Method looked promising – There was doubts if it would work for developing our products
– After thinking and discussions started to take it into use in ESW and other SW areas
– Lead to brief wild period with some SW development areas
• Agile = Freedom
– Old way mix Agile/Scrum, role challenges
– Learn how to practice Agile/Scrum also elsewhere
– SW and ESW uses Scrum
• Method is spreading (System Testing, Mechanical design etc.) – Getting better and better and still learning
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Suunto and Agile System Testing
• Adopting to the surrounding Agile/Scrum – Didn’t want to jump to Agile due to HW and Mechanics
– Using mainly old process
– Moved testing to earlier phases
– Took in the automation and simulation
– Decided to try some disciplines
• Early integration
• Strong test automation
• Nightly test runs
• Testing Backlog
• Sprints…
• It became evident…..
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
We use Scrum
Builds
HW/Mech
Build1 Build2 Build3
ESW
SW
System Testing
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Feedback from Test Project Manager / Scrum
Master
• ”We have better control and structure in the testing”
• ”We do more of the important things and less of not important”
• ”We need still continuously learn from our
ways of work”
• ”I wouldn’t go back any more to the old way”
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Test Automation
• My test automation background, Waterfall – I didn’t want to perform same checks over and over again.
– Tools available
– Not SW designer, tried to create modular and maintainable code
– After lots of ”refactoring” -> Test Automation is SW product
– And one ”turn key” test automation solution later
• Test Automation success story: – High goal -> go there bit by bit thru evolution
– Service based -> everything is simple and
atomic service to be used when you need it
– Modular -> only one place to do it
– Architectural thinking and good testing
oriented SW designers
– Control it yourself -> pick up a tool that is open
– Avoid record and playback
• Takes resources – Pays back when regression testing needed
– Pays back when close to the release
– Essential in Scrum/Agile
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Test Automation: Path
– Without test automation in Agile
• Manual regression is heavy
• Barely time to do the regression testing
• After 3 Sprints
”Arrrrggggh I do not want to do it again”
– Test automation at Suunto
• Started from small (web service)
• Tool that provided the needed capabilities
• Build on old internal tool
• Simple service based interface to control the tool
• The results encouraged to continue
-> Crazy vision of ”Full user automation”
• Selected tool seemed to stretch to this
• Lots of iterations and improvements and changes
• Woke up one day: ”we did it, close to reach the vision”
• When you hear:
”Hey look, we noticed we could use the automation also to this….”
You’ve got it
• Currently works in simulation, real device and in system
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Agile/Scrum is not a picnic
– Train the whole team before you start • Basic idea gets across, focus
– Strict discipline must be in place • Important things must be done
– Quality discipline (Definition of Done) • Create criteria set that works for you and emphasis on quality
– Continuous Integration is a must • On many levels, not only in Unit tests
• Proper Test Automation in place
– You must have and maintain the big picture • What is your target and how to get there
– Agile/Scrum doesn’t solve your problems • It should bring them visible
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
To Do Improvements in System Testing
– Take more Agile Testing practices in use:
• e.g. Test sketches to programmers before they start coding
– Improve the feedback chain from System Testing to the Product Backlog
– Improve the feedback between System Testing and programmers in other Sprints
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Grid
Suurkumarrus
Questions?
Find me: [email protected]
+358 40 5623 590