Why agile testing isn't working

Preview:

DESCRIPTION

Waarom Agile Testing niet werkt

Citation preview

Kishen Simbhoedatpanday #xebicon2012 @kishenpanday

ksimbhoedatpanday@xebia.com

Requirements + Design Implementation Testing Maintenance

Waterfall process

Agile Testing doesn’t work

When testing becomes

a separate activity

Todo Development Testing Done

Task 15 Task 13 Task 14

Task 5 Task 6 Task 7 Task 8 Task 9 Task 10 Task 11 Task 12

Task 1 Task 2 Task 3 Task 4

Scrum fall

Agile Testing doesn’t work

When team determines

tests during sprints

Becoming predicable?

Sprint X

Development Team

Unit Testing

Integration Testing

Automation Team

Acceptance Testing

Don’t split development & testing

Whole Team Approach

Specification Workshop

Sprint planning Implementation

Sprint

Review

Testing / Knowing upfront

Specification By Example Workshop

Individuals & Interaction are more important than

Processes & Tools

Why a Specification Workshop? Shared understanding of domain

Assumptions

Mom to her son:

“Son, please go to the market and buy 1 bottle of milk. If they have eggs, bring 6 ”

What did he bring home?

Create a common understanding Using Real Examples

Living documentation

Living documentation

Answer 1 Answer 2 IF answer 2 IF answer 1 Feedback

Spring Summer Wrong Right Bijna goed!

Summer Winter Wrong Wrong Niet goed

Winter Spring Right Wrong Bijna goed!

Winter Summer Right Right Goed!

Given: Student in exam with Question 1 And Question 1 has 2 answers to be entered And Correct answer 1 = Winter And Correct answer 2 = Summer

Agile Testing doesn’t work

When testers & developers

don’t really collaborate

Lets be honest… Some developers get TEST lazy

Testing

Not about breaking But preventing

The Dark Side

Why testers & developers should work together

Developers are great automaters!

Agile Testing doesn’t work

When testing is about zero bugs

Bad Quality?

Bad Quality?

Zero Bugs does not mean you’ve measured quality

Wait and see how it performs in the real world

It’s not low quality because it has 5 bugs

It’s low quality because people aren’t coming

~ Gojko Adzic

Low quality

Agile Testing doesn’t work

When it’s all about bugs status reports

Fire drill effect

Stop tracking stupid things nobody cares about

Are these measurements important to business?

Low Tech Testing Dashboard

0

1

2

3

4

5

6

7

8

9

Area 1 Area 2 Area 3 Area 4

Stop maintaining low level risk tests

Drive your testing effort

Agile Testing doesn’t work

When you focus on automation tools

UI

Integration

Unit

Acceptance tests too costly to maintain Avoid big tests in sequence and checks at the end

The Next Move

Drop the Testing Column – Test always

Specification by Example – Shared Understanding

Testers and Developers pulling the same direction

Measure what is important for the business

Shared agreement with business

Don’t focus on tools

Agile Testing will work when …

Coming together is a beginning. Keeping together is progress. Working together is success.

Heny Ford

Recommended