William McKee wrote:
On Fri, Mar 12, 2004 at 08:06:05PM -0800, Stas Bekman wrote:
Via wrappers, of course. In which case you should write several general
purpose modules put them under project/lib (or some special lib under
project/t) and then write the wrappers (.pl for mod_cgi, .pm for
Stas Bekman wrote:
William McKee wrote:
On Fri, Mar 12, 2004 at 08:06:05PM -0800, Stas Bekman wrote:
Via wrappers, of course. In which case you should write several
general purpose modules put them under project/lib (or some special
lib under project/t) and then write the wrappers (.pl for
On Mon, Mar 15, 2004 at 07:12:02PM -0800, Stas Bekman wrote:
Please try the current cvs, it should die on you much earlier if you use
the wrong Apache::TestRun subclass, with a useful error message as you have
suggested.
Well, I can't compile anything under Windows, so I cannot rebuild
William McKee wrote:
On Mon, Mar 15, 2004 at 06:25:27PM -0800, Stas Bekman wrote:
No, that's not fine. I've misread the code. Apache::TestRunPerl requires
mod_perl. I'm updating the docs. You need to use Apache::TestRun if you
don't want to run mod_perl.
Excellent. Using TestRun simply skips
William McKee wrote:
On Mon, Mar 15, 2004 at 07:12:02PM -0800, Stas Bekman wrote:
Please try the current cvs, it should die on you much earlier if you use
the wrong Apache::TestRun subclass, with a useful error message as you have
suggested.
Well, I can't compile anything under Windows, so I
On Tue, Mar 16, 2004 at 10:02:31AM -0800, Stas Bekman wrote:
I think all is needed is a good clear documentation. And
Apache::TestRunPerl will now tell you if you try to use it w/o having
mod_perl.
I would think that those two steps should be sufficient.
-Wm
--
Knowmad Services Inc.
On Fri, Mar 12, 2004 at 05:26:05PM -0800, Stas Bekman wrote:
I suspect that you are subclassing ModPerl::TestRun instead of
Apache::TestRun. The former requires mod_perl, the latter doesn't not.
ModPerl::TestRun is a subclass of Apache::TestRun
This would be in the TEST.PL file, right? Here's
William McKee wrote:
On Fri, Mar 12, 2004 at 05:26:05PM -0800, Stas Bekman wrote:
I suspect that you are subclassing ModPerl::TestRun instead of
Apache::TestRun. The former requires mod_perl, the latter doesn't not.
ModPerl::TestRun is a subclass of Apache::TestRun
This would be in the TEST.PL
On Fri, Mar 12, 2004 at 07:18:38PM -0800, Stas Bekman wrote:
No, that's fine. I should have looked at Apache/TestConfigPerl.pm line
486. It runs that code if you have mod_perl tests. i.e. response module
t/response/TestFoo/Bar.pm.
Does this mean that A::T cannot run response tests w/o
On Fri, Mar 12, 2004 at 07:43:15PM -0800, Stas Bekman wrote:
It certainly can be patched not to do so. But I don't response handlers can
be useful for anything else besides mod_perl. It'd help if you'd have
explained what are you try to test. mod_cgi?
Sorry, here's the background. I've
William McKee wrote:
On Fri, Mar 12, 2004 at 07:43:15PM -0800, Stas Bekman wrote:
It certainly can be patched not to do so. But I don't response handlers can
be useful for anything else besides mod_perl. It'd help if you'd have
explained what are you try to test. mod_cgi?
Sorry, here's the
On Fri, Mar 12, 2004 at 08:06:05PM -0800, Stas Bekman wrote:
Via wrappers, of course. In which case you should write several general
purpose modules put them under project/lib (or some special lib under
project/t) and then write the wrappers (.pl for mod_cgi, .pm for mod_perl)
and put those
12 matches
Mail list logo
