This week amidst all the crazy airline flight cancellations and my own pending flight to the Software Test & Performance Conference, I received an erroneous email from a large airline carrier.

I had already booked a flight with a major airline that was cancelling flights so I looked at flights from an alternate carrier and put a second flight on a 24 hour hold. I didn’t end up buying the ticket and the hold request expired as it should have. However the hold ticket generated an “easy online check-in email.” Mmm, feels like a missed regression test.

Tomorrow (Tuesday 15th April 2008), I'll be at Extreme Tuesdays Club at the Counting House.

If you want to chat about testing on Agile projects, Test Driven Development or just like beer and pie then do come along.

Given the sheer number of things that can go wrong on a software project, isn't it amazing how it always seems to be the same kinds of screw-ups pretty much every time?

New Pylot 1.1 release is available
Visit: www.pylot.org/download.html

It contains some minor code cleanup and a new test case recorder contributed by David Solomon. The recorder works with Windows and IE only.

It is a script that launches your web browser and records HTTP requests as you navigate. While it records, it prints Pylot's XML test cases. The test cases are printed to STDOUT, so just redirect it to a file and you will have a valid testcases.xml file to use as Pylot input.

Recently I’ve found my (sever years old) presentations with a lot of defect metrics and analysis. Only one slide I am proud of still – the percentage of “cancelled” bugs (drilled-down to percentage of reject reason: duplicated, not repeatable, etc.). What I like about this measure that it is direct – I’m really interested to keep the number of rejected bugs low – yes I’m interested in testers not reporting them in the first place.