Beefy Boxes and Bandwidth Generously Provided by pair Networks
Problems? Is your data what you think it is?
 
PerlMonks  

Re: Application Testing: Custom Module or Perl Test Files?

by jimX11 (Friar)
on Sep 08, 2005 at 04:11 UTC ( #490078=note: print w/ replies, xml ) Need Help??


in reply to Application Testing: Custom Module or Perl Test Files?

Using HTTP::Recorder to help start building tests with WWW::Mech is smart. Using Test::WWW::Mech is better. But using Test::WWW::Mech inside of Apache::Test is really powerful.

Apache::Test, a subproject of the Apache HTTP Server Project, provides the framework for what web apps need. What do web apps need? Well, a configured web server.

Configuration to determine:

  • the location of the log files
  • the location of the htdocs
  • maybe the location of your perl modules
  • maybe you have specific configuration, I like my cgi-bin outside of my htdocs, so I often alias the cgi-bin dir.

You don't really care about those things when you're testing. You just want to think about the tests.

Apache::Test (A-T) takes care of all of that for you, you just provide the tests.

And A-T works great with CVS (and SVN). Sure you can use test suite build only on Test::WWW::Mech in cvs, but it's often inflexible - the tests are often in a different location that the web server. A-T essentially bundles the httpd.conf with your perl modules and your perl scripts and your tests. Everything you need is in one place. So with A-T you can just check out a copy of your code in a different sandbox and hack away. No need to tweak the httpd.conf files to point to a different location.

A-T, and test suites in general, make maintenance so much easier. Say you have a mod perl 1 app and want to move it to mod perl 2. If you have a test suite (either using A-T or not), you can run the test suite on it. But running the test suite on different version of perl and apache is really easy in A-T. I've seen A-T guru Geoffrey Young quickly and easily run a test suite on different combinations of version of Perl and Apache.

If you develop your web app with care you'll almost always have tests that test things outside of the web app. A-T can handle that for you to.

I'd say the biggest hurdle is setting up A-T, but you only do that once (per server configuration). And there are skeletons to help you do that.

A-T works with perl cgi scripts, Apache::Registry, mod perl and even php.

The docs are helpful - I'd like to help reorganize them but have done nothing at all to help yet.

Geoff, who is often helpful on the A-T mailing list wrote this article.


Comment on Re: Application Testing: Custom Module or Perl Test Files?
Re^2: Application Testing: Custom Module or Perl Test Files?
by ghenry (Vicar) on Sep 08, 2005 at 20:50 UTC

    I will definitely be researching Apache::Test.

    I like the look of Flood, as a profile-driven HTTP load tester.

    Walking the road to enlightenment... I found a penguin and a camel on the way.....
    Fancy a yourname@perl.me.uk? Just ask!!!

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://490078]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others musing on the Monastery: (10)
As of 2014-07-14 06:51 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    When choosing user names for websites, I prefer to use:








    Results (255 votes), past polls