I'm currently writing a deploy script for an website.
As I'm writing it, it has occurred to me that I always want to check as I'm going that everything has happened correctly, that I want to print output for each step, and that ideally I'd like to be able to automatically run the deploy script and know that it worked on.
And ideally I need these things for every general administration type script that I write.
It seems to me that the features of TAP and Test::More combined (the ability to be both human and machine-readable and the ability to conveniently test as I go along) are almost ideal for writing these sorts of deploy scripts.
Not so much for the parts involving automated rollback and notification, but certainly the actual linear process for the deployment process.
The only difference would be that I want automatic BAIL_OUT if any test fails, because it's not safe to continue.
I'd be interested in people's thoughts about this sort of non-testing use of TAP/Test::More/etc.
Adam K
