Software is too expensive to build cheaply...

Fujitsu is going to roll out trolleys with scanners so that shoopers can avoid the checkout queue. Naturally, this assumes a degree of honesty on the part of the shoppers. What's amusing about this is how they plan to "trust, but verify".

This has been said before, I know, but it's worth re-iterating: a test should test one thing, and one thing only.

First, some scope definition. Using Kent Beck's terminology, I'm talking about developer tests, not acceptance tests. Also, by one thing, I mean that there should be only one thing that breaks the test (which is very different from saying any failure should only break one test...). In addition, the one thing that breaks should provide diagnostic information - a test failure shouldn't leave you scratching your head to determine the immediate cause

In Google for Robert Watkins. Yay!

Earlier, I wrote about testing only one thing at a time. A little one-liner I tossed out in that was using text files to load object graphs in your test cases. I thought I'd elaborate on that a bit more.