belgium testing days: shift your testing mindset

Lisa Crispin Co-‐Author with Janet Gregory, Agile Tes)ng: A Prac)cal Guide for Testers and Agile Teams, and the upcoming More Agile Tes)ng

Copyright 2014, Lisa Crispin and Janet Gregory

Copyright 2014 Lisa Crispin and Janet Gregory

•  Some slides and story-‐telling •  Learning through exercises and discussions


•  IteraBon (sprint) •  Feature (epic, theme or capability) •  Story • Done (story done, feature done, release done) •  Feedback

5


• more than “just” tesBng code • an acBvity; not a phase

6

What challenges do you see for tes2ng in agile?

7


Instead of ◦ We’re here to find bugs … or ensure requirements are met … or break the soWware …

Think – How do we “bake quality in” & help company succeed?

9


Can you think of some ways that you cross boundaries in how you work?

10

Also DevOps, UX designers, others

11

•  Simplicity •  Feedback • Respond to change


Analytical Relentlessly Curious Observant Skeptical Empiricist Critical Thinker Investigator

hCp://www.slideshare.net/ehendrickson

12

13

What does this phrase mean to you? What skills does tesBng require? Discuss!

Breadth of Skills

Dep

th o

f Ski

lls

T-‐shaped Skill-‐set

16

play, experiment, learn keeps us vital and alive Play, experiment, learn!


• Gives us an enthusiasm for life that is irreplaceable. Without it, life just doesn’t taste good -‐ Lucia Capocchione •  You can discover more about a person in an hour of play than in a year of conversaBon. -‐ Plato •  Play is our brain’s favourite way of learning – Dianne Ackerman

PorBa Tung (see references)

17


Instead of saying NO,

or being the gatekeeper

Be the informaBon provider so business can make the decisions

Ques2ons about the thinking tester? 18


• CommunicaBon means ... sharing ◦  Ideas, goals, informaBon, decisions, soluBons

• CollaboraBon means ... ◦ Working together to set goals, experiment, find soluBons ◦ The whole team …..

20


• Power of Three • Three Amigos • Pairing • ConBnuous feedback

21


•  On an index card, each person draw what your “word” means to you personally 4 minutes

• Now, collaborate – remember what is important to you … • Draw one picture (large paper) that everyone can ‘live with’. 7-‐8 minutes

22

Picture by Augusto EvangelisB, based on diagram from Elisabeth Hendrickson


User Story

Expand Tests

High level AT

Auto-‐ mate tests

Code &

Execute tests

Explore

Exploratory TesBng

Accept Story

Fix defects

Explore examples

24


Shoppers can easily and securely save billing info to re-‐use for each purchase, so that repeat business increases by X %.

25

Desired behavior (BDD) Given I am a shopper checking out, When I enter my billing informaBon, I’m prompted to save it securely for future

convenience



26

Given…

When…

Then…


• Examples provide common language •  Shared common understanding • Coding and tesBng concurrently •  Involves whole team •  Shared definiBon of DONE • Prevents defects

27

28

• QuesBon • Elicit examples • Uncover hidden assumpBons





Ques2ons about the collabora2on? 29


• Checking: Does the system do what it's supposed to do? • Exploring: Are there any other risks or vulnerabiliBes that we haven't thought about yet? • TesBng == checking + exploring

**Elisabeth Hendrickson, “The Two Sides of SoWware TesBng”, Agile ConnecBon

GUI

API

Unit Tests

31


From Mas Barcomb


It’s not just about code !!! ◦  Test business value ◦  Test assumpBons ◦ Uncover hidden assumpBons

The goal: ◦  Shared common understanding of the story ◦ PrevenBng defects (eliminate waste)

34

• Why are we doing this? • Who can help? Hinder? Who is impacted? • How can they help or hinder? Impacts • What can we do to support impacts?

Deliverables

35

36

Stakeholders / personas Impacts

Possible deliverables

Possible deliverables


AcBviBes by Bme

Child Storie

s

From Janet Gregory & MaC Barcomb

Jeff Pason: hsp://www.agileproductdesign.com/blog/the_new_backlog.html


From Janet Gregory & MaC Barcomb

Story Mapping


• Understand the business needs • What level are at? • Collaborate appropriately

Release level

IteraBon level

Story test level

Task level

System

level

40


• Know your customers • Make them real • Plan your exploratory tesBng using them

•  Picture – from Jeff Pason’s PragmaBc Personas weekly column on SBcky Minds (1/25/2010)

42


Template: •  Explore (target) •  With (resources) •  To discover (informa)on) Where: •  Target: Where are you exploring •  Resources: What resources will you bring with you •  Informa2on: What kind of informaBon are you hoping to find?

•  Explore It! by Elisabeth Hendrickson

43


Explore ediBng profiles With real user names To discover if there are instances where username constraints are not enforced A tool to guide explora)on. Keep it simple.

44


Story backlog for feature “Remember Me” New shoppers are encouraged to create a login account with username, password, and security features so that signups increase by X %.

Think of some personas to use for tesBng, and write some charters to guide your exploratory tesBng

45





Ques2ons? 46


• Know your context • Have a tool box full •  Simple is oWen best • Use your imaginaBon

Let’s look at some examples

48

Taken from Ready to use Graphic Organizers for primary grade teachers

Day 1

A new user wants to create her account

Day 1

The new user wants to log into the system

Day 2

An exisBng user wants to change her password

Day 2

An exisBng user forgets her password

Day 2

The new user wants to log into the system

Day 30

The system asks user to change her password

Day ??

…….

Day 60

The user wants to delete her account

Day ??

…….

Day ??

…….

Words / Phrases •  I wonder …. • What caught your asenBon? •  Could you show me? • What makes you think there is more?

Ques2ons / Predic2ons •  What might happen next?

•  Why would that be? •  What is the worst thing that could happen?

•  …. or the best? •  What assumpBons do you have?


Block account

User enters wrong

password

Wrong password a 2nd Bme; Issue

warning

User can’t log in

They are in the

database

The credenBals

meet req’ts

They entered their

credenBals correctly

Their password expired ….

Wrong password a third Bme

Prevent user from logging in again; Display msg

52


• PracBce anBcipaBng what will happen • Define your tests • Check – running tests or collaborate with customers and programmers before coding • Be prepared to change your tests if your predicBons are wrong •  Learn by reviewing – what quesBons could you have asked first.

53

Sub topic

Sub topic

Sub topic

MAIN TOPIC

Sub topic

Sub topic

first 2me

change

new account

password rules

encryp2on

save user name

rules

Login : User name & password


55


Story backlog for “Remember Me” capability


56


• Think simple • Have a variety of tools • Adapt to your needs •  Look in places you may not have considered

57





Ques2ons about the tools? 58


• Curiosity • Ability to observe • Ability to challenge • Ability to adapt • To recognize contexts • Ability to THINK !

60

61

Challenge Yourself !

What experiments will you try back at work?


Agile Tes)ng: A Prac)cal Guide for Testers and Agile Teams

Coming soon: More Agile Tes)ng !

By Lisa Crispin and Janet Gregory www.agiletester.ca Contact info www.lisacrispin.com Email: [email protected] Twiser: lisacrispin

62

•  Elisabeth Hendrickson �  CAST keynote hsp://www.slideshare.net/ehendrickson �  Explore It! – new book on PragmaBc Programmers �  hsp://www.agileconnecBon.com/arBcle/two-‐sides-‐soWware-‐tesBng-‐checking-‐and-‐exploring

•  Ben Kelly, hsp://lets-‐test.com/wp-‐content/uploads/2012/05/LetsTest2012-‐BenKelly-‐TheTesBngDead.pdf

•  Markus Gartner, hsp://www.shino.de/2012/07/16/cast-‐2012-‐the-‐tesBng-‐dead/, plus his book ATDD By Example

•  Paul Carvalho, hsp://www.agilejournal.com/arBcles/columns/column-‐arBcles/6515-‐low-‐tech-‐tools-‐for-‐the-‐thinking-‐tester

•  Ready to Use Graphic Organizers •  Alister Scos, tesBng ice cream cone anB-‐pasern, hsp://waBrmelon.com/2012/01/31/introducing-‐the-‐soWware-‐tesBng-‐ice-‐cream-‐cone/

•  Sharon Robson, Test AutomaBon Pyramid Expanded, hsp://blog.soWed.com/2013/08/26/1883/

•  hsp://www.exampler.com -‐ Brian Marick’s web site •  Gojko Adzic, Bridging the Communica)on Gap, 2009; Specifica)on by Example, 2011, Impact Mapping, 2013

•  www.sBckyminds.com/ PragmaBc Personas -‐ Jeff Pason’s weekly column 1/25/2010

•  Jean Tabaka, Collabora)on Explained, 2006 Addison-‐Wesley •  hsp://www.uie.com/arBcles/indispensable_skills •  PorBa Tung – Power of Play hsp://www.selfishprogramming.com/category/playmaking/

•  Esther Derby and Diana Larsen, Agile Retrospec)ves •  Linda Rising, Small Experiments, hsp://web.lindarising.info/uploads/Small_Experiments.pdf

•  Liz Keogh, “a simple way to esBmate complexity”, hsp://lizkeogh.com/2013/07/21/esBmaBng-‐complexity/ (and see her related blog posts)

•  Tastycupcakes.org, games for learning •  Gamestorming retreat hsp://www.co-‐learning.be/#agenda/GamestormingRetreat/06092014

•  Chaos Monkey & Ne{lix hsp://techblog.ne{lix.com/2012/07/chaos-‐monkey-‐released-‐into-‐wild.html

•  Weekend TesBng: www.weekendtesBng.org •  Michael Feathers, Working EffecBvely with Legacy Code, hsp://www.amazon.com/Working-‐EffecBvely-‐Legacy-‐Michael-‐Feathers/dp/0131177052

•  Strangler pasern for rewriBng legacy code: hsp://marBnfowler.com/bliki/StranglerApplicaBon.html





Any unanswered ques2ons / concerns? 66

belgium testing days: shift your testing mindset

Technology