saga of unsung heroes (a tribute to all testers in this world)

8/9/2019 Saga of Unsung Heroes (A tribute to all testers in this world)

1/129

Saga of Unsung Heroes

[email protected]

[email protected]://www.geektester.blogspot.com


2/129

Im Raj.


3/129

Im Nakul.

[email protected]

http://www.stickyminds.com/s.asp?F=S15975_ART_2


4/129

We test software at BIEngineering, MSIT.


5/129

Before starting we want toshow you some pictures


6/129


7/129


8/129


9/129

This presentations is for theTester, by the Testers.


10/129

Testers,who save millions of dollars


11/129


by finding bugs


12/129


still stay unheard


13/129


still stay unsung


14/129

Our job is to find faults in

the software


15/129

If we say the software is fine

and it isnt, it looks likewedidnt do our jobs


16/129

If we say the software isnt

fine and it is, it looks likewedont know what were

talking about


17/129

If we say the software isnt

fine andwere correct, wevedone our jobs right,but now

other people have to do more

work to fix it.


18/129

If we say the software IS fine

andwere correct, thenchampagne and pats on the

back of all the Developers


19/129

How often does that happen?


20/129

Scary Story #1Can we sign off?


21/129

First lets hear this out..


22/129

Developers & PMs havespent countless nights

developing the software


23/129

They are proud parent;Its

their baby


24/129

Nobodywants totell

someonethat they have anugly baby


25/129

Nobody wants to tell

someone that they have anugly baby, unfortunately, its

our job.


26/129

It is called Ugly BabySyndrome


27/129

Here comes the questionagain


28/129

Can we sign off ?


29/129

TheInevitable & RecurringGhost


30/129

All eyes on test; spotlights on


31/129

Expectation from Test?


32/129

Say YES to Go-Live


33/129

Despite of the fact


34/129

Despite of the factproduct crashes sometime


35/129

Despite of the factfew scenarios are not working


36/129

Despite of the factperformance doesnt always

meet the SLA.


37/129

BecauseSaying NO is seldom an option


38/129

BecauseTesters can sign off based on

their confidence & gut feel


39/129

BecauseAfter all Quality istester baby


40/129

But can we proposea formula for test sign-off


41/129

But can we propose80/20 Sign-Off Formula


42/129

80/20 Sign-O

ff Formula80 % of the decision to be based

ONLY on test metrics


43/129

80/20 Sign-O

ff Formulaonly 20% decision to be based on

Testers Emotional Quotient


44/129

80/20 Sign-O

ff FormulaSmiley

and Frown to be added to

to the app to take testersfeedback


45/129

80/20 Sign-O

ff FormulaInterpretations can be derived

from data

0

5

10

Frown Smiley

Tester's Feedback - EQ

Feature Count


46/129

Can we also proposea joint sign-off by


47/129

Can we also proposea joint sign-off by

Dev, PM & Test


48/129

After all Quality is everyonesresponsibility


49/129

Sign-off decision will improve

because


50/129


becausedeveloper know the best about

code he has written


51/129


becausePM knows best about the

requirements & scope


52/129


because& Test knows the best about

what's working & what's not


53/129

Sign-off decision will improvebecause

joint sign-off is going to make

everyone equally accountable


54/129

Can we also dare to propose


55/129

Can we also dare to proposestop putting unbearable

pressure on test


56/129

Becauseasking this question everyday

will not really solvethe problem


57/129

Becausethis will make your testers

nervous & sometime even scared


58/129

Becausehumans commit most of the

errorswhen they are nervous &

under pressure


59/129

Becauseto meet the high expectations

they might just break and say

GO


60/129

Because

and its no news that even Indian

cricket team doesnt do so well

in pressure games


61/129

Scary Story #2

Sandwich Problem


62/129

Clock is ticking; Waiting forthetime bombto go off


63/129

Drop doesnt arrive as

scheduled


64/129

Because


65/129

BecauseA new Change Request

creeps in too late in the cycle


66/129

Because

an unexpected

environmental issue appears

in Dev


67/129

Becauseone of the key developer is

on an emergency leave.


68/129

Expectation from Test?


69/129

Test is expected to


70/129

Test is expected toAbsorbthe delay


71/129

Test is expected to

Accommodate unplanned

drops


72/129

Test is expected toto still discover all the bugs

despite of the time crunch.


73/129

Test is expected toCatch up on the lost time.


74/129

Can we propose


75/129

Can we proposeDiversify your test strength!!


76/129

Its all

about different Personas


77/129

Choose a tester for Persona #1

Process, Positive Testing

Logical Text Book approach,

confides on Facts


78/129


Scenario Based, User Based,

Innovative, Optimistic &

Critical approach


79/129


Critical, Judgmental,

Hunch, Intuition &

Negative Tests approach


80/129

Can we also propose


81/129

Can we also proposeDuet Integration Testing!!


82/129

Test participate in Dev Unit &Integration Testing


83/129

Can we also proposeInternal Dog Fooding.


84/129

Provide a test env toEx-Team member, community

users, Technology enthusiast


85/129

In House UAT / Frequent BugBash


86/129

Scary Story #3

Dont shoot the messenger


87/129

Software Testers don't

break software; it'sbroken

when we get it.


88/129

Testers are often perceived

as


89/129


as

show spoilers


90/129


as

pessimist


91/129


as

obstacles


92/129


as

bearer of bad news


93/129

Test teams start feeling

de-motivated & loses that fireto breakthe application


94/129

People often tend to forget

that testers job is to


95/129


that testers job is toexpect the failure


96/129


that testers job is tomake it fail


97/129


that testers job is tonot to expect that it works


98/129


that testers job is tonot to make false promises

by saying

All is Well


99/129

Can we propose


100/129

Can we proposeCelebrate the bugs


101/129

If want to make better software


102/129

If want to make better softwarestart celebrating every bug

which is discovered


103/129

We are NOT suggesting

that bugs should not be

prevented from occurring


104/129

But when they occur

one shouldnt panic & make

testers feel guilty for

committing a sin


105/129

Can we also propose

Dont punish the Testers


106/129

Dont punish the Testers for

finding bugs late


107/129

Because


108/129

Finding bugs late is better than

not finding them at all


109/129

Finding bugs late is better than

the embarrassment caused

when customer finds them


110/129

We are NOT suggesting

finding bugs late should be the

expectations


111/129

But better late than nevershould be the key message


112/129

Post-mortem analysis

is the right forum & time to

take preventive actions


113/129

Can we also propose


114/129

Can we also propose

Dont abuse the metrics


115/129

Bug free code

should be a goal


116/129

Bug free code

not a commitment


117/129

Such commitments make devs

more defensive


118/129

Such commitments make devs

more defensive

about accepting bugs


119/129

As they feel

test is provingthat they didnt

do a good job


120/129

As they feel

itwill make their metrics look

ugly


121/129

As they feel it

will go against them in annual

review


122/129

With this we wish to wind

up the conversation today


123/129

It was a small tribute to all

the testers in the world


124/129


the testers in the worlddoing a thankless job


125/129


the testers in the worldwho have spent long hours &

many years


126/129


the testers in the worldwho sincerely believe that

every bug they find makes

the product better


127/129

We hope this talk will

reinstate the same belief innew generation of testers


128/129

We hope this talk will

help the experienced testersto deal with the known

challenges.


129/129

Thank You

saga of unsung heroes (a tribute to all testers in this world)

Documents