SDET approach for Agile Testing

Post on 08-Aug-2015

267 views 2 download

Tags:

Transcript of SDET approach for Agile Testing

Systems Thinker | Developer | Efficient | Tester

THE NEW AGE TESTING IN THE LAND OF AGILE

SDET

Once upon a time - There was place for everyone

Development

Test

IT Operations

Agile came…

Water Scrum Fall was born (Forrester Research)

IT Ops

Dev & Test

IT Ops

Ops had to work more…

IT-Ops - What going on?

Courtesy: Jez Humble

The business requires change!

Core Conflict of an IT organization

Respond more quickly to urgent business needs – deliver feature changes

&

Provide stable, secure & predictable IT service

Double edged Sword…

New Age IT

To handle business change quickly & to run the businesses

To reduce “IT friction” at Dev/Ops world

To improve velocity to build/deliver/deploy software

To care for Quality, Maintainability, Security, Scalability, Durability, Deployability

To reduce Technical Debts

Tools

Process

Culture

Perfect storm of 2009

Ops thinks like developers, Developers think like Ops

Courtesy: Flickr

Delivering Value

Test

DevOps Movement

Be a Nigel…he helped the fishes in the tank

Culture is the way you think, act and Interact

It is not for me syndrome

What has changed in Testing?

There is no such thing as “manual” or “automated” testing,

just as there isn’t “manual” or “automated” programming

Testing is contextual

SDLC

SDLC/Agile

Agile

Change

Business Needs

IT Readiness Adoption

Unbalanced workload create severe bottlenecks

development

testi

ng

eff

ort

time

end of cycle

Process Quadrant

Fallacies of testing

- Testing is after development- I fail/break applications- We find defects- We work incremental- More features, more test cases, more regression- I wait for my big-batch, so that I get busy- We know what went wrong – post mortem analysis- We multi-task- We love playing ping-pong- Testing is a phase – we call it stabilization- We are domain experts- Our test environment is limited- We love writing test-cases- we plan enough- We trade-off- We love finding facts - We have a weapon to expedite testing “Risk Based Testing”

Caveats of traditional testing

- Execution delays - Cycle time- Lead-time to failure- Integrate, build, deploy dependencies- Environment Spec for running an app- Silo culture - Incremental in nature- Cost of delay – High- Queues & Congestion- Missing Feedback loops- Lack of continuous improvement- Vanity metrics – After the facts- Quality is not an outcome- Lack of Systems thinking- Response to change- IT friction- Technical debts

James Bach / Satisfice and Michael Bolton / DevelopSense

Rapid Software Testing

How do we do Agile development

experiment Develop &Design

Build cleanly& Simple

FosterTestability

experimentDevelop & Design

Build cleanly& Simple

FosterTestability

Test This

Quality is not an outcome

Where to move…

Testing on the toilet

Testing is not a phase anymore,

it is a blended responsibility of the project teams to deliver

- Faster feedback loops- Incremental value- Business continuity- Consistency & speed to deliver software on time.