There's a great little chapter in Growing Object Oriented Software Guided by Tests on how to write helper methods for building complex test data. The specific techniques are somewhat less relevant in a post AutoFixture world, but the chapter also makes a powerful case that test code should read as English prose.
Saturday, April 22, 2017
Monday, January 2, 2017
I've always been a Unit Testing guy, but reading Growing Object Oriented Software Guided by Tests really brought home the role an acceptance test outer structure can play in an iterative development process.
Wednesday, November 9, 2016
Wednesday, November 2, 2016
So I've been working on a feature for Sitecore Instance Manager to automate installing Sitecore instances with Solr turned on. This has been pulled in to the Develop branch of SIM and should hopefully hit the downloadable version soon.
Wednesday, October 26, 2016
Thursday, September 15, 2016
Tuesday, June 14, 2016
Being able to debug Sitecore code is an important skill for supporting Sitecore solutions. There have been a number of excellent articles on how to do this, but they typically describe using JetBrains DotPeek product as a "symbol server". (See http://bilyukov.com/debugging-sitecore-dotpeek/, and https://jammykam.wordpress.com/2015/01/11/how-to-debug-sitecore-kernel-in-visual/). An alternative, which I find somewhat simpler, is to use ReSharper to generate PDB files, and place those in your solution bin directory. I will walk you through that approach in this article.
Wednesday, January 13, 2016
There is a special, lonely dread that accompanies a big, complex task. Am I up to it? Is it harder than I think? Am I missing something fundamental? I wonder what's going on on Twitter. Hey, I got retweeted...
Wednesday, January 6, 2016
Wednesday, December 30, 2015
This post is a quick look at one of my favorite features in Git, interactive rebases. I like this feature because it lets you do two conflicting things: make micro commits (like saving every couple of minutes when editing a Word doc) so you can replay your work, and always go back to a working state of your code, and making clean, well worded, self contained commits to a project repo. Interactive rebasing lets you squish your commits together when you are ready to share them.