Testing the Entire Stack

Most talks you see about testing cover one particular tool, and rarely delve into the strategies around when you should use a particular tool for a particular kind of testing. This talk differs because it covers testing the entire stack: unit, integration, functional, behavior-driven, databases, user acceptance, mocking & stubbing, and other topics and strategies. I discuss the merits of “known good state” vs. “nuke & pave” for databases, discuss the differences between Classic TDDers vs. Mockists and how they approach testing. Throughout, I provide strategies and heuristics to help guide you when making decisions about how, when and why you are testing some part of your infrastructure.

Watch this Oredev video

Related Videos:

  • No Related Videos