apache::testutil.3

视频监控网络部分的协议ddns,的模块的实现代码,请大家大胆指正.

.Vb 1
\&  t_write_file($filename, @lines);
.Ve
.Sp
\&\fIt_write_file()\fR creates a new file at \fI\f(CI$filename\fI\fR or overwrites the
existing file with the content passed in \fI\f(CI@lines\fI\fR. If only the
\&\fI\f(CI$filename\fI\fR is passed, an empty file will be created.
.Sp
If parent directories of \f(CW$filename\fR don't exist they will be
automagically created.
.Sp
The generated file will be automatically deleted at the end of the
program's execution.
.Sp
This function is exported by default.
.IP "\fIt_append_file()\fR" 4
.IX Item "t_append_file()"
.Vb 1
\&  t_append_file($filename, @lines);
.Ve
.Sp
\&\fIt_append_file()\fR is similar to \fIt_write_file()\fR, but it doesn't clobber
existing files and appends \f(CW@lines\fR to the end of the file. If the
file doesn't exist it will create it.
.Sp
If parent directories of \f(CW$filename\fR don't exist they will be
automagically created.
.Sp
The generated file will be registered to be automatically deleted at
the end of the program's execution, only if the file was created by
\&\fIt_append_file()\fR.
.Sp
This function is exported by default.
.IP "\fIt_write_shell_script()\fR" 4
.IX Item "t_write_shell_script()"
.Vb 1
\&  Apache::TestUtil::t_write_shell_script($filename, @lines);
.Ve
.Sp
Similar to \fIt_write_file()\fR but creates a portable shell/batch
script. The created filename is constructed from \f(CW$filename\fR and an
appropriate extension automatically selected according to the platform
the code is running under.
.Sp
It returns the extension of the created file.
.IP "\fIt_write_perl_script()\fR" 4
.IX Item "t_write_perl_script()"
.Vb 1
\&  Apache::TestUtil::t_write_perl_script($filename, @lines);
.Ve
.Sp
Similar to \fIt_write_file()\fR but creates a executable Perl script with
correctly set shebang line.
.IP "\fIt_open_file()\fR" 4
.IX Item "t_open_file()"
.Vb 1
\&  my $fh = t_open_file($filename);
.Ve
.Sp
\&\fIt_open_file()\fR opens a file \fI\f(CI$filename\fI\fR for writing and returns the
file handle to the opened file.
.Sp
If parent directories of \f(CW$filename\fR don't exist they will be
automagically created.
.Sp
The generated file will be automatically deleted at the end of the
program's execution.
.Sp
This function is exported by default.
.IP "\fIt_mkdir()\fR" 4
.IX Item "t_mkdir()"
.Vb 1
\&  t_mkdir($dirname);
.Ve
.Sp
\&\fIt_mkdir()\fR creates a directory \fI\f(CI$dirname\fI\fR. The operation will fail if
the parent directory doesn't exist.
.Sp
If parent directories of \f(CW$dirname\fR don't exist they will be
automagically created.
.Sp
The generated directory will be automatically deleted at the end of
the program's execution.
.Sp
This function is exported by default.
.IP "\fIt_rmtree()\fR" 4
.IX Item "t_rmtree()"
.Vb 1
\&  t_rmtree(@dirs);
.Ve
.Sp
\&\fIt_rmtree()\fR deletes the whole directories trees passed in \fI\f(CI@dirs\fI\fR.
.Sp
This function is exported by default.
.IP "\fIt_chown()\fR" 4
.IX Item "t_chown()"
.Vb 1
\&  Apache::TestUtil::t_chown($file);
.Ve
.Sp
Change ownership of \f(CW$file\fR to the test's \fIUser\fR/\fIGroup\fR.  This
function is noop on platforms where \fIchown\fR\|(2) is unsupported
(e.g. Win32).
.IP "\fIt_is_equal()\fR" 4
.IX Item "t_is_equal()"
.Vb 1
\&  t_is_equal($a, $b);
.Ve
.Sp
\&\fIt_is_equal()\fR compares any two datastructures and returns 1 if they are
exactly the same, otherwise 0. The datastructures can be nested
hashes, arrays, scalars, undefs or a combination of any of these.  See
\&\fIt_cmp()\fR for an example.
.Sp
If \f(CW$b\fR is a regex reference, the regex comparison \f(CW\*(C`$a =~ $b\*(C'\fR is
performed. For example:
.Sp
.Vb 1
\&  t_is_equal($server_version, qr{^Apache});
.Ve
.Sp
If comparing non-scalars make sure to pass the references to the
datastructures.
.Sp
This function is exported by default.
.IP "\fIt_server_log_error_is_expected()\fR" 4
.IX Item "t_server_log_error_is_expected()"
If the handler's execution results in an error or a warning logged to
the \fIerror_log\fR file which is expected, it's a good idea to have a
disclaimer printed before the error itself, so one can tell real
problems with tests from expected errors. For example when testing how
the package behaves under error conditions the \fIerror_log\fR file might
be loaded with errors, most of which are expected.
.Sp
For example if a handler is about to generate a run-time error, this
function can be used as:
.Sp
.Vb 8
\&  use Apache::TestUtil;
\&  ...
\&  sub handler {
\&      my $r = shift;
\&      ...
\&      t_server_log_error_is_expected();
\&      die "failed because ...";
\&  }
.Ve
.Sp
After running this handler the \fIerror_log\fR file will include:
.Sp
.Vb 2
\&  *** The following error entry is expected and harmless ***
\&  [Tue Apr 01 14:00:21 2003] [error] failed because ...
.Ve
.Sp
When more than one entry is expected, an optional numerical argument,
indicating how many entries to expect, can be passed. For example:
.Sp
.Vb 1
\&  t_server_log_error_is_expected(2);
.Ve
.Sp
will generate:
.Sp
.Vb 1
\&  *** The following 2 error entries are expected and harmless ***
.Ve
.Sp
If the error is generated at compile time, the logging must be done in
the \s-1BEGIN\s0 block at the very beginning of the file:
.Sp
.Vb 5
\&  BEGIN {
\&      use Apache::TestUtil;
\&      t_server_log_error_is_expected();
\&  }
\&  use DOES_NOT_exist;
.Ve
.Sp
After attempting to run this handler the \fIerror_log\fR file will
include:
.Sp
.Vb 3
\&  *** The following error entry is expected and harmless ***
\&  [Tue Apr 01 14:04:49 2003] [error] Can\*(Aqt locate "DOES_NOT_exist.pm"
\&  in @INC (@INC contains: ...
.Ve
.Sp
Also see \f(CW\*(C`t_server_log_warn_is_expected()\*(C'\fR which is similar but used
for warnings.
.Sp
This function is exported by default.
.IP "\fIt_server_log_warn_is_expected()\fR" 4
.IX Item "t_server_log_warn_is_expected()"
\&\f(CW\*(C`t_server_log_warn_is_expected()\*(C'\fR generates a disclaimer for expected
warnings.
.Sp
See the explanation for \f(CW\*(C`t_server_log_error_is_expected()\*(C'\fR for more
details.
.Sp
This function is exported by default.
.IP "\fIt_client_log_error_is_expected()\fR" 4
.IX Item "t_client_log_error_is_expected()"
\&\f(CW\*(C`t_client_log_error_is_expected()\*(C'\fR generates a disclaimer for
expected errors. But in contrast to
\&\f(CW\*(C`t_server_log_error_is_expected()\*(C'\fR called by the client side of the
script.
.Sp
See the explanation for \f(CW\*(C`t_server_log_error_is_expected()\*(C'\fR for more
details.
.Sp
For example the following client script fails to find the handler:
.Sp
.Vb 3
\&  use Apache::Test;
\&  use Apache::TestUtil;
\&  use Apache::TestRequest qw(GET);
\&  
\&  plan tests => 1;
\&  
\&  t_client_log_error_is_expected();
\&  my $url = "/error_document/cannot_be_found";
\&  my $res = GET($url);
\&  ok t_cmp(404, $res\->code, "test 404");
.Ve
.Sp
After running this test the \fIerror_log\fR file will include an entry
similar to the following snippet:
.Sp
.Vb 3
\&  *** The following error entry is expected and harmless ***
\&  [Tue Apr 01 14:02:55 2003] [error] [client 127.0.0.1] 
\&  File does not exist: /tmp/test/t/htdocs/error
.Ve
.Sp
When more than one entry is expected, an optional numerical argument,
indicating how many entries to expect, can be passed. For example:
.Sp
.Vb 1
\&  t_client_log_error_is_expected(2);
.Ve
.Sp
will generate:
.Sp
.Vb 1
\&  *** The following 2 error entries are expected and harmless ***
.Ve
.Sp
This function is exported by default.
.IP "\fIt_client_log_warn_is_expected()\fR" 4
.IX Item "t_client_log_warn_is_expected()"
\&\f(CW\*(C`t_client_log_warn_is_expected()\*(C'\fR generates a disclaimer for expected
warnings on the client side.
.Sp
See the explanation for \f(CW\*(C`t_client_log_error_is_expected()\*(C'\fR for more
details.
.Sp
This function is exported by default.
.IP "t_catfile('a', 'b', 'c')" 4
.IX Item "t_catfile('a', 'b', 'c')"
This function is essentially \f(CW\*(C`File::Spec\->catfile\*(C'\fR, but
on Win32 will use \f(CW\*(C`Win32::GetLongpathName()\*(C'\fR to convert the
result to a long path name (if the result is an absolute file).
The function is not exported by default.
.IP "t_catfile_apache('a', 'b', 'c')" 4
.IX Item "t_catfile_apache('a', 'b', 'c')"
This function is essentially \f(CW\*(C`File::Spec::Unix\->catfile\*(C'\fR, but
on Win32 will use \f(CW\*(C`Win32::GetLongpathName()\*(C'\fR to convert the
result to a long path name (if the result is an absolute file).
It is useful when comparing something to that returned by Apache,
which uses a Unix-style specification with forward slashes for
directory separators. The function is not exported by default.
.SH "AUTHOR"
.IX Header "AUTHOR"
Stas Bekman <[e-mail]>
.SH "SEE ALSO"
.IX Header "SEE ALSO"
\&\fIperl\fR\|(1)