Anthony Gardner wrote:
I'm trying to think of a way to do a test plan for a site that is already well developed but is going through a structural change rather than a content change.To cut a long story short, for future development we want to implement a good test suite to test the html in the response. At present, they just do visual tests.From what I've seen on CPAN, Apache::Test is used to test Apache::* modules (we don't write any at this time) and Apache::TestRequest is looking good for me ..... but is it what I want?For example, to catch the final output from the response phase of the request and then test the resulting (potentially large) html to see if there is a small chunk of expected html there (i.e hiden fields).This may sound like bread 'n butter to most of you but any suggestions would be greatly appreciated.
You might look at HTTP::Webtest or WWW::Mechanize Also, httpd-serf and httpd-test from the httpd.apache.org. Apache-Test is more for testing your PERL code -- but theres nothingreally stopping you from using it to issue requests to "handlers" then check the responses though I wouldn't recommend it.
-- ------------------------------------------------------------------------ Philip M. Gollucci (suppressed) 323.219.4708 Consultant / http://p6m7g8.net/Resume/resume.shtml Senior Software Engineer - TicketMaster - http://ticketmaster.com 1024D/A79997FA F357 0FDD 2301 6296 690F 6A47 D55A 7172 A799 97F I never had a dream come true 'Til the day that I found you. Even though I pretend that I've moved on You'll always be my baby. I never found the words to say You're the one I think about each day And I know no matter where life takes me to A part of me will always be... A part of me will always be with you.
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.