Category Archives: testing

I tweeted this a few minutes ago: This is in reference to a horrible test that I wrote today. It’s got 2 assertions and more than 20 lines of context to set up the mocks that I needed, to isolate … Continue reading →

Several of the reports that the app that Joey and I are working on will be generated via HAML to be displayed in the app, for the users. The generated content will end up being HTML, but starts it’s life … Continue reading →

I’m using Watchr in my current Rails 3 project, instead of Autotest, to run my Cucumber and RSpec tests whenever I save a file. It makes life so much easier than having to manually run them. Yesterday, I decided to … Continue reading →

It has been almost a month since I ventured out into contracting and took up OSX on a Macbook Pro as my primary operating system. In that time, I’ve been very fortunate to have Joey Beninghove guide me through the … Continue reading →

Mark Ploeh has an interesting post about interfaces in TDD – that interfaces aren’t necessarily abstractions.  That’s certainly true.   Interfaces don’t guarantee we’re actually following SOLID design principles.  In fact, the whole idea of the typical repository pattern in a … Continue reading →

There was a bit of interesting discussion on twitter this morning, concerning the cost of test-first vs. risk. Here’s the visual version of what I’m saying: The premise behind the value of test-first is that we will wash out (or … Continue reading →

For about 3 years, I wrote absolutely horrible UI tests.  These tests worked great for a while, but like most people that tried their hands at UI tests, found them to be utterly brittle and unmaintainable in the face of … Continue reading →

On a recent large project, we had a goal early on that we didn’t want to have a lot of QA folks manually testing our software.  Finding bugs through manual testing is incredibly time consuming and expensive, so we opted … Continue reading →