t/50-app-new.t .................... 6/8 # Failed test 'The name is "Standard"' # at t/50-app-new.t line 46. # got: 'Default' # expected: 'Standard' # Looks like you failed 1 test of 8.
Ouch - the name of the "Default" theme in Firefox is localized. I have to take care of that in my tests, likely by not testing for the name but the UUID of the theme.
t/50-mech-bufsize.t ............... 4/8
If that test hangs, this is bad for large webpages. It loads an image-heavy deviantart.com page, so that should work in any case. Maybe this is an issue with your proxy setup, but without knowing more about it, that'll be hard to replicate.
It would be nice if you could tell me what tests fail (and how) with your proxy, as that would help me make the tests (and maybe the module) more resilient against the proxy results.
t/70-urlbar.t ..................... 1/2 # Failed test 'We changed the location once' # at t/70-urlbar.t line 48. # got: '0' # expected: '1' Use of uninitialized value $this in pattern match (m//) at t/70-urlbar +.t line 49, <DATA> line 1. # Failed test '... to that other page' # at t/70-urlbar.t line 49. # undef # doesn't match '(?-xism:/70-urlbar-2.html$)' # Looks like you failed 2 tests of 2. t/70-urlbar.t ..................... Dubious, test returned 2 (wstat 51 +2, 0x200) Failed 2/2 subtests
These test failures are weird, as they also seem to indicate that the script does not receive some Firefox events. I'm not sure what to make of that.
In reply to Re^3: WWW::Mechanize::Firefox delayed returns / slow
by Corion
in thread WWW::Mechanize::Firefox delayed returns / slow
by tcordes
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |