![]() |
![]()
| ![]() |
![]()
NAMEApache::TestConfig -- Test Configuration setup moduleSYNOPSISuse Apache::TestConfig; my $cfg = Apache::TestConfig->new(%args) my $fh = $cfg->genfile($file); $cfg->writefile($file, $content); $cfg->gendir($dir); ... DESCRIPTION"Apache::TestConfig" is used in creating the "Apache::Test" configuration files.FUNCTIONS
Environment VariablesThe following environment variables affect the configuration and the run-time of the "Apache::Test" framework:APACHE_TEST_COLORTo aid visual control over the configuration process and the run-time phase, "Apache::Test" uses coloured fonts when the environment variable "APACHE_TEST_COLOR" is set to a true value.APACHE_TEST_LIVE_DEVWhen using "Apache::Test" during the project development phase, it's often convenient to have the project/lib (live) directory appearing first in @INC so any changes to the Perl modules, residing in it, immediately affect the server, without a need to rerun "make" to update blib/lib. When the environment variable "APACHE_TEST_LIVE_DEV" is set to a true value during the configuration phase ("t/TEST -config", "Apache::Test" will automatically unshift the project/lib directory into @INC, via the autogenerated t/conf/modperl_inc.pl file.Special PlaceholdersWhen generating configuration files from the *.in templates, special placeholder variables get substituted. To embed a placeholder use the "@foo@" syntax. For example in extra.conf.in you can write:Include @ServerRoot@/conf/myconfig.conf When extra.conf is generated, "@ServerRoot@" will get replaced with the location of the server root. Placeholders are case-insensitive. Available placeholders: Configuration OptionsAll configuration variables that can be passed to "t/TEST", such as "MaxClients", "DocumentRoot", "ServerRoot", etc. To see the complete list run:% t/TEST --help and you will find them in the "configuration options" sections. NextAvailablePortEvery time this placeholder is encountered it'll be replaced with the next available port. This is very useful if you need to allocate a special port, but not hardcode it. Later when running:% t/TEST -port=select it's possible to run several concurrent test suites on the same machine, w/o having port collisions. AUTHORSEE ALSOperl(1), Apache::Test(3)
|