QUTE looks, er, cute
Essentially it is an evolution of his utPLSQL API. I love utPLSQL: it's a major contribution to code safety and I never understood why more people didn't use it. Perhaps everybody else always gets things right first time. I see there is a function so we can import our existing utPLSQL tests into QUTE. Unfortunately this hasn't worked for the two suites I've tried it with. I think this feature is an important one as I don't want to have to bounce between two different testing tools.
My main reservation is that when the program failed with a PLS-6502 error QUTE crashed and had to be re-started. I don't think that is very friendly. My other concern is more philosophical: QUTE isn't Test First. By its very nature we have to have a program unit signature before we can code a test. But once over that hump I'm sure we can get into a more Test Driven cycle.
Steven is still not certain about the roadmap yet. But he stated on the utPLSQL forum that QUTE will remain free for the foreseeable future. And as QUTE offers the ability to generate utPLSQL test suites we will retain our investment in the tests whatever he eventually decides.
At the moment QUTE is beta and there's plenty of room for improvement but I still think everybody ought to start using it now. Don't Google for it (Qute is the name of a FireFox icon set and several other things): download it from here.
I downloaded QUTE r3 last night and they've fixed the utPLSQL import bugs. Hurrah!