I’m just about ready for a new release of Granny Squares. I did all my tests and development, merged with the master branch, and ran my tests again.
And one failed.
A trivial case–ensure that there’s one instance of the form in the formset on the main page of the site.
It certainly works. But the response object’s context is None, even though the content, status code, etc., are on point.
I’m not releasing the damn thing until the tests pass, but it’s a pain the ass, because I wanted to already be full tilt on August’s project.
For all the brouhaha about unit testing and Test Driven Development, I have yet to find a guide — book, website, anything — that actually discusses how to write unit tests.
There are nUnit-specific articles that talk about the foibles of each and how to have testing run constantly and so on and so forth, but how do I know how to compose a unit test? How low-level and nitty-gritty do tests need to be so that they’re useful without making me want to stab myself in the eye from maintenance? What’s the best way to test controllers vs. models?
Maybe I’m just not cool enough with Uncle Google to find what I’m looking for, and I certainly don’t mind experimentation, but I’d be interested in hearing how the “experts” approach TDD.