File Coverage

blib/lib/Test/Server.pm

Criterion	Covered	Total	%
statement	6	8	75.0
branch			n/a
condition	0	2	0.0
subroutine	2	3	66.6
pod	1	1	100.0
total	9	14	64.2

package Test::Server;

=head1 NAME

Test::Server - what about test driven administration?

=head1 SYNOPSIS

	cp -r examples /etc/t
	cd /etc/t
	vim test-server.yaml
	prove /etc/t

	use Test::Server;
	Test::Server->run();

=head1 DESCRIPTION

Ever heard of test driven development? What about test driven administration?
Take a look around F folder for example tests that you can run
agains your server.

The general configuration should be done through the F and should
be managable by any non Perl awear admin (are there any?). Of course you are free to
put any other test that make sence for your server.

The idea behind this is following: You run C and everything is
fine. Server is up and running. Life is nice. Then somebody calls you at 3am...
Oups! What went wrong? You login to the server (if possible of course) and run
the C friend. Something failed? => fix it. Nothing failed?
=> write a test that will reveal that something is wrong && fix the problem
of course ;). And then at 6am go happily to sleep again...

To be the administration really test drive ;) you should be writing your tests
before you install the server...

Any other benefits? What about migration || reinstalation of the server? Do you
always remember what services || purpouses is the server used for? You just
C the F folder to the new machine and C will tell
you. If not you'll write a test ;).

Or are you writing firewall rules and need to check if you didn't close some
ports that you should not? Check out the F<03_open-ports.t>.

I hope you'll enjoy the idea as I do. (until I find that there are 30 other
similar solutions like this...)

=cut

use warnings;
use strict;

our $VERSION = '0.06';

=head1 METHODS

=head2 run()

For the moment just runs C. Any other better idea?

=cut

sub run {
	my $class = shift;

	system('prove', shift || '/etc/t');
}

1;


__END__