Embed Size (px)
Citation preview
June 2015
Continuous Cycles in Test Automation
Ard Kramer (Delta Lloyd)Derk-Jan de Grood (Valori)
2015
2
A shared experience
Ard Kramer• Testmanager Delta Lloyd Leven• Test Consultant EclipseIT• @Ard_Kramer
Derk-Jan de Grood• Principal consultant Valori• @DerkJandeGrood• http://djdegrood.wordpress.com/
The Test Automation day – A continuing story
3
The Test Automation day – A continuing story
The sequels
4
TAD 2014
TAD 2013
1. TA only works when
mature 2. We need to start with TA to gain experience
(esp in Agile)
3. Start with pilot, don't let
the organization
get in the way
4. We need a business case
in order to convince managers
5. BC is influenced by
maturity6. get started and let each team find its own solution
7. TA as driver for Change
8.Growing need for central
approach
9. Embedding in the
organization is crucial
10. What test do you
automate? Are there any tests
defined?
TAD 2012
TAD 2015
Where we ended last year…
Steps 1-7: Early insights
6
Initial starting point
We want effective usage of Test Automation throughout the organization
7
Convert Manual to
Automated Testing
Re-usage of knowledge and standardized
approach
Tool selection should
lead to leading tool
1. Which application will fit
2. Which Divisions wants to start with test
automation
3. Prioritize (roadmap with TI, PoC en
Operational phase per division
4. Management decision to consolidate
5. Plan TI sessions
Test AnalystTest NavigatorART team Test Navigator
ART team
Support
Operational phase
Test Analyst
Business case
Managerial steering
First estimation by IT/Test manager
Commitment on priorities and roadmap
Turining BC bases upon PoC findings
Decision operational launch
Support by
ART team
PoC (pilot) faseexploration phase
PoC report
Test NavigatorPer division
Test NavigatorART team
Economic feasibility
Technicalfeasibility
Organizational feasibility
Apply individual results to other teams
9
Sharing Knowledge
10
v
11
Making a mind map with things that need to be organized for proper
support learned that this was a lot!
Roles and competences
12
Helpdesk ….CoachLicence manager
Conclusion of last year’s presentation:
13
People Determine
Success
Change needs speed, limited
scope and visibility
Chose an adaptive Approach
NEW LESSONS LEARNED WHILE IMPLEMENTING
Step 8-10
14
DECENTRAL: SUPPORT SA’S WITH EACH OF THE DEPT.
Helpdesk ….CoachLicence manager
Service
agreement
Transition TA in scrum
Team A
Team B
Team CIntegration
Give me the 10% most critical
tests in your testsetNOW
The Full Circle
18
1. TA only works when
mature 2. We need to start with TA to
gain experrience (esp in Agile)
3. Start with pilot, don't let
the organization get
in the way
4. We need a business case in
order to convince managers
5. BC is influenced by
maturity6. get started and let each team find its own solution
7. TA as driver for Change
8. Growing need for central
approach
9. Embedding in the
organization is crucial
10. What test do you
automate? Are there any tests
defined?
So it’s about maturity after all
19
Testflight: When tests are available …
What do we have, what can we do?
Team B Integration
Benchmark facts • 40-60% of the required tests is already automated
• 25-40% of these tests actually run • Failed tests need to be repaired.• Missing tests need to be designed
and automated.
Automated and OK
Automated but failing
Not Automated
When in a greenfield situation
Original roadmap
24
25
1. TA only works when
mature 2. We need to start with TA to gain experience (esp. in Agile)
3. Start with pilot, don't let
the organization get
in the way
4. We need a business case in
order to convince managers
5. BC is influenced by
maturity6. get started and let each team find its own solution
7. TA as driver for Change
8. Growing need for central
approach
9. Embedding in the
organization is crucial
10. What test do you
automate? Are there any tests
defined?
Key process, new challenge
26
TI PoC Ops
ORGANISATIONAL CHANGE
FROM DECENTRAL TO CENTRAL
27
New leadership: centralisation competences
Test
Business lines
Com
pete
nce
lines
Support TA
29
1. TA only works when
mature 2. We need to start with TA to gain experience (esp. in Agile)
3. Start with pilot, don't let
the organization get
in the way
4. We need a business case in
order to convince managers
5. BC is influenced by
maturity6. get started and let each team find its own solution
7. TA as driver for Change
8. Growing need for central
approach
9. Embedding in the
organization is crucial
10. What test do you
automate? Are there any tests
defined?
v
30
RETHINK THE SUPPORT AND MAINTENANCE IDEAS
New leadership: centralisation competences:Possibilities per business line?
Business lines
Com
pete
nce
lines
TestSupport TA
32
1. TA only works when
mature 2. We need to start with TA to gain experience (esp. in Agile)
3. Start with pilot, don't let
the organization get
in the way
4. We need a business case in
order to convince managers
5. BC is influenced by
maturity6. get started and let each team find its own solution
7. TA as driver for Change
8. Growing need for central
approach
9. Embedding in the
organization is crucial
10. What test do you
automate? Are there any tests
defined?
Scrum Teams
• Are test automation driven• Improve their way of working• Think of new solutions• That benefit their business
case.
33
TAD!
Reaching a tipping point
35
What tool to put in the spotlight ?
36
1. TA only works when
mature 2. We need to start with TA to gain experience (esp. in Agile)
3. Start with pilot, don't let
the organization get
in the way
4. We need a business case in
order to convince managers
5. BC is influenced by
maturity6. get started and let each team find its own solution
7. TA as driver for Change
8. Growing need for central
approach
9. Embedding in the
organization is crucial
10. What test do you
automate? Are there any tests
defined?
The new solutions that pop up can have value for other scrum teams as well.
THERE MORE CYCLES
37
Other cycles
38
Business Case Testing
Other cycles
39
Agile Adoption
Other cycles
40
Organizational Changes
Other cycles
41
TPI
Other cycles
42
(agile) Test strategy
Collaborate
43
WRAP-UP
44
Highlights
- People determine the success- Continue balance between central and decentral- Technique can be driver for change- But maturity can slow it down
- Be aware the context is changing – Collaboration needed
45
Technique
People
The earlier presentations
2014• http://www.slideshare.net/DerkJandeGrood/experience-story-
implementing-test-automation-in-your-organization• http://www.slideshare.net/DerkJandeGrood/implementing-test-
automation
2013• http://www.slideshare.net/DerkJandeGrood/im-looking-at-you-to-tell-
me-should-i-automate-v102012• http://www.slideshare.net/DerkJandeGrood/ta-day-door-to-open-or-to-
lock-in-template-taday-v11
46
