seeking ‘ a’gile testing
Post on 25-Feb-2016
16 Views
Preview:
DESCRIPTION
TRANSCRIPT
Seeking ‘a’gile Testing
Robert Manger – Senior Test Analyst
2
Seek Context – Numbers & Facts• >14 years old• Sales, Advertising & Marketing Company• 5 technology platforms• ~7 project streams (in IT alone)• After several false starts didn’t want to be ‘Agile’ • Focused on problem of Speed to Market
‘a’gile was the answer
3
Agile flavours at Seek
Kanban
XP (Extreme
Programming)
Scrum
Lean
4
Agile flavours at Seek
Kanban
XP (Extreme
Programming)
Scrum
Lean
Teams use a combination of
whatever makes sense to them
“It’s not about adopting ‘Agile’. It’s about using agile techniques to get better”
5
High Level Scope
• People• Roles and Responsibilities• Attitudes and Perceptions
• Tools• Some of the tools we use to help us in our jobs
• Process• How we ensure we are maintaining and measuring a high level
of quality while ensuring speed
People
7
Agile Myth: We Don’t Need Testers
Distinct Roles within a Successful Team
Quality and Testing is a joint effort for all parties involved
Source: Craig Smith - Suncorp
8
Changing Roles & Responsibilities
Testing is more important than ever, but it is evolving
Cod
e
Cus
tom
er
Expl
orat
ory
Test
ing
Secu
rity
Perf
orm
ance
Aut
omat
ion
Man
ual
Scrip
ted
Req
uire
men
ts
Uni
t Tes
ting
Developer
Tester
Business Analyst
Tools
10
Choosing a Toolset
Agile Myth: We Don’t Need Tools
There’s no such thing as a Silver Bullet
11
The Right Tools for the Job
Too much? Too little?
Choosing a Toolset
12
Use what you need to get the job done
Nunit
Resharper
Selenium
SpecFlow
CTE XL
Test ManagerMS TFS
SnagIt
Custom Test Harnesses
SAP GUI
NetLimiter
StresStimulus
The tools do not dictate how you do your jobThey help you to do a better job
Process
14
Agile Myth: We Don’t Need Planning or Documentation
A Working Process
15
2 - Story Kick-off
4 - Story Walkthrough
1 - Story Workshop
“Quality Gateways” through the whole process
0 - Inception
3 – Parallel Development and Test Planning
5 - Test Execution
6 - Showcase
7 - Retro
16
Quality Gateways
Everyone is involved at every step along the way
0 – Inception 1 – Story Workshop
2 – Story Kick-off
3 - Test Planning
4 – Story Walkthrough
5 – Test Execution 6 – Showcase 7 – Retro
• Everyone is involved in Project definition
• Everyone has input into the requirements and estimates
• Developers are absolutely clear on what they need to do
• Testers are absolutely clear on what they are getting
• Stakeholders get a chance to give feedback
• Everyone has a chance to improve!
• Parallel Development and Test Planning
Manual
Ex-plorator
yAutoma-
tion
17
4 – Test Execution
End to End traceability is automatically maintained
~60% of Test Effort lies in Automation
~40% of Test Effort lies in Manual/Exploratory
API Selenium Custom Reports
18
Reporting is automatically generated
Reporting should be customised depending on the intended audience
19
Summary• Testers are increasing their skillsets• Testing is known to be an integral part of a strongly
cohesive team• There is no one “right” way of doing things• Testers (and BAs) are now driving the development• There is no hidden effort across the whole project • We can easily respond to change• Testers determine their own toolsets• A continuously improving process• This is just the tip of the iceberg
• The journey has only just begun….
top related