Re^6: Chrome freezes on windows when opened with WWW::Mechanize::Chrome

Thanks for posting the log!

Looking at it, there is some redirect loop going on that I don't hit when I'm testing - that's one of the drawbacks of running tests against external servers...

I don't see a good/quick fix, but as the test suite progresses somewhat, it seems sane to force-install the module, skipping the test suite.

I'll look at rewriting the test using only local resources so it doesn't trip with the next (regional) behaviour change.

Comment on Re^6: Chrome freezes on windows when opened with WWW::Mechanize::Chrome

Replies are listed 'Best First'.

Re^7: Chrome freezes on windows when opened with WWW::Mechanize::Chrome
by Bod (Parson) on Oct 20, 2021 at 21:47 UTC

Thanks for posting the log!

No problem at all...thanks for creating what looks like an extremely useful module!

that's one of the drawbacks of running tests against external servers...

Yes - when I wrote the tests for Business::Stripe::WebCheckout, I tried to get it to connect to my server during testing with dummy public and private keys. Although the test server gave the right response to a browser, it always failed when the Perl tests tried to access it. The required code for testing mode is still in the module...

choroba helpfully shared a blog over on Re^5: [RFC] Module code and POD for CPAN - Testing and test file

That blog is a bit beyond me at present so I had planned to go back and revisit Business::Stripe::WebCheckout. I have not done that yet and really should.

Perhaps there is a need for a module to help with testing modules that need to connect to external services?

[reply]


Perl: the Markov chain saw
	PerlMonks