pgTAP 0.20 Infiltrates PostreSQL Community

I did all I could to stop it, but it just wasn't possible. pgTAP 0.20 has somehow made its way from my Subversion server and infiltrated the PostgreSQL community. Can nothing be done to stop this menace? Its use leads to cleaner, more stable, and more-safely refctored code. This insanity

test harness presentation layer plugins

I'm mostly sending this email because I had an idea, and it's late, and I don't want to forget. Today it occured to me that many Test:: extensions are more about better diagnostic output than better test comparison. This stinks: want: foo bar have: foo bar So you write some plugin that