anztb may, 2014 sydney · automate at the story level automate ... •be pro-active; learn what it...

Janet Gregory, DragonFire Inc. Copyright 2014

ANZTB – May, 2014

Sydney

With material from Lisa Crispin

Copyright 2014 DragonFire Inc.

First agile team – 2000

Currently – coaching, testing

Agile Testing; January 2009

Working on 2nd book: Fall 2014 2


• Testing and Agile

• Importance of collaboration

• A couple of models for testing

• ATDD (acceptance test driven development)

• Wrap-up

Copyright 2009: Janet Gregory, DragonFire 3


• have short feedback loops

• active customer participation

• demand whole team collaboration

• test features as they are coded

• deliver business value at regular intervals

• adapt their processes based on feedback

…and so on………….


• more than “just” testing code

• an activity; not a phase

5

Potentially shippable product

Potentially shippable product

Testing Activities


• Can’t “test quality in”

• Whole team thinks testing

• Team is committed to quality

• Whole team solves problems

• Everyone collaborates

• Power of Three

7


• Collaboration means ... ◦ Working together to find solutions, etc.

• Communication means ... sharing ◦ Ideas, information, decisions, solutions, etc.

◦ Understand the media

◦ Know the audience

8

• Wrong assumptions are made

• Impact to the system are found too late

• Everyone’s skills are not utilized

• The team becomes divided

• Testers don’t know what is going on


• Mind maps

• Mock-ups / paper prototypes

• Flow diagrams

• Feedback and interaction

• Visibility – white boards

• Workshops

10

Understand the business value !

Copyright 2014 DragonFire Inc. Copyright 2009 Janet Gregory, DragonFire 15

The Agile Testing Quadrants (adapted from Brian Marick)

Copyright 2014 DragonFire Inc. Copyright 2009 Janet Gregory, DragonFire 16

The Agile Testing Quadrants (adapted from Brian Marick)

ATDD (Acceptance Test Driven Development)

push the tests lower

Automate at the feature

level

Automate at the

story level

Automate at the

task level

19

“Living

Documentation” David Evans, Gojko Adzic


• Whole team approach - collaborate

• Small testable stories

• Iterative & fast feedback

• Plan automation tasks for each story

• Keep the big picture in mind

22

Automate tests


Collaboration

Teamwork

Trust

Commitment

Delivering value to the customer


Instead of ◦ We’re here to find bugs … or ensure

requirements are met … or break the software …

Think

– What can I do to help deliver the software successfully!

24


• Testers are NOT responsible for quality

◦ The whole team is

• Programmers do not code alone

◦ Everyone helps them understand what to code

• Your team needs the “right” roles and people

◦ Those in transition may feel protective of role

◦ New skills may be needed

Agile testing is full of challenges

• Be courageous – be a change agent

• Be pro-active; learn what it can be

26

Mostly, have fun

and enjoy the

challenge!


• www.lisacrispin.com

• [email protected]

• www.testobsessed.com (heuristics cheat sheet)

• Elisabeth Hendrickson, Explore IT, http://pragprog.com/book/ehxta/explore-it

• http://www.exampler.com - Brian Marick’s web site

• Gojko Adzic, Bridging the Communication Gap, 2009, Specification by Example, 2011

• Jean Tabaka, Collaboration Explained, 2006 Addison-Wesley


Now Available

Agile Testing: A Practical Guide for Testers and Agile Teams

By Lisa Crispin and Janet Gregory www.agiletester.ca

My contact info

www.janetgregory.ca

http://janetgregory.blogspot.com/

Email: [email protected]

www.lisacrispin.com

http://lisacrispin.com

Email: [email protected]

28


Instead of saying NO,

or being the gatekeeper

Be the information provider so business can make the decisions

Do you still have any concerns or unanswered questions?

29

anztb may, 2014 sydney · automate at the story level automate ... •be pro-active; learn what it...

Documents