200 likes | 295 Views
Seeking ‘ a’gile Testing. Robert Manger – Senior Test Analyst. 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’
E N D
Seeking ‘a’gile Testing Robert Manger – Senior Test Analyst
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’gilewas the answer
Agile flavours at Seek XP (Extreme Programming) Kanban Lean Scrum
Agile flavours at Seek XP (Extreme Programming) Teams use a combination of whatever makes sense to them Kanban Lean Scrum “It’s not about adopting ‘Agile’. It’s about using agile techniques to get better”
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
Distinct Roles within a Successful Team Quality and Testing is a joint effort for all parties involved Source: Craig Smith - Suncorp Agile Myth: We Don’t Need Testers
Changing Roles & Responsibilities Testing is more important than ever, but it is evolving Business Analyst Tester Developer Manual Scripted Exploratory Testing Code Unit Testing Security Performance Automation Requirements Customer
Choosing a Toolset Agile Myth: We Don’t Need Tools There’s no such thing as a Silver Bullet
Choosing a Toolset Too much? Too little? The Right Tools for the Job
Use what you needto get the job done NetLimiter The tools do not dictate how you do your job They help you to do a better job SnagIt Custom Test Harnesses Test Manager CTE XL SpecFlow MS TFS SAP GUI Selenium Resharper Nunit StresStimulus
A Working Process Agile Myth: We Don’t Need Planning or Documentation
“Quality Gateways” through the whole process 0 - Inception 1 - Story Workshop 2 - Story Kick-off 3 – Parallel Development and Test Planning 4 - Story Walkthrough 5 - Test Execution 6 - Showcase 7 - Retro
Quality Gateways • Everyone is involved in Project definition • Everyone has input into the requirements and estimates • Developers are absolutely clear on what they need to do • Parallel Development and Test Planning • Testers are absolutely clear on what they are getting • Stakeholders get a chance to give feedback • Everyone has a chance to improve! Everyone is involved at everystep along the way
4 – Test Execution End to End traceability is automaticallymaintained ~60% of Test Effort lies in Automation ~40% of Test Effort lies in Manual/Exploratory Reports API Selenium Custom
Reporting is automatically generated Reporting should be customised depending on the intended audience
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….
Questions & Contact RobertManger rmanger@seek.com.au @robertmanger