I was just working on this myself the other day, and I took a look at Storable and HTML::Embperl, if I remember correctly. They were helpful for getting down the basics of *how* to do it.

It sounds more like your question might be *what* to do, though, ie. what exactly you should be testing. Perhaps? The most important reason for having a test suite, I think, is that it should test every important piece of your system. This allows for:

• Easy portability testing; you have a defined set of tests that you can run on different platforms. If some fail, you know what you need to work on.
• Version maintenance. If someone makes a change to the system, and it breaks a test when you next run the test suite, you know which change caused the problem, and where it broke in the test suite. This is very good for you, because you now have a better sense of what to fix.

I realize that this isn't very specific, but really the specifics all deal with your particular system.