Upload
remigiusz-dudek
View
76
Download
2
Embed Size (px)
Citation preview
GLUTTONY
• aPraepropere – too soon
• aLaute – too expensive
• aNimis,aArdenter – too much / eagerly
• aStudiose – too daintly
• aForente – wildly
aLaute – too expensive
• Ensure that something does not happen (impossible/flickering)
• Basing on schedulers (* */1 * * *)
• Push downwards
aStudiose – too daintly
• Mockery
• Try not to mock at all (functor approach)
• Try not to mock business objects (business object library)
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