19

7 cardinal sins of testing

Embed Size (px)

Citation preview

AGENDA

• Glutony• Greed• Sloth• Envy• Pride• Kenodoxia• Desire/Anger

SYSTEM UNDER TEST

GLUTTONY

• aPraepropere – too soon

• aLaute – too expensive

• aNimis,aArdenter – too much / eagerly

• aStudiose – too daintly

• aForente – wildly

aPraepropere – before time

aLaute – too expensive

• Ensure that something does not happen (impossible/flickering)

• Basing on schedulers (* */1 * * *)

• Push downwards

SYSTEM UNDER TEST

aArdenter/Nimis – too eagerly/much

aStudiose – too daintly

• Mockery

• Try not to mock at all (functor approach)

• Try not to mock business objects (business object library)

aForente – wildly

GREED

One wants access to resources she should

not have access to

• system test using non-business API (ex.

querying DB to see if everything is ok)

• integration test checking state of classes

that it is supposed to integrate

SLOTH

One does not want to do one's duty

• Tests that do not clean after themselves

• Purposely usess mess left by other test

ENVY

One wants to do other's duties

• System test extensively asserting (ex. report content)

KENODOXIA - BOASTING

BOASTING TEST

MODEST TEST

PRIDE

It's good to know languages but...

• Java

• Groovy

• Scala

• XQuery

• Etc.

WRATH / DESIRE

WRATH