Geoffrey Young wrote:
[...]
I'd like to second Geoff comments on the fact that it's a complex stuff. And
we are here to help. And you are here to remember/write down all the unclear
things and help improve the docs so the next time you need to do it again
it'll be all milk chocolate sweety.
if
William McKee wrote:
On Thu, Jan 15, 2004 at 05:08:39PM -0800, Stas Bekman wrote:
strange, I saw it once and could never reproduce it again. What is the
sequence of commands when you get it?
t/TEST -start
t/TEST -run-tests t/03_hostport.t
can't work alone, you need to tell the httpd or apxs locat
William McKee wrote:
On Thu, Jan 15, 2004 at 09:03:54PM -0800, Stas Bekman wrote:
I didn't commit this part. I'm not sure we want to duplicate the porting
guide in this document. Instead of duplicating things, I've added a section
telling that this document uses mp2 in examples and gave a pointer
William McKee wrote:
On Fri, Jan 16, 2004 at 01:03:00PM -0500, William McKee wrote:
On Thu, Jan 15, 2004 at 04:24:41PM -0800, Stas Bekman wrote:
I don't have apache 1.3 with ssl so I can't test it. And it doesn't quite
work with apache/mp 2.0 because you have hardcoded mp1 API. Please see the
por
William McKee wrote:
Also you may want to adopt the convention we use for other test suites,
where the response part of the test resides under t/response. So you
usually don't test the module as is, but you create a response handler that
tests it. But it doesn't have to be that way of course.
O
William McKee wrote:
On Thu, Jan 15, 2004 at 05:08:39PM -0800, Stas Bekman wrote:
strange, I saw it once and could never reproduce it again. What is the
sequence of commands when you get it?
That is interesting. Right now, I'm playing with Geoff's
bug-reporting-skeleton-mp1 running my my Apache 1
I've reproduced the problem:
setenv APACHE /home/stas/httpd/1.3-dynamic/bin/httpd
t/TEST -v -trace=debug -port select
t/TEST -v -trace=debug
one the first run, extra.conf.in is parsed:
Including /tmp/bug-reporting-skeleton-mp1/t/conf/extra.conf config file
generating conf/extra.conf from
/tmp/bug-
Stas Bekman wrote:
I've reproduced the problem:
setenv APACHE /home/stas/httpd/1.3-dynamic/bin/httpd
t/TEST -v -trace=debug -port select
t/TEST -v -trace=debug
one the first run, extra.conf.in is parsed:
Including /tmp/bug-reporting-skeleton-mp1/t/conf/extra.conf config file
generating conf/extra.c
On Fri, Jan 16, 2004 at 02:30:45PM -0500, Geoffrey Young wrote:
> basically, there are two ways to approach Apache-Test: do it all yourself or
> let Apache-Test add some highly magical stuff. the article I wrote takes
> the first route - it assumes that you already know how to edit an httpd.conf
>
On Fri, Jan 16, 2004 at 07:23:11PM -0800, Stas Bekman wrote:
> Yes, just like the document explains. Have you read further down? It goes:
Sorry, I guess I missed that part. It's a big page.
> And then 4 hours later you posted another email with a list of
> problems/questions. So is that the fin
> I like that idea very much. Take the running/working simple test suite
> and start adding your things on top and not the other way around. Geoff,
> do you feel like adding this idea somewhere in the top of the
> testing.pod doc?
sure. I'll come up with another skeleton instead, though - as wil
>
> There's one last piece that I'm still unclear on which your article did
> not mention--reponse handlers. Is this where the two paths diverge? I'm
> not sure that I see much difference between the way you do it and the
> highly magical stuff.
well, that's the next step. instead of calling pl
On Sat, Jan 17, 2004 at 09:59:03AM -0500, Geoffrey Young wrote:
> > There's one last piece that I'm still unclear on which your article did
> > not mention--reponse handlers. Is this where the two paths diverge? I'm
> > not sure that I see much difference between the way you do it and the
> > highl
> I see why you call this code magical. It's definitely a step beyond my
> understanding and probably beyond my needs for now.
:)
> OK, I'm beginning to see now. I was able to take my revised skeleton and
> replace Apache::Test with Test::More. I had to modify the plan line to
> remove the have
14 matches
Mail list logo
