(For the purposes of this discussion, I will call the module Test::Sysconfig, but the name is by no means final).
Test::Sysconfig is a module that provides functions for system configuration related tests. (At the moment, there are two functions: Check for a file which has contents matching a specified regex, and check that a package is installed (with dpkg, though I plan to add support for RPM. Patches welcome for others). My site's use for this module is unit testing cfengine configuration.
Aside from the obligatory (and welcome) comments/criticism, I have a few queries.
First, I'm not sure if this module belongs in the Test:: namespace (although I'm not sure where else to put it). It seems that the Test:: namespace is for testing code, and while my module is based on those in Test::*, it does not test code. In short, does my module belong in Test::? If not, where?
Also, (especially if you use cfengine), what else would you like to see in this module? I'm thinking about adding support for testing links, permissions/ownership, and directories.
Test::Sysconfig lives, for the moment, at http://iank.org/files/Test-Sysconfig-0.01.tar.gz.
In reply to RFC: Test::Sysconfig by jagh
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |