Last week I had the pleasure of presenting at a .Net Code Camp on the topic of Unit Testing. A key theme of the session was barriers to adoption and the values we can achieve using this tool.The main barrier to my adoption of Unit Testing was the idea that writing twice as much code would increase the value of my work. Twice as much code, as was pointed out in a response to my post two week’s ago, sounds like higher maintenance costs, higher initial development costs, and a greater opportunity for bugs.
Less Than Dot is a community of passionate IT professionals and enthusiasts dedicated to sharing technical knowledge, experience, and assistance. Inside you will find reference materials, interesting technical discussions, and expert tips and commentary. Once you register for an account you will have immediate access to the forums and all past articles and commentaries.
Browsing "unit testing"
Saturday started off cold and rainy, but it didn’t matter because, for over 100 of us, there were more important things going on. Namely sessions ranging from the one I presented, Unit Testing, to specific C#, jQuery, database, ALM, Silverlight, Ruby, and Python topics. In fact there were so many specific topics and I heard so many good things about all of the sessions that I wish I could have twinned or tripled myself to attend them all.
There is a long list of reasons not to use Unit Testing in your current projects. In fact I was able to make such a long list of reasons not to use automated Unit Testing that I wasn’t able to use them all in my presentation for the Raleigh Code Camp this coming weekend.
Previous posts can be found here: Part One – The Beginning Part Two – The Domain Model Part Three – Testing the Schema Setting up the repositories for our objects is where this really starts to get fun for me. This is what allows us to work with the persisted objects so easily from our […]
Previous posts can be found here: Part One – The Beginning Part Two – The Domain Model In part two we set up our domain model. Now, before we can test nhibernate’s ability to work with and persist objects, we need to ensure that we’ve defined our schema well enough that NHibernate can create the […]
Part One – The Beginning In part one we discussed what has brought me to the shameful point of using an object-relational mapper. At the risk of being ostracized from the database community, I really think this is going to be helpful for my project. The next step is to actually build up the domain […]
For a while now, I’ve been brewing my own beer. Being a programmer, when I’m brewing of course I also need a way to store my recipes, and how they turn out. So I have a simple application I wrote that most recently uses SQL Server Compact edition for its database. Recently I was trying […]