Everyone knows it's important to test your code. But sometimes, the experience
What to do? Abandon the tests? Never! Smokey, this is not 'Nam. This is coding. There are rules.
Lately I have been thinking about how to write better integration tests for email scenarios in our applications. Email messaging is typically a pretty important part in the end users experience. It's a touch point, and it should be thoroughly tested in my opinion. So I took a look at things like email-spec that certainly will work well, but I still wasn't making me feel perfectly warm and fuzzy. I wanted a more "real world" integration test.
So we had a hackfest the other night, and it rocked. With pizza, beer, and nerd-chat, what could go wrong? We started off with some post-workday socializing then dove in to a great discussion about how people are utilizing testing to help them with their projects. A few in the room were...