An alternative is the Aegis change management system. Aegis uses a very different model than CVS, although it can be configured to use RCS as its underlying source code control system, in much the same way that CVS wraps the RCS functionality. Aegis manages and enforces testing conventions in very much the way you describe--that is, it can run tests with references to copies of things already checked in to the repository. It does more for you, although you have to buy into its model of the development cycle. If you do, though, it's very powerful.

Setting up Aegis for Perl module development is a little tricky, but a solved problem. (Recently, Michael G. Schwern has started using it for module development.) I'd be happy to assist anyone who wants to give it a try.