Developing for Automation - WordPress.com

fanaticalpumaMechanics

Nov 5, 2013 (3 years and 7 months ago)

79 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’


Focused on problem of
Speed to Market


2


a’gile

was
the answer

Agile flavours at Seek

3

Kanban

XP

(Extreme
Programming
)


Scrum

Lean

Agile flavours at Seek

4

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”

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

5

People




Agile Myth: We Don’t Need Testers

Distinct Roles within a Successful Team

Quality and Testing
is a
joint effort for all parties involved


7

Source: Craig Smith
-

Suncorp

Changing Roles & Responsibilities

Testing is more important than ever, but it is evolving

8

Code

Customer

Exploratory
Testing

Security

Performance

Automation

Manual
Scripted

Requirements

Unit Testing

Developer

Tester

Business Analyst

Tools


Choosing a Toolset

10

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

Use what you
need

to get the job done

12

Nunit

Resharper

Selenium

SpecFlow

CTE XL

Test
Manager

MS TFS

SnagIt

Custom Test

Harnesses

SAP
GUI

NetLimiter

StresStimulus

The tools do not dictate how you do your job

They help you to do a better job

Process


Agile Myth: We Don’t Need Planning or
Documentation

A Working Process

14

2
-

Story Kick
-
off

4
-

Story Walkthrough

1
-

Story Workshop

“Quality Gateways” through the whole process

15

0
-

Inception

3


Parallel Development
and Test Planning

5
-

Test Execution

6
-

Showcase

7
-

Retro

Quality Gateways

16

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

Exploratory

Automation

4


Test Execution

End to End traceability is
automatically

maintained

17

~60
% of Test Effort
lies in Automation


~40%
of Test Effort lies
in
Manual/Exploratory


API

Selenium

Custom

Reports

Reporting is
a
utomatically generated

18

Reporting should be customised depending on the intended audience

Summary

19


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

20

Robert

Manger

rmanger@seek.com.au

@robertmanger