Re: setting up testing
On Thu, Mar 1, 2012 at 2:50 PM, Michael Felt wrote: > Want to get started on this. I read the links from > http://httpd.apache.org/test/ and think I understand the flood subproject. > From reading the forums here recently I get the impression that more than > flood is being used, or even something other than flood. > > Looking for assistance and suggestions. perl framework... get svn on your AIX box if you don't have it already check out /httpd/test/framework/trunk/ perl Makefile.PL -apxs /path/to/apxs t/TEST t/TEST -clean No it won't be fun because things will fail and there will be many different reasons, few if any obvious ones :) You will likely need to install more Perl modules... Some old instructions of mine: perl -MCPAN -e 'shell' cpan>install Test::Harness cpan>install URI cpan>install LWP::Protocol::https cpan>install HTTP::DAV cpan>install Bundle::ApacheTest cpan>install LWP::Simple (dunno if this is current or everything you need on your level of AIX; this was for OpenSolaris a couple of years ago)
Re: setting up testing
perl with -MCPAN I used to use a lot, getting svn - personal build via a personal build is a different story. Guess I'll have to hunt down a package of RPM's for now and solve the core dump problem (in sqlite3 I have found at least). Macros are nice for coding, but less nice when working through dbx (although I used to be an expert with both adb and debug.com) Sigh... Thanks Jeff! On Thu, Mar 1, 2012 at 9:01 PM, Jeff Trawick wrote: > On Thu, Mar 1, 2012 at 2:50 PM, Michael Felt wrote: > > Want to get started on this. I read the links from > > http://httpd.apache.org/test/ and think I understand the flood > subproject. > > From reading the forums here recently I get the impression that more than > > flood is being used, or even something other than flood. > > > > Looking for assistance and suggestions. > > perl framework... > > get svn on your AIX box if you don't have it already > > check out /httpd/test/framework/trunk/ > > perl Makefile.PL -apxs /path/to/apxs > t/TEST > t/TEST -clean > > No it won't be fun because things will fail and there will be many > different reasons, few if any obvious ones :) > > You will likely need to install more Perl modules... Some old > instructions of mine: > >perl -MCPAN -e 'shell' >cpan>install Test::Harness >cpan>install URI >cpan>install LWP::Protocol::https >cpan>install HTTP::DAV >cpan>install Bundle::ApacheTest >cpan>install LWP::Simple > > (dunno if this is current or everything you need on your level of AIX; > this was for OpenSolaris a couple of years ago) >
Re: setting up testing
One quick question: can I assume that the test is ideally in a different machine than the httpd system being tested, or do the tests assume localhost? On Thu, Mar 1, 2012 at 8:50 PM, Michael Felt wrote: > Want to get started on this. I read the links from > http://httpd.apache.org/test/ and think I understand the flood > subproject. From reading the forums here recently I get the impression that > more than flood is being used, or even something other than flood. > > Looking for assistance and suggestions. > > Michael >
Re: setting up testing
On Thu, Mar 1, 2012 at 3:17 PM, Michael Felt wrote: > One quick question: can I assume that the test is ideally in a different > machine than the httpd system being tested, or do the tests assume > localhost? To be honest I haven't looked, but I suspect it is local host only... Once you have the test suite installed somewhere, try t/TEST -help and you'll see a multitude of options, some of which are for controlling the test environment more closely than with the very basic instructions I gave. Come to think of it, try it first on Linux and get it running cleanly there with help of dev@ as necessary, then when on AIX and possibly stumbling through issues getting the right CPAN packages installed you'll already know what it is supposed to look like. And of course you can play with the available test variations. > > On Thu, Mar 1, 2012 at 8:50 PM, Michael Felt wrote: >> >> Want to get started on this. I read the links from >> http://httpd.apache.org/test/ and think I understand the flood subproject. >> From reading the forums here recently I get the impression that more than >> flood is being used, or even something other than flood. >> >> Looking for assistance and suggestions. >> >> Michael > > -- Born in Roswell... married an alien...
Re: setting up testing
On 3/1/2012 2:17 PM, Michael Felt wrote: > One quick question: can I assume that the test is ideally in a different > machine than the > httpd system being tested, or do the tests assume localhost? You can do either, see t/TEST --help
Re: setting up testing
On Thu, Mar 1, 2012 at 3:14 PM, Michael Felt wrote: > perl with -MCPAN I used to use a lot, getting svn - personal build via a > personal build is a different story. Guess I'll have to hunt down a package > of RPM's for now and solve the core dump problem (in sqlite3 I have found at > least). Macros are nice for coding, but less nice when working through dbx > (although I used to be an expert with both adb and debug.com) I think I've suggested this before, but the path of least resistance on AIX is the java-based svnkit for svn.
Re: setting up testing
yes you have, and I lost the info ... will start the search now... first on linux: assumes you have a linux box ready and waiting, which i dont. However, in 20 minutes I can have a new clean AIX sandbox - so I'll suffer through a bit. CPAN works very well is my memory of it. On Thu, Mar 1, 2012 at 9:45 PM, Eric Covener wrote: > On Thu, Mar 1, 2012 at 3:14 PM, Michael Felt wrote: > > perl with -MCPAN I used to use a lot, getting svn - personal build via a > > personal build is a different story. Guess I'll have to hunt down a > package > > of RPM's for now and solve the core dump problem (in sqlite3 I have > found at > > least). Macros are nice for coding, but less nice when working through > dbx > > (although I used to be an expert with both adb and debug.com) > > I think I've suggested this before, but the path of least resistance > on AIX is the java-based svnkit for svn. >
Re: setting up testing
trying: # svnkit-1.3.7/bin/jsvn checkout http://svn.apache.org/viewvc/httpd/test/framework/trunk test get: svn: Repository moved permanently to '/viewvc/httpd/test/framework/trunk'; please relocate svn: OPTIONS request failed on '/viewvc/httpd/test/framework/trunk' Explanation please. On Thu, Mar 1, 2012 at 9:01 PM, Jeff Trawick wrote: > On Thu, Mar 1, 2012 at 2:50 PM, Michael Felt wrote: > > Want to get started on this. I read the links from > > http://httpd.apache.org/test/ and think I understand the flood > subproject. > > From reading the forums here recently I get the impression that more than > > flood is being used, or even something other than flood. > > > > Looking for assistance and suggestions. > > perl framework... > > get svn on your AIX box if you don't have it already > > check out /httpd/test/framework/trunk/ > > perl Makefile.PL -apxs /path/to/apxs > t/TEST > t/TEST -clean > > No it won't be fun because things will fail and there will be many > different reasons, few if any obvious ones :) > > You will likely need to install more Perl modules... Some old > instructions of mine: > >perl -MCPAN -e 'shell' >cpan>install Test::Harness >cpan>install URI >cpan>install LWP::Protocol::https >cpan>install HTTP::DAV >cpan>install Bundle::ApacheTest >cpan>install LWP::Simple > > (dunno if this is current or everything you need on your level of AIX; > this was for OpenSolaris a couple of years ago) >
Re: setting up testing
On Thu, Mar 1, 2012 at 8:09 PM, Michael Felt wrote: > trying: > # svnkit-1.3.7/bin/jsvn checkout > http://svn.apache.org/viewvc/httpd/test/framework/trunk test > > get: > svn: Repository moved permanently to '/viewvc/httpd/test/framework/trunk'; > please relocate > svn: OPTIONS request failed on '/viewvc/httpd/test/framework/trunk' > > Explanation please. viewvc is a CGI script, not part of the svn path This page here has an example of checking out something under the httpd project: http://httpd.apache.org/dev/devnotes.html > > On Thu, Mar 1, 2012 at 9:01 PM, Jeff Trawick wrote: >> >> On Thu, Mar 1, 2012 at 2:50 PM, Michael Felt wrote: >> > Want to get started on this. I read the links from >> > http://httpd.apache.org/test/ and think I understand the flood >> > subproject. >> > From reading the forums here recently I get the impression that more >> > than >> > flood is being used, or even something other than flood. >> > >> > Looking for assistance and suggestions. >> >> perl framework... >> >> get svn on your AIX box if you don't have it already >> >> check out /httpd/test/framework/trunk/ >> >> perl Makefile.PL -apxs /path/to/apxs >> t/TEST >> t/TEST -clean >> >> No it won't be fun because things will fail and there will be many >> different reasons, few if any obvious ones :) >> >> You will likely need to install more Perl modules... Some old >> instructions of mine: >> >> perl -MCPAN -e 'shell' >> cpan>install Test::Harness >> cpan>install URI >> cpan>install LWP::Protocol::https >> cpan>install HTTP::DAV >> cpan>install Bundle::ApacheTest >> cpan>install LWP::Simple >> >> (dunno if this is current or everything you need on your level of AIX; >> this was for OpenSolaris a couple of years ago) > > -- Born in Roswell... married an alien...
Re: setting up testing
In other words, I needed to look lower at: so I should be using: "svn checkout" https://svn.apache.org/repos/asf/perl/Apache-Test/trunk Apache-Test Thanks On Fri, Mar 2, 2012 at 2:29 AM, Jeff Trawick wrote: > On Thu, Mar 1, 2012 at 8:09 PM, Michael Felt wrote: > > trying: > > # svnkit-1.3.7/bin/jsvn checkout > > http://svn.apache.org/viewvc/httpd/test/framework/trunk test > > > > get: > > svn: Repository moved permanently to > '/viewvc/httpd/test/framework/trunk'; > > please relocate > > svn: OPTIONS request failed on '/viewvc/httpd/test/framework/trunk' > > > > Explanation please. > > viewvc is a CGI script, not part of the svn path > > This page here has an example of checking out something under the httpd > project: > > http://httpd.apache.org/dev/devnotes.html > > > > > On Thu, Mar 1, 2012 at 9:01 PM, Jeff Trawick wrote: > >> > >> On Thu, Mar 1, 2012 at 2:50 PM, Michael Felt wrote: > >> > Want to get started on this. I read the links from > >> > http://httpd.apache.org/test/ and think I understand the flood > >> > subproject. > >> > From reading the forums here recently I get the impression that more > >> > than > >> > flood is being used, or even something other than flood. > >> > > >> > Looking for assistance and suggestions. > >> > >> perl framework... > >> > >> get svn on your AIX box if you don't have it already > >> > >> check out /httpd/test/framework/trunk/ > >> > >> perl Makefile.PL -apxs /path/to/apxs > >> t/TEST > >> t/TEST -clean > >> > >> No it won't be fun because things will fail and there will be many > >> different reasons, few if any obvious ones :) > >> > >> You will likely need to install more Perl modules... Some old > >> instructions of mine: > >> > >>perl -MCPAN -e 'shell' > >>cpan>install Test::Harness > >>cpan>install URI > >>cpan>install LWP::Protocol::https > >>cpan>install HTTP::DAV > >>cpan>install Bundle::ApacheTest > >>cpan>install LWP::Simple > >> > >> (dunno if this is current or everything you need on your level of AIX; > >> this was for OpenSolaris a couple of years ago) > > > > > > > > -- > Born in Roswell... married an alien... >
Re: setting up testing
Seems to have worked, and only a minor error/warning (I hope) - twice... Manifying blib/man3/Apache::TestHandler.3 lib/Apache/TestHandler.pm:106: Unknown command paragraph "=encoding utf8" So, I expect I'll still have to load more stuff from CPAN, once I find the start button... On Fri, Mar 2, 2012 at 8:34 AM, Michael Felt wrote: > In other words, I needed to look lower at: > > so I should be using: "svn checkout" > https://svn.apache.org/repos/asf/perl/Apache-Test/trunk Apache-Test > > Thanks > > > On Fri, Mar 2, 2012 at 2:29 AM, Jeff Trawick wrote: > >> On Thu, Mar 1, 2012 at 8:09 PM, Michael Felt wrote: >> > trying: >> > # svnkit-1.3.7/bin/jsvn checkout >> > http://svn.apache.org/viewvc/httpd/test/framework/trunk test >> > >> > get: >> > svn: Repository moved permanently to >> '/viewvc/httpd/test/framework/trunk'; >> > please relocate >> > svn: OPTIONS request failed on '/viewvc/httpd/test/framework/trunk' >> > >> > Explanation please. >> >> viewvc is a CGI script, not part of the svn path >> >> This page here has an example of checking out something under the httpd >> project: >> >> http://httpd.apache.org/dev/devnotes.html >> >> > >> > On Thu, Mar 1, 2012 at 9:01 PM, Jeff Trawick wrote: >> >> >> >> On Thu, Mar 1, 2012 at 2:50 PM, Michael Felt >> wrote: >> >> > Want to get started on this. I read the links from >> >> > http://httpd.apache.org/test/ and think I understand the flood >> >> > subproject. >> >> > From reading the forums here recently I get the impression that more >> >> > than >> >> > flood is being used, or even something other than flood. >> >> > >> >> > Looking for assistance and suggestions. >> >> >> >> perl framework... >> >> >> >> get svn on your AIX box if you don't have it already >> >> >> >> check out /httpd/test/framework/trunk/ >> >> >> >> perl Makefile.PL -apxs /path/to/apxs >> >> t/TEST >> >> t/TEST -clean >> >> >> >> No it won't be fun because things will fail and there will be many >> >> different reasons, few if any obvious ones :) >> >> >> >> You will likely need to install more Perl modules... Some old >> >> instructions of mine: >> >> >> >>perl -MCPAN -e 'shell' >> >>cpan>install Test::Harness >> >>cpan>install URI >> >>cpan>install LWP::Protocol::https >> >>cpan>install HTTP::DAV >> >>cpan>install Bundle::ApacheTest >> >>cpan>install LWP::Simple >> >> >> >> (dunno if this is current or everything you need on your level of AIX; >> >> this was for OpenSolaris a couple of years ago) >> > >> > >> >> >> >> -- >> Born in Roswell... married an alien... >> > >
Re: setting up testing
I have seen the name apxs many times in the past, t/TEST -help names an -apxs location of apxs (default is from Apache2::BuildConfig) Currently I have a partition (actually a WPAR) that only has perl updated via cpan and Apache-Test loaded. Since I wont be starting the httpd locally, do I still need apxs? It looks like it is used for start/stop/reconfig? Off to work, thanks again for the help! On Fri, Mar 2, 2012 at 8:42 AM, Michael Felt wrote: > Seems to have worked, and only a minor error/warning (I hope) - twice... > > Manifying blib/man3/Apache::TestHandler.3 > lib/Apache/TestHandler.pm:106: Unknown command paragraph "=encoding utf8" > > So, I expect I'll still have to load more stuff from CPAN, once I find the > start button... > > On Fri, Mar 2, 2012 at 8:34 AM, Michael Felt wrote: > >> In other words, I needed to look lower at: >> >> so I should be using: "svn checkout" >> https://svn.apache.org/repos/asf/perl/Apache-Test/trunk Apache-Test >> >> Thanks >> >> >> On Fri, Mar 2, 2012 at 2:29 AM, Jeff Trawick wrote: >> >>> On Thu, Mar 1, 2012 at 8:09 PM, Michael Felt wrote: >>> > trying: >>> > # svnkit-1.3.7/bin/jsvn checkout >>> > http://svn.apache.org/viewvc/httpd/test/framework/trunk test >>> > >>> > get: >>> > svn: Repository moved permanently to >>> '/viewvc/httpd/test/framework/trunk'; >>> > please relocate >>> > svn: OPTIONS request failed on '/viewvc/httpd/test/framework/trunk' >>> > >>> > Explanation please. >>> >>> viewvc is a CGI script, not part of the svn path >>> >>> This page here has an example of checking out something under the httpd >>> project: >>> >>> http://httpd.apache.org/dev/devnotes.html >>> >>> > >>> > On Thu, Mar 1, 2012 at 9:01 PM, Jeff Trawick >>> wrote: >>> >> >>> >> On Thu, Mar 1, 2012 at 2:50 PM, Michael Felt >>> wrote: >>> >> > Want to get started on this. I read the links from >>> >> > http://httpd.apache.org/test/ and think I understand the flood >>> >> > subproject. >>> >> > From reading the forums here recently I get the impression that more >>> >> > than >>> >> > flood is being used, or even something other than flood. >>> >> > >>> >> > Looking for assistance and suggestions. >>> >> >>> >> perl framework... >>> >> >>> >> get svn on your AIX box if you don't have it already >>> >> >>> >> check out /httpd/test/framework/trunk/ >>> >> >>> >> perl Makefile.PL -apxs /path/to/apxs >>> >> t/TEST >>> >> t/TEST -clean >>> >> >>> >> No it won't be fun because things will fail and there will be many >>> >> different reasons, few if any obvious ones :) >>> >> >>> >> You will likely need to install more Perl modules... Some old >>> >> instructions of mine: >>> >> >>> >>perl -MCPAN -e 'shell' >>> >>cpan>install Test::Harness >>> >>cpan>install URI >>> >>cpan>install LWP::Protocol::https >>> >>cpan>install HTTP::DAV >>> >>cpan>install Bundle::ApacheTest >>> >>cpan>install LWP::Simple >>> >> >>> >> (dunno if this is current or everything you need on your level of AIX; >>> >> this was for OpenSolaris a couple of years ago) >>> > >>> > >>> >>> >>> >>> -- >>> Born in Roswell... married an alien... >>> >> >> >
Re: setting up testing
Very definitely localhost. The test suite will automatically configure and launch variously configured httpd instances for testing itself. On 01/03/2012 22:22, Jeff Trawick wrote: > On Thu, Mar 1, 2012 at 3:17 PM, Michael Felt wrote: >> One quick question: can I assume that the test is ideally in a different >> machine than the httpd system being tested, or do the tests assume >> localhost? > To be honest I haven't looked, but I suspect it is local host only... > Once you have the test suite installed somewhere, try t/TEST -help > and you'll see a multitude of options, some of which are for > controlling the test environment more closely than with the very basic > instructions I gave. > > Come to think of it, try it first on Linux and get it running cleanly > there with help of dev@ as necessary, then when on AIX and possibly > stumbling through issues getting the right CPAN packages installed > you'll already know what it is supposed to look like. And of course > you can play with the available test variations. > >> On Thu, Mar 1, 2012 at 8:50 PM, Michael Felt wrote: >>> Want to get started on this. I read the links from >>> http://httpd.apache.org/test/ and think I understand the flood subproject. >>> From reading the forums here recently I get the impression that more than >>> flood is being used, or even something other than flood. >>> >>> Looking for assistance and suggestions. >>> >>> Michael >> > >
Re: setting up testing
Well, as long as I dont need a compiler (as I dont have one installed here, dont want test to be dependent on compiler, or dev related files not normally found on production system) this wont be a problem - I will just install the packages and then execute the tests. However, as noted for the performance benchmark between ngix (or something like that) and httpd-2.4.1 - testing over network interfaces, rather than on local host is also needed (if not preferred). On Fri, Mar 2, 2012 at 10:13 AM, Issac Goldstand wrote: > Very definitely localhost. The test suite will automatically configure > and launch variously configured httpd instances for testing itself. > > On 01/03/2012 22:22, Jeff Trawick wrote: > > On Thu, Mar 1, 2012 at 3:17 PM, Michael Felt wrote: > >> One quick question: can I assume that the test is ideally in a different > >> machine than the httpd system being tested, or do the tests assume > >> localhost? > > To be honest I haven't looked, but I suspect it is local host only... > > Once you have the test suite installed somewhere, try t/TEST -help > > and you'll see a multitude of options, some of which are for > > controlling the test environment more closely than with the very basic > > instructions I gave. > > > > Come to think of it, try it first on Linux and get it running cleanly > > there with help of dev@ as necessary, then when on AIX and possibly > > stumbling through issues getting the right CPAN packages installed > > you'll already know what it is supposed to look like. And of course > > you can play with the available test variations. > > > >> On Thu, Mar 1, 2012 at 8:50 PM, Michael Felt wrote: > >>> Want to get started on this. I read the links from > >>> http://httpd.apache.org/test/ and think I understand the flood > subproject. > >>> From reading the forums here recently I get the impression that more > than > >>> flood is being used, or even something other than flood. > >>> > >>> Looking for assistance and suggestions. > >>> > >>> Michael > >> > > > > > >
Re: setting up testing
On Fri, Mar 2, 2012 at 2:50 AM, Michael Felt wrote: > I have seen the name apxs many times in the past, t/TEST -help names an > -apxs location of apxs (default is from > Apache2::BuildConfig) apxs is for building plugin modules (via a compiler that must be installed) testing relies on special plugin modules (mod_XXX, mod_YYY, etc.) that are part of the test suite to be built and installed into the httpd under test > > Currently I have a partition (actually a WPAR) that only has perl updated > via cpan and Apache-Test loaded. > > Since I wont be starting the httpd locally, do I still need apxs? It looks > like it is used for start/stop/reconfig? > > Off to work, thanks again for the help! > > > On Fri, Mar 2, 2012 at 8:42 AM, Michael Felt wrote: >> >> Seems to have worked, and only a minor error/warning (I hope) - twice... >> >> Manifying blib/man3/Apache::TestHandler.3 >> lib/Apache/TestHandler.pm:106: Unknown command paragraph "=encoding utf8" >> >> So, I expect I'll still have to load more stuff from CPAN, once I find the >> start button... >> >> On Fri, Mar 2, 2012 at 8:34 AM, Michael Felt wrote: >>> >>> In other words, I needed to look lower at: >>> >>> so I should be using: "svn checkout" >>> https://svn.apache.org/repos/asf/perl/Apache-Test/trunk Apache-Test >>> >>> Thanks >>> >>> >>> On Fri, Mar 2, 2012 at 2:29 AM, Jeff Trawick wrote: On Thu, Mar 1, 2012 at 8:09 PM, Michael Felt wrote: > trying: > # svnkit-1.3.7/bin/jsvn checkout > http://svn.apache.org/viewvc/httpd/test/framework/trunk test > > get: > svn: Repository moved permanently to > '/viewvc/httpd/test/framework/trunk'; > please relocate > svn: OPTIONS request failed on '/viewvc/httpd/test/framework/trunk' > > Explanation please. viewvc is a CGI script, not part of the svn path This page here has an example of checking out something under the httpd project: http://httpd.apache.org/dev/devnotes.html > > On Thu, Mar 1, 2012 at 9:01 PM, Jeff Trawick > wrote: >> >> On Thu, Mar 1, 2012 at 2:50 PM, Michael Felt >> wrote: >> > Want to get started on this. I read the links from >> > http://httpd.apache.org/test/ and think I understand the flood >> > subproject. >> > From reading the forums here recently I get the impression that >> > more >> > than >> > flood is being used, or even something other than flood. >> > >> > Looking for assistance and suggestions. >> >> perl framework... >> >> get svn on your AIX box if you don't have it already >> >> check out /httpd/test/framework/trunk/ >> >> perl Makefile.PL -apxs /path/to/apxs >> t/TEST >> t/TEST -clean >> >> No it won't be fun because things will fail and there will be many >> different reasons, few if any obvious ones :) >> >> You will likely need to install more Perl modules... Some old >> instructions of mine: >> >> perl -MCPAN -e 'shell' >> cpan>install Test::Harness >> cpan>install URI >> cpan>install LWP::Protocol::https >> cpan>install HTTP::DAV >> cpan>install Bundle::ApacheTest >> cpan>install LWP::Simple >> >> (dunno if this is current or everything you need on your level of >> AIX; >> this was for OpenSolaris a couple of years ago) > > -- Born in Roswell... married an alien... >>> >>> >> > -- Born in Roswell... married an alien...
Re: setting up testing
On 02.03.2012 11:44, Michael Felt wrote: Well, as long as I dont need a compiler (as I dont have one installed here, dont want test to be dependent on compiler, or dev related files not normally found on production system) this wont be a problem - I will just install the packages and then execute the tests. As Jeff wrote: the test suite needs a compiler, because it builds additional modules that come with the test suite first. You might be able to start tests and let the modules build and then later move everything to a non-dev box and rerun the tests there (which will not try to build those modules again). Never tried it, but you should at least move it to the same directory on the other box. However, as noted for the performance benchmark between ngix (or something like that) and httpd-2.4.1 - testing over network interfaces, rather than on local host is also needed (if not preferred). The test suite checks functionality and bug regressions. It doesn't test performance. For performance tests you will need specialized tools and the results will depend a lot on the type of environment used, the configuration and the use cases being simulated. Regards, Rainer
Re: setting up testing
thx On Sat, Mar 3, 2012 at 7:42 PM, Rainer Jung wrote: > On 02.03.2012 11:44, Michael Felt wrote: > >> Well, as long as I dont need a compiler (as I dont have one installed >> here, dont want test to be dependent on compiler, or dev related files >> not normally found on production system) this wont be a problem - I will >> just install the packages and then execute the tests. >> > > As Jeff wrote: the test suite needs a compiler, because it builds > additional modules that come with the test suite first. > > You might be able to start tests and let the modules build and then later > move everything to a non-dev box and rerun the tests there (which will not > try to build those modules again). Never tried it, but you should at least > move it to the same directory on the other box. > > > However, as noted for the performance benchmark between ngix (or >> something like that) and httpd-2.4.1 - testing over network interfaces, >> rather than on local host is also needed (if not preferred). >> > > The test suite checks functionality and bug regressions. It doesn't test > performance. For performance tests you will need specialized tools and the > results will depend a lot on the type of environment used, the > configuration and the use cases being simulated. > > Regards, > > Rainer >
Re: setting up testing
Bother: I did not need to install any extra modules - and this has taken forever, because I kept running into problems trying to install all the extra modules. However, "Is this all there is?", and why do I not have a mod_perl.c - is that a "tester/developer" only module, or just no longer in the "all" list? Would you consider this a PASS for the tests? Thx. root@x104:[/data/prj/SVN/Apache-Test]t/TEST [warning] setting ulimit to allow core files ulimit -c unlimited; /usr/opt/perl5/bin/perl /data/prj/SVN/Apache-Test/t/TEST /opt/httpd/sbin/httpd -d /data/prj/SVN/Apache-Test/t -f /data/prj/SVN/Apache-Test/t/conf/httpd.conf -D APACHE2 -D PERL_USEITHREADS using Apache/2.5.0-dev (worker MPM) waiting 60 seconds for server to start: ... waiting 60 seconds for server to start: ok (waited 2 secs) server loopback:8529 started [ info] adding source lib /data/prj/SVN/Apache-Test/../Apache-Test/lib to @INC t/alltest/all...skipped all skipped: testing all.t t/alltest2/all..skipped all skipped: testing more than one all.t t/bad_codingok t/cookies...ok t/importok t/log_watch.ok t/log_watch_for_broken_linesok t/more/all..skipped all skipped: cannot find module 'mod_perl.c' t/next_available_port...ok t/ping..ok t/redirect..ok t/request...ok t/sok...ok All tests successful, 3 tests skipped. Files=13, Tests=93, 24 wallclock secs ( 8.67 cusr + 6.69 csys = 15.36 CPU) [warning] server loopback:8529 shutdown [warning] port 8529 still in use... ..done On Thu, Mar 1, 2012 at 9:01 PM, Jeff Trawick wrote: > On Thu, Mar 1, 2012 at 2:50 PM, Michael Felt wrote: > > Want to get started on this. I read the links from > > http://httpd.apache.org/test/ and think I understand the flood > subproject. > > From reading the forums here recently I get the impression that more than > > flood is being used, or even something other than flood. > > > > Looking for assistance and suggestions. > > perl framework... > > get svn on your AIX box if you don't have it already > > check out /httpd/test/framework/trunk/ > > perl Makefile.PL -apxs /path/to/apxs > t/TEST > t/TEST -clean > > No it won't be fun because things will fail and there will be many > different reasons, few if any obvious ones :) > > You will likely need to install more Perl modules... Some old > instructions of mine: > >perl -MCPAN -e 'shell' >cpan>install Test::Harness >cpan>install URI >cpan>install LWP::Protocol::https >cpan>install HTTP::DAV >cpan>install Bundle::ApacheTest >cpan>install LWP::Simple > > (dunno if this is current or everything you need on your level of AIX; > this was for OpenSolaris a couple of years ago) >
Re: setting up testing
I found some info on a mod_perl, and have picked it up via svn - but am stuck - where does it expect to be? root@x104:[/data/prj/modperl]perl Makefile.PL MP_APXS=/opt/httpd/bin/apxs Reading Makefile.PL args from @ARGV MP_APXS = /opt/httpd/bin/apxs [ error] Can't find a sub-directory Apache-Test. Make sure that you are using a complete source distribution On Wed, Apr 4, 2012 at 10:13 PM, Michael Felt wrote: > Bother: I did not need to install any extra modules - and this has taken > forever, because I kept running into problems trying to install all the > extra modules. > > However, "Is this all there is?", and why do I not have a mod_perl.c - is > that a "tester/developer" only module, or just no longer in the "all" list? > > Would you consider this a PASS for the tests? > > Thx. > > root@x104:[/data/prj/SVN/Apache-Test]t/TEST > [warning] setting ulimit to allow core files > ulimit -c unlimited; /usr/opt/perl5/bin/perl > /data/prj/SVN/Apache-Test/t/TEST > /opt/httpd/sbin/httpd -d /data/prj/SVN/Apache-Test/t -f > /data/prj/SVN/Apache-Test/t/conf/httpd.conf -D APACHE2 -D PERL_USEITHREADS > using Apache/2.5.0-dev (worker MPM) > > waiting 60 seconds for server to start: ... > waiting 60 seconds for server to start: ok (waited 2 secs) > server loopback:8529 started > [ info] adding source lib /data/prj/SVN/Apache-Test/../Apache-Test/lib > to @INC > t/alltest/all...skipped > all skipped: testing all.t > t/alltest2/all..skipped > all skipped: testing more than one all.t > t/bad_codingok > > t/cookies...ok > > t/importok > > t/log_watch.ok > > t/log_watch_for_broken_linesok > > t/more/all..skipped > all skipped: cannot find module 'mod_perl.c' > t/next_available_port...ok > > t/ping..ok > > t/redirect..ok > > t/request...ok > > t/sok...ok > > All tests successful, 3 tests skipped. > Files=13, Tests=93, 24 wallclock secs ( 8.67 cusr + 6.69 csys = 15.36 CPU) > [warning] server loopback:8529 shutdown > [warning] port 8529 still in use... > ..done > > > > On Thu, Mar 1, 2012 at 9:01 PM, Jeff Trawick wrote: > >> On Thu, Mar 1, 2012 at 2:50 PM, Michael Felt wrote: >> > Want to get started on this. I read the links from >> > http://httpd.apache.org/test/ and think I understand the flood >> subproject. >> > From reading the forums here recently I get the impression that more >> than >> > flood is being used, or even something other than flood. >> > >> > Looking for assistance and suggestions. >> >> perl framework... >> >> get svn on your AIX box if you don't have it already >> >> check out /httpd/test/framework/trunk/ >> >> perl Makefile.PL -apxs /path/to/apxs >> t/TEST >> t/TEST -clean >> >> No it won't be fun because things will fail and there will be many >> different reasons, few if any obvious ones :) >> >> You will likely need to install more Perl modules... Some old >> instructions of mine: >> >>perl -MCPAN -e 'shell' >>cpan>install Test::Harness >>cpan>install URI >>cpan>install LWP::Protocol::https >>cpan>install HTTP::DAV >>cpan>install Bundle::ApacheTest >>cpan>install LWP::Simple >> >> (dunno if this is current or everything you need on your level of AIX; >> this was for OpenSolaris a couple of years ago) >> > >
Re: setting up testing
On 05 Apr 2012, at 12:03 AM, Michael Felt wrote: > I found some info on a mod_perl, and have picked it up via svn - but am stuck > - where does it expect to be? > root@x104:[/data/prj/modperl]perl Makefile.PL MP_APXS=/opt/httpd/bin/apxs > Reading Makefile.PL args from @ARGV >MP_APXS = /opt/httpd/bin/apxs > [ error] Can't find a sub-directory Apache-Test. Make sure that you are > using a complete source distribution Mod_perl is a completely separate project, it would need to be packaged separately. Regards, Graham -- smime.p7s Description: S/MIME cryptographic signature
Re: setting up testing
On Wed, Apr 4, 2012 at 4:13 PM, Michael Felt wrote: > Bother: I did not need to install any extra modules - and this has taken > forever, because I kept running into problems trying to install all the > extra modules. > What modules? > However, "Is this all there is?", and why do I not have a mod_perl.c - is > that a "tester/developer" only module, or just no longer in the "all" list? mod_perl is separate, but your test results imply the framework thinks you built almost no modules and thus ran the absolute bare minimum of tests. Most shared modules would be built and loaded in the default configuation, and there is a developer-mode flag to enable all the modules compiled. The test suite onl y tests modules enabled in your configuration. It finds them when you configure it (perl Makefile.PL...) > > Would you consider this a PASS for the tests? Yes, with an asterisk that seemingly most modules were skipped so most tests were not run. > > Files=13, Tests=93, 24 wallclock secs ( 8.67 cusr + 6.69 csys = 15.36 CPU)
Re: setting up testing
On 05.04.2012 00:10, Eric Covener wrote: On Wed, Apr 4, 2012 at 4:13 PM, Michael Felt wrote: Most shared modules would be built and loaded in the default configuation, and there is a developer-mode flag to enable all the modules compiled. The test suite onl y tests modules enabled in your configuration. It finds them when you configure it (perl Makefile.PL...) configure ... --enable-load-all-modules ... Or edit the installed httpd.conf by hand and uncomment the "LoadModule" lines of the modules you want to be tested. Roughly you can activate all of those lines, though I'm not sure whether there could be a few conflicting (don't think so). Regards, Rainer
