Post on 21-Jan-2017
7 CARDINAL SINS OF
TESTING
R E M I GI U
S Z DU D E K
AGENDA•Glutony•Greed•Sloth•Envy•Pride•Kenodoxia•Desire/Anger
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
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
GREEDOne 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
SLOTHOne does not want to do one's duty• Tests that do not clean after themselves• Purposely usess mess left by other test
ENVYOne wants to do other's duties• System test extensively asserting (ex. report content)
KENODOXIA - BOASTING
BOASTING TEST
MODEST TEST
PRIDEIt's good to know
languages but...• Java•Groovy• Scala• XQuery• Etc.
WRATH / DESIRE
WRATH
THANK YO
U
Thou
shalt
go and re
sist t
he tem
ptation
to si
n