Geoffrey Young wrote:
bugger. if the bloody package continues running through the rest of
the tests even after encountering a failure -- which is right, and what
it does -- it should use a uniform report syntax and most certainly *not*
conceal details about the totals.. :-(
I can't say
so, it looks like an issue with your wrapper and not A-T
core, yes?
no. if i run only a test script that passes completely, i get
t/modules/accessok
All tests successful.
Files=1, Tests=408, 4 wallclock secs ( 3.13 cusr + 0.43 csys = 3.56 CPU)
if i run only a script that fails,
Geoffrey Young wrote:
hmm, I get the following with 5.8.3
t/protocol/nntp-like...ok
t/ssl/all..skipped
all skipped: cannot find module 'mod_ssl', cannot find module
'LWP::Protocol::https'
All tests successful, 7 tests and 14 subtests skipped.
Files=42,
t/modules/expires.t924 4.35% 13 21 33 45
14 subtests skipped.
and that's it.
oh, I see what you mean, you're missing the
Failed 1/1 test scripts, 0.00% okay. 1/1 subtests failed, 0.00% okay.
line.
are you using an older version of perl perhaps?
yep,
Geoffrey Young wrote:
t/modules/expires.t924 4.35% 13 21 33 45
14 subtests skipped.
and that's it.
oh, I see what you mean, you're missing the
Failed 1/1 test scripts, 0.00% okay. 1/1 subtests failed, 0.00% okay.
line.
actuall, what i'm missing (and
in my case, it's possibly my wrapper that's gobbling the line. for
pity's sake, why it that going to stderr when everything else is going to
stdout?
erk. now i'm seeing it, but *only* if all of the tests are successful.
i need to see it regardless, and including the
Rodent of Unusual Size wrote:
2. t/SKIP (which i haven't used for a long time) seems to have changed
behaviour. for instance, t/php runs regardless of whether i have
'php' or 't/php' or anything else mentioning it in t/SKIP. what is
the method nowadays to get a test script
Rodent of Unusual Size wrote:
it looks as though the attached patch will fix this regression.. but
is it the appropriate solution?
der! would help if i attached it, wouldn't it..
--
#kenP-)}
Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/
Author, developer, opinionist
-$file ||= 'SKIP';
+$file ||= 't/SKIP';
excellent, thanks for tracking that down.
we just need to be a bit more platform independent. if you could verify
that the attached patch works ok for you, I'll commit it.
--Geoff
Index: lib/Apache/TestHarness.pm
1. is it possible to run the suite *without* doing a 'make install'?
in my development environment i discovered that i had to do that
in order oget rid of some cruft left behind from having done a
'make install' in the past. however, i'd prefer to not have to
force the
-$file ||= 'SKIP';
+$file ||= catfile Apache::Test::vars('serverroot'), 'SKIP';
oops. forgot to add the class up top. guess I'm not quite with it today yet :)
--Geoff
Index: lib/Apache/TestHarness.pm
===
RCS file:
Geoffrey Young wrote:
-$file ||= 'SKIP';
+$file ||= 't/SKIP';
excellent, thanks for tracking that down.
we just need to be a bit more platform independent. if you could verify
that the attached patch works ok for you, I'll commit it.
Index: lib/Apache/TestHarness.pm
-$file ||= 'SKIP';
+$file ||= catfile Apache::Test::vars('serverroot'), 'SKIP';
Geoff, you are making a good point of removing the hardcoding of t/
towards the idea of being able to split the test suite.
well, it's an idea that we're all working toward, yourself included :)
Geoffrey Young wrote:
-$file ||= 'SKIP';
+$file ||= catfile Apache::Test::vars('serverroot'), 'SKIP';
Geoff, you are making a good point of removing the hardcoding of t/
towards the idea of being able to split the test suite.
well, it's an idea that we're all working toward, yourself
14 matches
Mail list logo
