Thanks for your reply. You're right, my module is documented rather poorly. I'll be fixing that, but to briefly clarify here, the module has little to do with cfengine, aside from the fact that I use it to test my cfengine config on a staging server, before pushing it out to production.

As for check_package and file_contains, they check that a package exists and that a file's contents match a regexp, respectively. They call ok() (as in Test::Builder::Module's ok())

The failed test was a silly oversight on my part. I'd forgotten that some systems don't use dpkg and apt :). I'll have it skip that test on non-dpkg systems.

I've fixed the tests to work correctly on a non-dpkg system and clarified the docs quite a bit (I think :). Here is the fixed version. The Sys:: namespace seems like a good idea; I'm thinking something like Sys::ConfigTest... will ponder that for a bit.

Thanks again for taking the time to review this, and the great advice. ++.