Re: Testing mod_perl

If I may ask a potentially stupid question, what are you attempting to do which necessitates the use of Apache2::Directive? On Wed, May 14, 2014 at 5:01 PM, Worik Stanton wrote: > On another matter... > > On 15/05/14 05:16, Perrin Harkins wrote: > > simpler things like PerlSetVar. There is an a

Re: Testing mod_perl

On 16/05/14 08:24, John Dunlap wrote: > If I may ask a potentially stupid question, what are you attempting to do > which necessitates the use of Apache2::Directive? I am randomly thrashing around trying to get started with the mod_perl API. More accurately I was. I have my bearings now and am m

Re: Testing mod_perl

> I looked up http://perl.apache.org/docs/general/testing/testing.html This is for testing applications written on top of mod_perl2. > Where is the > documentation that shows how to arrange the files and run these tests? In . Generate the test files as describe

Re: Testing for -D parameters.

On Tue, May 08, 2007 at 01:20:24PM +0200, Krist van Besien wrote: > Suppose I start my apache with an extra paramter, eg "-D FOO". Is > there a way to test for the presences of this parameter from within > mod perl sections? TFM would have told you, but you can use Apache->define("FOO"). /joel

Re: Testing a Handler

I got it, It was just a package naming issue. Sorry for the inconvenience, (it was late, I was tired...) Josh On 9/10/06, Jay Scherrer <[EMAIL PROTECTED]> wrote: Joshua Shapiro wrote: > Hello, > > I have inherited an application that makes use of mod_perl. I have > never used it before and

Re: Testing a Handler

Joshua Shapiro wrote: Hello, I have inherited an application that makes use of mod_perl. I have never used it before and am currently trying to understand it. I am trying to setup a simple CLI utility that will allow me to test the functionality of the website offline and eventually set up uni

Re: Testing a Handler

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, Sep 09, 2006 at 10:55:57PM -0600, Joshua Shapiro wrote: > Hello, > > I have inherited an application that makes use of mod_perl. I have > never used it before and am currently trying to understand it. I am > trying to setup a simple CLI util

Re: testing Apache/2.2 on Win32

We recently removed cli-[dev/[EMAIL PROTECTED] and moved that traffic straight to the general [EMAIL PROTECTED]/[EMAIL PROTECTED] lists. I mention it because announcements like this could be very useful to [EMAIL PROTECTED] folks. Bill Randy Kobes wrote: For those Win32 users using ActivePerl

Re: testing frameworks

On Mon, 2006-01-30 at 16:45 +, Carl Johnstone wrote: > By the way, anybody got any other suggestions? HTTP::Recorder? - Perrin

Re: Testing problem

Brenda Washington wrote: I'm getting this error message when I run a t/TEST. Does anyone know why I'm getting this error? Starting program: /usr/local/apache2/bin/httpd -D ONE_PROCESS -d /opt/apache/mod_perl-2.0.1/t -f /opt/apache/mod_perl-2.0.1/t/conf/httpd.conf -D APACHE2 [Thu Nov 10 14:

Re: testing against both apache 1.x and 2.x

Dorian Taylor wrote: so i'm working on one of my modules that works in both mod_perl 1 and 2, (custom config directives, conditional makefile processing, the whole nine) and i realized i have to test against both apache 1 and 2, preferably in one sequence. now, there's APACHE_TEST_APXS, APACHE_TE

Re: Testing failures not necessarily actual failures for a given installation

Kinyon, Rob wrote: It's been indicated to me that many of the tests which may or may not fail may not indicate that MP is unusable for a given installation. Are there any docs to explain what feature a given test tests? Or, is there a way of indicating to "make test" which features you actually car

RE: Testing issues w/ mod_perl 1.99_13

ib/perl5/site_perl . *** Packages of interest status: Apache::Request: - CGI: 3.03 LWP: 5.76 mod_perl : 1.9912 3. This is the core dump trace: (if you get a core dump): None. This report was generated by t/REPORT on Mon Mar 29 19:09:28 2004 GMT. -

Re: Testing issues w/ mod_perl 1.99_13

Obitz, Toby wrote: > Stas, > > You had asked me to reply to the list with an answer to your question: > > "BTW, can you please try 1.99_12. Do you have the same failures? Please > reply to that thread on the modperl list. And let's continue that > discussion over there." > > I have tried the follow

Re: Testing issues w/ mod_perl 1.99_13

[cc'ing Toby who is in the same boat] Kinyon, Rob wrote: t/filter/both_str_con_add.t43 75.00% 2-4 t/protocol/echo.t 22 5632 32 66.67% 2-3 t/protocol/echo_filter.t 22 5632 32 66.67% 2-3 Interesting, all 3 test have one thing in common -

Re: Testing issues w/ mod_perl 1.99_13

Stas Bekman wrote: Kinyon, Rob wrote: Rob, please submit a properl bug report: http://perl.apache.org/bugs/ You can't be bothered to help us resolve your problems? :( __ Stas BekmanJAm_pH --> Just Another mod_perl Hac

RE: Testing issues w/ mod_perl 1.99_13

> t/filter/both_str_con_add.t43 75.00% 2-4 > t/protocol/echo.t 22 5632 32 66.67% 2-3 > t/protocol/echo_filter.t 22 5632 32 66.67% 2-3 Interesting, all 3 test have one thing in common - they use a raw socket to communicate with the clien

Re: Testing issues w/ mod_perl 1.99_13

Kinyon, Rob wrote: Rob, please submit a properl bug report: http://perl.apache.org/bugs/ 2) _13 compiled fine using 2.0.49. However, it will not pass the tests. I removed all mention of RewriteEngine, but still ran into problems. The error log has no errors in it. The only item is that it seems t

Re: Testing issues w/ mod_perl 1.99_13

Geoffrey Young wrote: + +RewriteEngine On actually, rewrite seems to be a leftover, maybe from when the test was being originally written - I can't see the need for rewrite at all and removing the RewriteEngine directive still allows the tests to pass (as you mentioned). bu

Re: Testing issues w/ mod_perl 1.99_13

> + > +RewriteEngine On actually, rewrite seems to be a leftover, maybe from when the test was being originally written - I can't see the need for rewrite at all and removing the RewriteEngine directive still allows the tests to pass (as you mentioned). but let's let stas l

Re: Testing issues w/ mod_perl 1.99_13

Geoffrey Young wrote: >>I'm having problems in that some of the tests in _12 and _13 use >>RewriteEngine, which I have disabled. To get _12 to pass, I had to >>delete all mention of "RewriteEngine". > > > please try the attached patch. oops, sorry - I forgot to change one thing. please discar

Re: Testing issues w/ mod_perl 1.99_13

> I'm having problems in that some of the tests in _12 and _13 use > RewriteEngine, which I have disabled. To get _12 to pass, I had to > delete all mention of "RewriteEngine". please try the attached patch. --Geoff Index: t/filter/both_str_req_proxy.t ===

Re: Testing mod_perl

Ged Haywood wrote: Hi there, On Tue, 3 Feb 2004, Hemond, Steve wrote: I just installed Apache2/mod_perl2 and wants to test it. ... [Tue Feb 03 11:23:46 2004] [error] failed to resolve handler `Apache::Registry' ... What's wrong? http://perl.apache.org/docs/2.0/user/intro/start_fast.html#Regist

Re: Testing mod_perl

Hi there, On Tue, 3 Feb 2004, Hemond, Steve wrote: > I just installed Apache2/mod_perl2 and wants to test it. > ... > [Tue Feb 03 11:23:46 2004] [error] failed to resolve handler `Apache::Registry' > ... > What's wrong? http://perl.apache.org/docs/2.0/user/intro/start_fast.html#Registry_Scripts

Re: Testing custom configuration directives

Tank you very much, Geoff! Now the things comes to play right...! Merry Christmas!! -- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html

Re: Testing custom configuration directives

> I still having problem with this extra.last.conf.in. > Please, if you want and have time, take a look to included TGZ stub package > (I included in cause is small and, maybe, make clear my problem). > TIA > > YEAH finally, a user that submits a nice sample tarball for me to just run!!!

Re: Testing custom configuration directives

> moving back on-list so everyone can benefit :) Yes, sorry. > oh, I think I see what you mean. use t/conf/extra.last.conf.in instead of > extra.conf.in - it will make sure your modules are loaded before the config > is parsed. I still having problem with this extra.last.conf.in. Please, if you

Re: Testing custom configuration directives

moving back on-list so everyone can benefit :) Carletto wrote: >>I was assuming from the above that he already had Apache-Test working. >> >>--Geoff > > > Yes, that is. > The problem is: the configuration directives (expressed in Foo/Bar.pm as > explained in Chap.6 of > "User's guide" mod_perl 2

Re: Testing custom configuration directives

>>> # file t/conf/extra.conf.in > Carletto is talking about the live testing of a module that won't work > without running mod_perl and he is not aware of Apache-Test, required > for this kind of tests. I was assuming from the above that he already had Apache-Test working. --Geoff -- Reporti

Re: Testing custom configuration directives

Geoffrey Young wrote: Carletto wrote: Hi! Anyone has experience in testing an Apache module (mod_perl 2.0, of course) with custom configuration directives ? I'm talking about a module "packaged" (h2xs -AX -n Foo::Bar) and then tested (perl Makefile.PL; make; make test), when as custom configuratio

Re: Testing custom configuration directives

Carletto wrote: > Hi! > Anyone has experience in testing an Apache module (mod_perl 2.0, of course) > with > custom configuration directives ? > I'm talking about a module "packaged" (h2xs -AX -n Foo::Bar) and then tested > (perl Makefile.PL; make; make test), when as custom configuration is like

Re: Testing

Nick Phillips wrote: On 12/12/2003, at 8:34 AM, Garrett Goebel wrote: Nick Phillips wrote: > > Just wondering whether anyone here has any cunning ways of > unit testing code that uses the various Apache:: modules; > the only vaguely useful thing I've managed to find so far > is Apache::FakeRequest

Re: Testing

On Fri, 12 Dec 2003 08:55:43 +1300 Nick Phillips <[EMAIL PROTECTED]> wrote: > So far as I can see, that is all directed at testing by sending a > request > to a server and checking what comes back; that's really not useful for > testing components of code individually, which is the point. I don't

RE: Testing

Title: RE: Testing Nick Phillips wrote: > Garrett Goebel wrote: > > Nick Phillips wrote: > > > > > > Just wondering whether anyone here has any cunning ways of > > > unit testing code that uses the various Apache:: modules; > > > the only vag

Re: Testing

> > So far as I can see, that is all directed at testing by sending a request > to a server and checking what comes back; that's really not useful for > testing components of code individually, which is the point. I don't > want to test the server, I want to individually test each chunk of my cod

Re: Testing

> Effectively testing web apps without messing around with parsing HTML > is something I've been wondering about for a while. Anyone solve > this problem well? Not sure if this falls into your parsing HTML category or not but I've found it to be quite comprehensive when it comes to testing web

Re: Testing

On 12/12/2003, at 8:34 AM, Garrett Goebel wrote: Nick Phillips wrote: > > Just wondering whether anyone here has any cunning ways of > unit testing code that uses the various Apache:: modules; > the only vaguely useful thing I've managed to find so far > is Apache::FakeRequest, but that still leav

Re: Testing

> http://search.cpan.org/search?query=Apache+testing&mode=all > > http://search.cpan.org/~geoff/Apache-Test-1.06/ > > http://perl.apache.org/docs/general/testing/testing.html > there's also http://www.perl.com/pub/a/2003/05/22/testing.html which might help as well. and while it's not nearly

Re: Testing

At 8:30 AM +1300 12/12/03, Nick Phillips wrote: Just wondering whether anyone here has any cunning ways of unit testing code that uses the various Apache:: modules; the only vaguely useful thing I've managed to find so far is Apache::FakeRequest, but that still leaves problems with code that uses A

Re: Testing

On Fri, 12 Dec 2003, Nick Phillips wrote: > Just wondering whether anyone here has any cunning ways of unit testing > code > that uses the various Apache:: modules; the only vaguely useful thing > I've > managed to find so far is Apache::FakeRequest, but that still leaves > problems > with code

RE: Testing

Title: RE: Testing Nick Phillips wrote: > > Just wondering whether anyone here has any cunning ways of > unit testing code that uses the various Apache:: modules; > the only vaguely useful thing I've managed to find so far > is Apache::FakeRequest, but that still le