There's a new version of WWW::Mechanize for you people who do automated
testing with it. It adds a title() and is_html() method, and removes
the dependency on Clone, which I hope will fix stability issues on
Windows.
xoa
--
Andy Lester, lead singer & driver of the Winnebago
[EMAIL PROTECTED],
-BEGIN PGP SIGNED MESSAGE-
Moin,
On 04-Mar-03 Andy Lester carved into stone:
> There's a new version of WWW::Mechanize for you people who do automated
> testing with it. It adds a title() and is_html() method, and removes
> the dependency on Clone, which I hope will fix stability issue
Damn. I still forgot to check out this incredible cool sounding
module, I
have some HTML-output testing in a testsuite and it is very whacky and
uncomplete...
I'd be glad to look at it, and see what kinds of things Mechanize can
do.
xoa
--
Andy Lester, lead singer & driver of the Winnebago
[EMA
Le mercredi 05 mars 2003 à 19:38, Robert Spier écrivait:
>
> > There really aren't many tests that are meaningful without that access.
> > 00.load.t, 99.pod and add_header.t are all that seem to be valid
> > without it.
>
> You could allow the user to choose between internal and external
> te
Andy Lester said:
> There's a new version of WWW::Mechanize for you people who do automated
> testing with it. It adds a title() and is_html() method, and removes
> the dependency on Clone, which I hope will fix stability issues on
> Windows.
Nice, thanks.
I installed it on a machine at work,
You could allow the user to choose between internal and external
tests, where the internal tests are much simpler, maybe including a
trivial self-contained webserver to make sure everything works.
Help me out here. I'm trying to imagine why someone would want
WWW::Mechanize without a net connecti
I installed it on a machine at work, and a large number of tests failed
because the machine has no access to the outside world. Fixing that is
probably more effort than it is worth, but you might want to keep it in
mind for the next major rewrite.
There really aren't many tests that are meaningful
> Help me out here. I'm trying to imagine why someone would want
> WWW::Mechanize without a net connection. Or are you saying that people
> will want to use it strictly behind a restrictive firewall where
> google.com isn't accessible?
Yes.
-R
Andy Lester sent the following bits through the ether:
> Or are you saying that people will want to use it strictly behind a
> restrictive firewall where google.com isn't accessible?
For example, we use it at work for testing our web applications. The
slightly overly-secure server we use for deve
For example, we use it at work for testing our web applications. The
slightly overly-secure server we use for developing can not see the
Internet, but it can test on localhost or other internal
servers. (There's a local CPAN mirror and other such things to make it
bearable).
I've created RT ticket
> "AL" == Andy Lester <[EMAIL PROTECTED]> writes:
>> For example, we use it at work for testing our web applications. The
>> slightly overly-secure server we use for developing can not see the
>> Internet, but it can test on localhost or other internal
>> servers. (There's a local CPAN mirror
-BEGIN PGP SIGNED MESSAGE-
Moin,
On 06-Mar-03 Andy Lester carved into stone:
>> You could allow the user to choose between internal and external
>> tests, where the internal tests are much simpler, maybe including a
>> trivial self-contained webserver to make sure everything works.
>
> H
> There really aren't many tests that are meaningful without that access.
> 00.load.t, 99.pod and add_header.t are all that seem to be valid
> without it.
You could allow the user to choose between internal and external
tests, where the internal tests are much simpler, maybe including a
trivi
Le jeudi 06 mars 2003 à 10:43, Andy Lester écrivait:
> >For example, we use it at work for testing our web applications. The
> >slightly overly-secure server we use for developing can not see the
> >Internet, but it can test on localhost or other internal
> >servers. (There's a local CPAN mirror an
14 matches
Mail list logo