in reply to using Test::* modules for generic testing of non perl stuff?

At work I have used Test::More and family to build a framework for unit testing an application server + business logic modules.

It involved making xml calls to the server and see that the correct values are returned, and that the database contents changes accordlingly.

For this I wrote a generic Perl client to call the application server, Test::More for the returned values and Test::DatabaseRow for testing the database. The rest looks like any ordinary .t script.

This iterative, low ceremony setup proved to be orders of magnitude more productive than writing unit tests in C++.