> -----Original Message----- > From: Nik Clayton [mailto:[EMAIL PROTECTED] > Sent: 05 July 2005 14:13 > To: perl-qa@perl.org > Subject: [ANNOUNCE] Test::Symlink > > > * Replies will be sent through Spamex to [EMAIL PROTECTED] > * For additional info click -> http://www.spamex.com/i/?v=6889066 > > <quote> > The uploaded file > > Test-Symlink-0.01.tar.gz > > has entered CPAN as > > file: $CPAN/authors/id/N/NI/NIKC/Test-Symlink-0.01.tar.gz > size: 4123 bytes > md5: 9a3797b3d94c3ad73b061bd7b1aa2134 > </quote> > > Test::Symlink is the first in a series of modules that I'm writing. > They differ from many of the modules in the Test:: namespace in that > instead of being intended for testing code they are designed to help > test the environment in which the code will be run. > > This is to solve a business requirement I have involving > auditing some > servers to verify that they have been built according to a particular > documented standard. The intention is that a series of test scripts > will be written that enforce the standard, and the output > from the test > scripts will then provide sufficient evidence that the > servers have been > built correctly. > > By automatically running these tests on a regular basis we can ensure > that any deviations from the standard that are inadvertently > introduced > can be quickly identified and corrected. > > This isn't, in itself, a particularly new concept. Tools > like tripwire > and so forth provide similar functionality. But > Test::Harness, related > tools like prove(1), as well as many of the Test::* modules, are an > attractive base to build on.
I have a concern on this relating to portability. How will the module behave on platforms that don't have symlinks? Sorry if this is documented - the module hasn't reached search.cpan.org for me yet.
