ok, here we go :)
I have a preliminary implementation. what happens now is that two files are
autogenerated if they don't already exist:
t/server-start.t
t/server-stop.t
they are used to control the starting and stopping of the server. so, the
output of make test looks like
# writing file:
anyway, so that's how it looks on the outside. on the inside is another
matter...
ok, I see at least one problem already - if the server doesn't start
(missing APXS or whatnot) the tests continue (and obviously fail).
I've been playing all afternoon with 'Bail out!' but it seems that when
OK, here is an idea how to solve it. instead of starting and stopping
the server by t/TEST delegate it to a specially designed tests. So the
last test in t/pre-start/ will start the server and the first test in
t/post-stop/ will stop the server. Both can be autogenerated. Of course
this will
The only issue is with Test::Harness, we will need to somehow feed tests
to it so it'll take them all as one bunch, while we have to run first
t/pre-start/ test, followed by normal tests, followed by t/post-stop/
tests.
oh, I see the issue now.
if we call TestRun::run_tests multiple times,
Geoffrey Young wrote:
The only issue is with Test::Harness, we will need to somehow feed
tests to it so it'll take them all as one bunch, while we have to run
first t/pre-start/ test, followed by normal tests, followed by
t/post-stop/ tests.
oh, I see the issue now.
if we call
hi all...
I'm thinking about implementing a mechansim that allows you to run certain
tests after the server shuts down. the rationale behind this is some work
I'm doing on Devel::Profiler::Apache - the profiler generates statistics
when the children die off, so I need to either kill the
