slides from advanced topics in agile testing · gojko adzic •why are we doing this? --- the goal...

Advanced Topics in Agile Testing

Janet GregoryWith material by Lisa Crispin

www.eurostarconferences.com

A little about me

Agile Testing; 2009

More Agile Testing: Oct 2014

Website:

www.agiletester.com www.agiletester.ca

DragonFire Inc.

www.janetgregory.ca

@janetgregoryca

[email protected]

The Day… Maybe!

1. Introductions2. What do we want to talk about?3. Prioritize the topics4. Start tackling one problem at a time, using different

brainstorming techniques

5. Perhaps time at the end for general discussion or mini-open space for topics not discussed earlier

Advanced Topics on Agile Testing

• Collaborative, problem solving attitude, open

• Workshop – explore some new frontiers!

• Some slides – if we need them for explanation

• You’ll leave with some experiments to help with your biggest problems and goals

Expectations


What might we talk about? It’s up to you!

• Skills needed

• Selecting tools

• Technical debt

• Automation

• Pairing patterns

• Exploratory testing

• Experimenting

• Agile testing quadrants

Testing in:

• distributed teams

• with out-sourcing

• enterprise environments

• data warehousing / BI

• regulatory environments

• embedded systems

• mobile apps

Others?????Advanced Topics on Agile Testing

Introductions

• What is your specialty?

• What’s your goal for today?

• If possible, get some diverse specialties in your table group.


Let’s get started …

• Use the sticky notes on the tables to identify your problems

• Try be specific because we’ll be grouping them later

7

Now … Let’s prioritize

Group similar issues

Dot vote for your “favorites”

8

Next…

• Set SMART goals for the top 4 problems you are going to work on.

• What might be a measure for each.

15 minutes

4 Problems – 4 Approaches

Brainstorming techniques experimentation

– to help achieve goals– to reduce problem size

Techniques we’ll experiment with are:

1. Impact mapping2. Brain writing3. Communicating around a whiteboard: drawing, mind

mapping, flow diagrams4. A twist on brain writing

Debrief on each technique, sharing stories and experiences


Round 1: Impact Mapping – Gojko Adzic

• Why are we doing this? --- the goal

• Who can help or hinder? --- the stakeholders

• How can they help or hinder? --- the impacts!

• What can we do to help? --- the deliverables


Impact Map Example

Problem #1 on your list

Use impact mapping to help identify possible solutions

1. Take your group’s highest priority goal. That’s the Why? of your impact map.

2. Create an impact map with Whos, and

Hows for each Who, and

Whats for each How.

3. What’s the first experiment you’d try? Choose one path in the map to share with other groups.


Round 1: Outcomes – Impact Mapping

• What experiments do you want to try?

• Any interesting stories?

• Any outstanding questions?

• Any surprises about using impact mapping?


Round 2: Brain Writing

What is brain writing?

• It’s a way to share your ideas in writing and for others to add theirs

• Generate multiple ideas in silence

• Then discuss



Use brain writing to help identify possible solutions

1. Each of you take a sheet of paper.

2. Write your ideas for ways to work towards the goal on the paper.

3. After three minutes, pass your paper to the next person. (we’ll call time)

4. Read the ideas on the paper you got, and add more of your own.

5. Continue until each person has written on each paper.


Round 2: Outcomes – Brain Writing

• What experiments do you want to try?



• Any surprises about using brain writing?


Round 3: Using a Whiteboard

It’s about :

• Collaborating• Visualizing• Asking questions• Clarifying


Sub topic

Sub topic

Sub topic

Mind Mapping as a Tool

MAINTOPIC

Sub topic

Sub topic

first time

change

new account

password

rules

encryption

saveuser name

rules



Use the whiteboard (or flip chart) to draw to help clarify ideas and generate possible solutions

1. Gather around the flip chart

2. Start discussing ideas for working towards the goal. Draw as you talk. You can draw a mind map, flow diagram, pictures, whatever helps you think.

3. Capture ideas and experiments to try


Round 3: Outcomes - Drawing

• Did drawing help?

• What experiments or ideas did you capture?



• Any surprises about drawing?


Round 4: Brain Writing with a Twist

Incorporate ideas from others groups



Use other groups to help identify possible solutions

1. Start on your flipchart

2. Write your ideas for ways to work towards the goal.

3. After five-ten minutes, move right to the next team’s flip chart (we’ll call time)

4. Read the ideas written down, and add more of your own.

5. Continue for 3 rounds


Round 4: Outcomes -

• Take a look at all the ideas?

• Can you turn those ideas into realistic experiments to try?

• Any surprises about this way of thinking?


• The following slides may be helpful for topics we discussed or for future reference.

• We’ll write down resources, and there’s a separate list of useful links on agiletester.ca

More Resources


• Guiding development with examples• Testing• Automation tools• Learning / skills

ATDD (Acceptance Test Driven Development)


The discussion is the important part

• Try this in your groups – discuss this word

• Think of different aspects

• How many different perspectives can you get?

• Does it have different consequences based on how you use it?

Pairing for Testing

Tester-

Designer

Tester-

Support

Tester-Tester

Tester-Coder

Analyst,

DBA, Sys

Admin,

Customer…

Tester-

Marketer

Story Mapping

Jeff Patton: http://www.agileproductdesign.com/blog/the_new_backlog.html

Story Mapping

Example Story MapFrom Steve Rogalsky


Let’s Talk Testing ….

Advanced Topics on Agile Testing:

33

Agile Testing Quadrants

Variation from Gojko Adzic

Think Testing at Different Levels of Precision

Test Automation

Volcano

Original idea from Matt Barcomb;

Image by Jenn Sinclair


The key is “sustainable pace”

Technical debt slows us down


• Whole team = project team

• Team is responsible for testing activities

– Includes automation

• Whole team has all the skills needed

• Team designs for ease of test automation

• Whole team is ‘automation-infected’

Whole Team Approach


Choosing Your Tools

One size does not fit all !


• Focus on the problem, not the tool

• What’s being automated?

• What are the existing tools, environment?

• What is the life span, or future use of tests

Understand the Purpose


• Business readable

• Once passing, must always pass

Tests as Living Documentation


• Enables testers / business to define tests

• test code can be in programming language

• Programmers can run tests as they code

• Testers can ask programmers for help

• Takes time from ‘coding’ production code

• Tests are usually through the UI

• Programmers aren’t usually willing to help

• Tests are implemented after the code is written

• Testers create and implement all tests


Learning


Multi- discipline skills

Expert / Discipline skills

T-Shaped Skills

Breadth of Skills

De

pth

of

Sk

ills

Square-shaped Team

See links for more by Rob Lambert and Adam P. Knight

Context Sensitivity

Large organizations

Supportive Culture


The right infrastructure


The right people


1. Use real examples

2. Perform exploratory testing

3. Test your features (and the system)

4. Learn continually

5. Sensitivity to your context

6. Keep it real

Confidence Building Practices


References

• Check out the agiletester.ca website

• The list we created today


Agile Testing: A Practical Guide for Testers and Agile Teams

By Lisa Crispin and Janet Gregory

www.janetgregory.ca

email: [email protected]

Twitter: @janetgregoryca53

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

www.agiletester.ca www.agiletester.com

lisacrispin.com

email: [email protected]

Twitter: @lisacrispin

slides from advanced topics in agile testing · gojko adzic •why are we doing this? --- the goal...

Documents