-BEGIN PGP SIGNED MESSAGE-
Moin,
On 23-Sep-02 Andy Lester carved into stone:
>> 4) WWW::Automate and WWW::Chat
>
> I've forked WWW::Automate as WWW::Mechanize, to make it a bit more
> robust, and to fix the bugs that have gone unfixed for at least six
> months.
>
> Also, I don't see an
> 4) WWW::Automate and WWW::Chat
I've forked WWW::Automate as WWW::Mechanize, to make it a bit more
robust, and to fix the bugs that have gone unfixed for at least six
months.
Also, I don't see any mention of content handling. My HTML::Lint and
its Test::HTML::Lint wrapper check the structure o
On 23 Sep 2002, Dave Cross wrote:
> A way to throw requests at various parts of the web site in order
> to test the a) correctness and b) speed of the responses.
For pure speed testing we use normally use http_load[1], as it allows us
to simulate many people with a 28.8Kb modem, which is totall
Ilya Martynov sent the following bits through the ether:
> 4) WWW::Automate and WWW::Chat
And recently petdance has updated WWW::Automate to WWW::Mechanize.
Personally I use a home-brewed solution which is very compact
test-wise, but I'm open to moving to something where other people can
underst
> On 23 Sep 2002 02:42:14 -0700, "Dave Cross" <[EMAIL PROTECTED]> said:
DC> What is the current state of the art in testing web apps.
DC> What we have:
DC> * mod_perl (Apache::Registry) web site
DC> * cookies (boo!)
DC> * frames (bigger boo!!)
DC> What we need:
DC> A way to throw requests
What is the current state of the art in testing web apps.
What we have:
* mod_perl (Apache::Registry) web site
* cookies (boo!)
* frames (bigger boo!!)
What we need:
A way to throw requests at various parts of the web site in order
to test the a) correctness and b) speed of the responses.
Is
