Advanced  Topics  in  Agile  Tes0ng  Agile  Tes0ng  Days  2013  

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    

2

The  day…  Maybe!  

1.  Introduc0ons  2.  What  do  we  want  to  talk  about  3.  Priori0ze  4.  Then  start  tackling  one  problem  at  a  0me.          

 

3

Expecta0ons  

•  Collabora0ve,    problem  solving  aPtude,  open  

•  Workshop  –  We’ll  share  outcomes  with  the  world  (keep  me  honest)  

•  Some  slides  –  if  we  need  them  for  explana0on  

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

       

 

4

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

•  Impact  mapping  •  Agile  tes0ng  quadrants  •  T-­‐shaped  Skillsets  •  Mind  mapping  •  Selec0ng  tools  •  Technical  debt  

     

 

•  Distributed  teams  •  Out-­‐sourcing  •  Automa0on  •  Pairing  pa[erns  •  Experimen0ng  •  Others????    

     

 

Possible  topics:  

Next:      •  Iden0fy  problems,  set  SMART  goals  •  Brainstorm  experiments  to  achieve  goals  and  reduce  problem  size  –  Impact  mapping  – Other  discussion  and  brainstorming  exercises  such  as  mind  mapping,  drawing  on  the  whiteboard,  brain  wri0ng,  SWOT  analysis  

– We’ll  share  stories  and  experiences  

 

In  table  groups:  1.  Write  down  biggest  

tes0ng-­‐related  problems  for  your  own  team,  one  per  s0cky  note  

2.  Dot  vote  to  priori0ze  3.  Set  SMART  goal  for  

highest  priority  problem  

•  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  

Impact  Mapping  

7  

Example  Impact  Map    

8  

Based  on  example  at  h[p://impactmapping.org,  Gojko  Adzic  Recommended  book:  Impact  Mapping  

9  

Impact    Map  

Stakeholders  /  personas   Impacts  

Possible  deliverables  

Possible  deliverables  

10

More  Resources  

The  following  slides  may  be  helpful  for  topics  we  discuss,  or  for  future  reference.  

We’ll  write  down  resources,  and  there’s  a  separate  list  of  useful  links  

       

 

11

Agile  Tes0ng  Quadrants                

ATDD  (Acceptance  Test  Driven  Development)  

User  Story  

Expand  Tests  

High  level  AT  

Auto-­‐  mate  tests  

Code  &  

Execute  tests  

Explore    

Exploratory  Tes0ng  

Accept  Story  

Fix  defects  

Explore  examples  

12  

Sub  topic  

Sub  topic  

Sub  topic  

Mind  Mapping  as  a  Tool  

MAIN  TOPIC  

Sub  topic  

Sub  topic  

first  3me  

change  

new  account  

password  rules  

encryp3on  

save   user  name  

rules  

13  

14

Choosing  Tools  

§  Team  effort  §  Time  §  Requirements  §  Focus  on  goals,  problems,  not  tools.  §  Experiment          

 

•  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  0me  from  ‘coding’  produc0on  code  

•  Tests  are  usually  through  the  UI  

•  Programmers  aren’t  usually  willing  to  help  

•  Tests  are  implemented  amer  the  code  is  wri[en  

•  Testers  create  and  implement  all  tests  

15  

16

Understand  the  Purpose  

§  Who’s  using  the  tests?  What  for?  §  What’s  being  automated?  §  Exis0ng  tools,  environment  §  Who’s  doing  what  for  automa0ng?          

 

17

What  Fits  Your  Situa0on  •  Exis0ng  skills    •  Language  of  applica0on  under  test  •  Collabora0on  needs  •  What’s  being  automated  •  Life  span,  future  use  of  tests            

 

√  

19  

Pairing  for  Tes3ng  

Tester-Designer�

Tester-Support �

Tester-Tester�

Tester-Coder�

Analyst, DBA, Sys Admin, Customer…�

Tester-Marketer�

20  

The  key  is  “sustainable  pace”  

Technical  debt  slows  us  down    

     

   

       

Technical  Debt  Volcano  

From  Ma[  Barcomb  

Story  Mapping  

   

Ac0vi0es  by  0me  

Child  Storie

s  

From  Janet  Gregory  &  Ma?  Barcomb  

Jeff  Pa[on:  h[p://www.agileproductdesign.com/blog/the_new_backlog.html  

From  Janet  Gregory  &  Ma?  Barcomb  

Story  Mapping  

Mul0-­‐  discipline  skills  Expert  /  Discipline  skills  

Breadth of Skills

Dep

th o

f Ski

lls

T-­‐shaped  Skill-­‐set  

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

Test  Automa0on  Volcano  

From  Ma[  Barcomb  

Source:  Gojko  Adzic,  StarEast  2011  keynote  

Source:  Gojko  Adzic,  StarEast  2011  keynote  

29

Learn  to  write  maintainable  tests  §  Get  over  the  “hump  of  pain”                

From  Gerard  Meszaros’  XUnit  Test  Pa?erns  

30

Tests  as  Living  Documenta0on  §  Understandable  §  Who  will  really  use  them?  §  Once  passing,  must  always  pass                        

 

31  

Supportive Culture�

32  

The right infrastructure �

33  

The right people �