Brian White added the comment:
I am somewhat new to mock objects. I'm coding up my first one now (in
D) to simulate a "stream" for other objects I want to write.
Even within a single module, I typically have many tests for the methods
within that module. And since a module
Brian White added the comment:
Having tests run independently of each other is not the same as having
tests be completely independent. I'd argue that the latter is
impossible. You're never going to test the entire system in a single
test case and thus the tests work together
New submission from Brian White:
The attached diff adds a "-o" ("--one") option to the "unittest" module
that causes the run to abort on the first error encountered. I name my
tests so that the lowest-level tests get run first so stopping at the
first error tends
