Trying to unit test your code but finding that you end up with brittle, hard-to-maintain unit tests that are taking more and more of your time to keep current as your production code evolves? Do you KNOW you should be writing tests, but just cannot find an efficient way to do so? Then this talk is for YOU! Effective unit testing is more art than science -- in this talk we'll look at both Patterns and Anti-Patterns for writing, organizing, and designing efficient, effective unit tests that help to ensure your tests continue to add value to your project throughout its evolution rather than becoming an anchor that weighs down your progress and impedes your speed! Learn both what to do and what NOT to do from someone who has been writing unit tests for over ten years! Attendees should have at least some familiarity with basic unit testing frameworks (using Asserts, etc.) and be comfortable with general C# language constructs.
Speaker: Steve Bohlen
Topics: Unit Testing
Great material, though I think more code would have been helpful. Maybe covering fewer patterns would work better for the time slot?
This talk was really insightful. The speaker was one of the best at the conference IMHO. I have already (or rather un-applied in the case of anti-patterns) applied many of the points he made. For those who attended you can get the samples and slides he used on his blog, unhandled-exceptions.com, BTW this form doesn't work in ff 5
There was a lot of material in the class and it was probably one of my favorites of the whole conference. I believe his explanations and comparisons really solidified the material. We will be adopting some of these strategies and practices in our business. Considering the breadth and depth of what was presented, he did a fantastic job. I felt he really liked this subject (more than his course on DI and IoC) because he had so much to say on unit testing practices (both best practices and anti-patterns) while doing comparisons between them. I'm personally happy that he didn't go into mock frameworks in-depth, because that would just be too much for the session. But using mock frameworks is "big" right now, so I heard people discussing a lot about that related to the session. The course was packed full of good information. He seemed like a college professor giving you the best information to apply to your field, successfully. Highly recommended--you will leave with a lot to talk about, and even more that you want to go learn by yourself.
Lots of good content. Too much to cover in an hour. Could have a parts 2 & 3 easily. Tweeted several points/observations from his presentation.
While I liked the speaker's other two talks, I didn't enjoy this one as much. I think the main thing lacking was concrete examples of each "test smell" immediately after a description of it. Having an immediate example of false positives or excessive mocks would've been valuable. The examples at the end were good, but I would've liked more time spent on code.
Steve is a great communicator. He shared many practical tips during this session.