Ramdeo green

11:30 – 12:15 Room 3 Misleading Validations: Be Aware of Acceptance Criteria (en) Anand Ramdeo

Time:

Location:

Title:

Presenter:

MISLEADING      VALIDATIONS  

Be  Aware  Of  Acceptance  Criteria   Anand  Ramdeo  

@tes@nggeek  

!

1

Life  is  short,  art  long,  opportunity  flee4ng,  experience  treacherous,  

judgement  difficult    

Hippocrates  (460  –  400  BC)  

Men  are  disturbed  not  by  things,  but  by  the  views  which  they  take  of  them.  

 Epictetus  

Project  is  progressing  well  and  was  delivered  on  4me.  Customer  is  not  happy.    Project  is  progressing  well  and  was  delivered  on  4me,  however  customer  is  not  happy  because  upgraded  version  corrupted  their  exis4ng  data.  

Tes4ng  –  Problem  to  discover  

Dopamine  –  Green  is  good  

Informa4on  to  theory   Confirma4on  bias  –  

Don’t  ques4on  theory  

Sprint  =  tunnel  vision  

Working  system  aVer  every  commit-­‐  Lucid  Fallacy    

Narra4ve  fallacy  –  if  something  does  fail.  

NO  

YES  

The  value  of  any  prac4ce  depends  on  its  context.  

Define  context?  What  do  you  mean  by  context?   How  this  principle  helps  

me  on  –  every  single  day?  

How  do  I  know  if  I  am  following  this  principle?  

Can  I  consciously  check  if  I  am  following  this  principle?  

There  are  good  prac4ces  in  context,  but  there  are  no  best  prac4ces.  

What  do  we  get  by  rejec4ng  the  no4on  of  best  prac4ces?   If  an  approach  always  

work  in  a  given  context,  does  it  not  become  best  prac4ce  in  that  context?  

Does  it  not  make  it  easier  for  starter?  

When  do  we  know  if  a  prac4ce  is  becoming  best  prac4ce  –  in  our  mind?  

People  working  together  are  the  most  important  part  of  any  project’s  

context.  

How  do  you  define  most  important?  

What  do  you  mean  by  working  together?  

What  other  factors  are  considered  in  branding  people  as  most  important?  Are  they  important  

even  if  they  are  not  delivering?  

What  if  someone  is  not  a  good  team  member  and  s4ll  delivers  the  most?  

Projects  unfold  over  4me  in  ways  that  are  oVen  not  predictable.    

So  what  –  what  does  it  tell  me?  How  does  this  principle  help  me?  

How  do  I  know  if  I  am  following  this  principle  or  not  following  this  principle?  

What  if  project  turns  out  to  be  predictable?  

How  do  we  plan  if  we  know  its  unpredictable?  

The  product  is  a  solu4on.  If  the  problem  is  not  solved,  product  doesn’t  

work.  

Product  works  or  does  not  work  –  is  it  a  binary  thing?  What  if  there  are  workarounds?  

Product  usually  is  a  collec4on  of  problems,  what  if  most  problems  are  solved  and  few  are  not  solved?  

Is  it  important  to  find  a  problem?   How  does  it  help  in  my  

tes4ng  ac4vi4es  –  during    planning    &  execu4on?  

Good  soVware  tes4ng  is  a  challenging  intellectual  process.  

Does  it  have  to  be  challenging?  What  if  you  know  pa_ern  and  don’t  need  to  work  hard  to  find?  

What  do  you  mean  by  intellectual    process  in  tes4ng?  

How  do  I  know  if  what  I  am  doing  is  intellectual  or  not  ?  

What  happens  if  I  don’t  find  it  challenging  or  intellectually  engaging?  

Only  through  judgement  and  skill,  exercised  coopera4vely  throughout  the  en4re  project,  are  we  able  to  do  the  right  things  at  the  right  4mes  to  

effec4vely  test  our  products.  

 Given  That  4me  runs  out  or  par4cipants  are  bored  When  speakers  have  nothing  more  to  say  or  can  not  answer  Then    speaker  say  thank  you  for  your  4me  and  a_en4on.  

           Anand  Ramdeo              @tes4nggeek  

We depend on your feedback in order to improve the quality of this conference. Please kindly complete your feedback form.

At the end of the day feedback forms will be collected by the exit.

Thank you.