The first thought I had, reading about the Skype meltdown last week is: here’s another opportunity to score points for unit testing. Nothing like a a single bug causing so much havoc (or silence, in this case) to get developers attention to the catastrophes waiting to happen. But I decided to go deeper. There are
I was asked this question last Wednesday, when I led a TDD open session at the Israeli Software Craftsmanship User Group. My answer: It makes you think before you write code. In fact, next time somebody asks you what TDD stands for, you answer: Thinking-Driven Development. Sure, all the benefits are there: structured incremental progress,
It will be for me.This Wednesday, December 15th, I’m going to be a bit busy. 3pm Israel time, that’s 2pm CET, and 8am EST I’m giving a webinar about steps you can take right now toward agile. I really like to learn real world actionable stuff, and this webinar is where I’m giving back. Do
A couple of posts I read lately made me think. Again. The first one is Elisabeth Hendrickson’s on whether testers should write code. Elisabeth focuses on the perception of the tester in agile team. From Elisabeth’s research it shows that testers in teams (not only agile) are expected to be able to code. The research
I had a discussion today about the name “unit testing”, and its connotations. I’d like to remind you, dear reader, that the audience of this blog is already aware of the goodness that comes with unit testing. Unit testing is part of our day-to-day work, and also for people just starting to get interested in
Some people think that by blaming Microsoft, I’ve removed the responsibility of self development from the developers themselves. These are two separate things.Developers who want to expand their horizon, enhance their craftsmanship, will find ways to do that. And because there are so many sources, they will probably not get it just from Microsoft.But we
Last week I gave my “unit testing in the wild” presentation on LIDNUG. It was nice, and once the recording is up I’ll get all the info. But I wanted to talk about the experience. First of all: people, I’ve hit the jackpot. I’ve hit on one of the best ways to extract gold out
Time to see the difference between Moles and Isolator code. Let’s start with the code under test (a webpart): public class NewMessagesCountWebPart : WebPart{ private Label lblNewMessages; protected void CreateChildControls(int i) { CreateChildControls(); } protected override void CreateChildControls() { lblNewMessages = new Label(); lblNewMessages.Text = GetMessageNumberText(); this.Controls.Add(lblNewMessages); base.CreateChildControls(); } private string GetMessageNumberText() { using (SPSite site = new SPSite(“http://sharepoint.typemock.com”)) { using (SPWeb web
Recently, I’ve had a twitter conversation with Kent Beck. He mentioned that he noticed tests running slower – jumping from 1 to 6 seconds. I asked if he noticed an impact, and he said he definitely started running tests less. First of all, I take off my hat – I’m not sure I would notice
As part of my design for testability talk, I talked about how tools and languages impact testability. Then I came about Brett Schuchert’s post about TDD and if it’s language neutral. The post concentrates on how different TDD looks like in different languages. Moreover, how it is interpreted, based on the language of choice. And