This is obvious, but differences between environments cause problems. You can expect bugs to cluster around them.
Continue reading “Differences cause problems”
As I said earlier, I’ve been reading Michael Feathers _Working Effectively With Legacy Code_ recently (I’m taking my time with it; it’s a good book). He spends a lot of time talking about techniques to get code under test. However, he spends very little talking about finding out if (and to what extent) a method is under test in the first place. So here’s how I do it:
Continue reading “How do I find what tests use this method?”
Been seeing this pattern a lot today. I’m working with integration tests, which have a lot of test fixtures around to do common tasks (such as inserting data into the database). These test fixtures propagate exceptions. In many cases, they simply declare that they throw java.lang.Exception. Ouch.
Continue reading “Don’t propagate exceptions in test fixtures”
A neat little Eclipse plugin I’m playing with at the moment is the Continuous Testing Plugin for Eclipse The basic purpose of this plugin is to run your tests (or a selected subset) as part of the build cycle in Eclipse.
Continue reading “Automated Test Running”
No, it’s not an exercise craze (though I do want to get serious about losing weight soon). I’m talking about the FIT acceptance test harness. I looked into it recently, and this (rather extended) post describes what I found out.
Continue reading “Getting FIT”
I’m sick of the term “performance testing”. It misses the point.
Continue reading “Sick of “Performance Testing””