Closed sdzivanovich closed 9 years ago
Hmm, that's a good idea. Let me look through it today and see how I could do that.
I don't know about this. I kind of like how it shows individual elements, and then tips and tricks for how to put them all together.
I don't feel strongly about it. I'm probably biased because I learned general unit test structure/goals first, then started digging into mocking/verification/etc. afterward
I'm going to close this for now. If students seem to have trouble understanding unit tests, may re-arrange later.
I think "Unit Test Structure" (and maybe also "Code Coverage" and "Unit Testing as Part...") should precede the sections on doubles/stubs/verification/etc., as you kind of implicitly use the knowledge in the "Unit Test Structure" when structuring the unit test examples in the preceding chapters. The flow would be more "this is how unit tests are generally structured" into specifics, rather than throwing out a bunch of low-level specifics then presenting the more basic concepts of unit test structure afterwards