Testing Traps to Avoid in Agile Testing - EuroSTAR Conference · The 5 Traps .. again Testing Traps...

Preview:

Citation preview

Testing Traps to Avoid in Agile Testing

Janet GregoryWith material by Lisa Crispin

Dublin, 2014

Copyright 2014 DragonFire Inc. 2

Agile Testing; 2009

More Agile Testing: Oct 2014

Website:

www.agiletester.com www.agiletester.ca

DragonFire Inc.

www.janetgregory.ca

@janetgregoryca

janet@agiletester.ca

The Format

• Clues to identify 5 traps

• The associated risks

• Tips & techniques for avoidance

Testing Traps to Avoid on Agile Teams – Janet Gregory

The Traps

Testing Traps to Avoid on Agile Teams – Janet Gregory

1. Waiting for Tuesday’s build

2. Testers aren’t “really” part of the team

3. Maintaining a “Quality Police” mindset

4. Trying to test everything manually

5. Forgetting the big picture

#1 – Waiting for Tuesday’s Build

Testing Traps to Avoid on Agile Teams – Janet Gregory

• Testing tasks are stacking up ‘to do’

• Stories cannot be marked DONE

• Testing is done the next iteration

• Deployments aren’t tested regularly

The Risk: The Mini-Waterfall (ketchup effect)

Testing Traps to Avoid on Agile Teams – Janet Gregory

More Risks

Testing Traps to Avoid on Agile Teams – Janet Gregory

• Stories aren’t tested completely

• Testers lose credibility

• Technical debt increases

• Team changes meaning of ‘DONE’

Tip – Make CI Mandatory

Testing Traps to Avoid on Agile Teams – Janet Gregory

• Understand your CI (continuous integration) tool

• Know your build pipeline

• Plan for your test infrastructure

Tip - Collaborate

• Include testing tasks in the velocity

• Get your developers used to immediate feedback

• Test where it makes sense

Testing Traps to Avoid on Agile Teams – Janet Gregory

Copyright 2014 DragonFire Inc.

Instead of saying NO,

or being the gatekeeper

Be the information provider so business can make the decisions

Questions… about waiting …

10

#2 – Testers Aren’t ‘Really’ Part of the Team

Testing Traps to Avoid on Agile Teams – Janet Gregory

Testers don’t actively

participate

• Testing isn’t included in team velocity

• Testers test ‘only’ what the developers code

• Testers don’t understand the stories

The Risks

Testing Traps to Avoid on Agile Teams – Janet Gregory

• Wrong assumptions are made

• Impacts to the system are found late

• Everyone’s skills are not utilized

• The team becomes divided

Tips for Early Tester Involvement

Testing Traps to Avoid on Agile Teams – Janet Gregory

More Tips to Avoid Team Division

Testing Traps to Avoid on Agile Teams – Janet Gregory

• Help customers develop stories

Or Better Yet ….

Testing Traps to Avoid on Agile Teams – Janet Gregory

Copyright 2014 DragonFire Inc.

Instead of saying NO,

or being the gatekeeper

Be the information provider so business can make the decisions

Questions about whole team?

16

#3 – Maintaining a Quality Police Mindset

Testing Traps to Avoid on Agile Teams – Janet Gregory

• All bugs are entered into the DTS (Defect Tracking System)

• Testers are part of a separate test team

• The test team sits apart

• The test team can stop production

The Risks

Testing Traps to Avoid on Agile Teams – Janet Gregory

• Project team doesn’t buy the ‘build quality in’ concept

• Communication is through the defect tracking system

• Developers use testers as a safety net

• The team never ‘gels’

Tips to Change the “QP” Mindset

Testing Traps to Avoid on Agile Teams – Janet Gregory

• Define DONE to include testing

• Use a consulting mindset;

− share testing expertise

• Become more technically aware

• Have all members pick up testing tasks

• Develop relationships with programmers

20Testing Traps to Avoid on Agile Teams – Janet Gregory

Can you change your mindset?

Testing Traps to Avoid on Agile Teams – Janet Gregory

Think◦What can we do to help deliver

the software successfully?

Instead of◦We’re here to break the software!

Copyright 2014 DragonFire Inc.

Instead of saying NO,

or being the gatekeeper

Be the information provider so business can make the decisions

Questions… Agile Tester’s Mindset?

22

#4 – Trying to Test Everything Manually

Testing Traps to Avoid on Agile Teams – Janet Gregory

• Making excuses to miss meetings

• Regression suite not run regularly

• Spending time retesting features already tested

• Not testing new features

• Not contributing to implementation / design discussions

The Risks

Testing Traps to Avoid on Agile Teams – Janet Gregory

• Testing cannot keep up with new stories

• Features that used to work, are broken and not noticed

• Testers don’t learn new technology

• Testers get stuck in a rut

Techniques to Increase Automation

Testing Traps to Avoid on Agile Teams – Janet Gregory

• Automate as you go

• Include automation time in your estimates

• Design for testability

• Chose tools that encourage collaboration

• Understand the power & risks of automation

Tip: Make the Automation Maintainable

Testing Traps to Avoid on Agile Teams – Janet Gregory

• Tests pass all the time

• Don’t Repeat Yourself (DRY)

• Tests reveal intent – create good names

• Keep tests small with a clear purpose

• Manage your tests – be able to find them

Copyright 2014 DragonFire Inc. 28

**Automation does not exclude the need for exploratory testing*

Copyright 2014 DragonFire Inc.

Instead of saying NO,

or being the gatekeeper

Be the information provider so business can make the decisions

Questions… Automation?

29

• Testing only individual stories

• Finding integration bugs late

• Testing is based on what developers code

• Testing finds requirements type bugs

• Developers add extra code after they are finished

#5 – Forgetting the Big Picture

Testing Traps to Avoid on Agile Teams – Janet Gregory

Copyright 2014 DragonFire Inc.

We only see the tip of the IcebergWe don’t think of big systemsWe only looking at our own team.

The Risks

31

More Risks

Testing Traps to Avoid on Agile Teams – Janet Gregory

• Workflow isn’t smooth

• Decisions made during coding aren’t aligned with the end goal

Copyright 2014 DragonFire Inc. 33

Tips to Avoid Missing the Goal

Testing Traps to Avoid on Agile Teams – Janet Gregory

• Understand the story before coding starts

• Think system impacts

• Draw pictures / workflows

• Test data to reflect real world◦ Use examples ◦ Exploratory test

Copyright 2014 DragonFire Inc. 35

36

Think – Levels of Detail

37

Acceptance Test Driven Development

Copyright 2014 DragonFire Inc. 38

Agile Testing Quadrants (Brian Marick)

39

Think Feature Complete

Testing Traps to Avoid on Agile Teams – Janet Gregory

• Define “Feature (or epic) DONE”

– Acceptance tests for bigger picture

– GUI automation on workflow

– Quadrant 3 & 4 tests (from agile testing quadrants)

• Define “story DONE”

– API level automation by story

– Quadrant 1, 2, 3 tests (maybe some Q4)

Copyright 2014 DragonFire Inc.

Instead of saying NO,

or being the gatekeeper

Be the information provider so business can make the decisions

Questions… Remembering the Big Pic?

41

The 5 Traps .. again

Testing Traps to Avoid on Agile Teams – Janet Gregory

1. Waiting for Tuesday’s build− Not keeping up with developers

2. Testers aren’t really part of the team− No input into requirements

3. Quality police mindset− Ignoring the whole team approach

4. Trying to test everything manually− Not taking advantage of automation

5. Forgetting the big picture− Not delivering the right thing

Testing in agile projects is full of traps

Testing Traps to Avoid on Agile Teams – Janet Gregory

• Be aware, and watch for them, but don’t let them scare you

• Problems happen faster so impact is felt faster

• Make them visible so you can learn

• Be courageous – be a change agent

Mostly, have fun and enjoy the

challenge!

Agile Testing: A Practical Guide for Testers and Agile Teams

By Lisa Crispin and Janet Gregory

44

More Agile Testing: Learning Journeys for the Whole TeamBy Janet Gregory and Lisa Crispin

www.agiletester.ca www.agiletester.com

Contact info

www.janetgregory.ca

Email: janet@agiletester.ca

Twitter: janetgregoryca

Copyright 2014 DragonFire Inc.

• www.lisacrispin.com

• Elisabeth Hendrickson, Explore It, 2013

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

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

• Ester Derby and Dianne Larsen, Agile Retrospectives

• Agile Manifesto: http://agilemanifesto.org/

• Mary Poppendieck and Tom Poppendieck, Lean Software Development, Addison-Wesley (series of 3)

• agile-testing@yahoogroups.com

• Photos – Janet’s vacations or Microsoft office

45

Recommended