stas 01/12/27 03:10:04
Modified: pod modperl_dev.pod
Log:
'make test' features now all live in the writing_tests document
Revision Changes Path
1.49 +2 -98 modperl-2.0/pod/modperl_dev.pod
Index: modperl_dev.pod
===================================================================
RCS file: /home/cvs/modperl-2.0/pod/modperl_dev.pod,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -r1.48 -r1.49
--- modperl_dev.pod 2001/12/27 09:23:14 1.48
+++ modperl_dev.pod 2001/12/27 11:10:04 1.49
@@ -206,104 +206,8 @@
=head1 'make test' Features
-=head2 What Test Options are Available
-
-Run:
-
- % ./t/TEST -help
-
-to get the list of options you can use during testing
-
-=head2 'make test' Debug
-
-mod_perl-2.0 provides built in 'make test' debug facility. So in case
-you get a core dump during make test, or just for fun, run in one shell:
-
- % ./t/TEST -debug
-
-in another shell:
-
- % ./t/TEST -run
-
-then the I<-debug> shell will have a (gdb) prompt, type 'where' for
-stacktrace.
-
-You can change the default debugger by supplying the name of the
-debugger as an argument to I<-debug>. E.g. to run the server under
-C<ddd>:
-
- % ./t/TEST -debug=ddd
-
-=head2 Advanced Debugging
-
-If you debug mod_perl internals you can set the breakpoints using the
-I<-breakpoint> option, which can be repeated as many times as
-needed. When you set at least one breakpoint, the server will start
-running till it meets the I<ap_run_pre_config> breakpoint. At this
-point we can set the breakpoint for the mod_perl code, something we
-cannot do earlier if mod_perl was built as DSO. For example:
-
- % ./t/TEST -debug -breakpoint=modperl_cmd_switches \
- -breakpoint=modperl_cmd_options
-
-will set the I<modperl_cmd_switches> and I<modperl_cmd_options>
-breakpoints and run the debugger.
-
-If you want to tell the debugger to jump to the start of the mod_perl
-code you may run:
-
- % ./t/TEST -debug -breakpoint=modperl_hook_init
-
-In fact I<-breakpoint> automatically turns on the debug mode, so you
-can run:
-
- % ./t/TEST -breakpoint=modperl_hook_init
-
-
-=head2 Running Individual Tests
-
-Run a single test:
-
- % ./t/TEST protocol/echo.t
-
-The server will be stopped if it was already running and a new one
-will be started before running the I<t/protocol/echo.t> test. At the
-end of the test the server will be shut down.
-
-You can run groups of tests at once.
-
- % ./t/TEST modules protocol/echo.t
-
-will run all the tests in I<t/modules/> directory, followed by
-I<t/protocol/echo.t> test.
-
-=head2 Repeating the Tests
-
-By default when you run the test without I<-run-tests> option, the
-server will be started before the testing and stopped at the end. If
-during a debugging process you need to re-run tests without a need to
-restart the server, you can start the server once:
-
- % ./t/TEST modules -start-httpd
-
-and then run the test(s) with I<-run-tests> option many times:
-
- % ./t/TEST -run-tests protocol/echo
-
-without waiting for the server to restart.
-
-When you are done with tests shutdown the server:
-
- % ./t/TEST modules -stop-httpd
-
-=head2 Verbose Testing
-
-By default print() statements in the test script are filtered out by
-C<Test::Harness>. if you want the test to print what it does (if you
-decide to debug some test) use C<-verbose> option:
-
- % t/TEST -verbose protocol/echo.t
-
+L<../writing_tests/writing_tests.pod> document covers the C<make test>
+suite.
=head1 mod_perl configuration directives
