comment on

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?

In reply to Re^7: Chrome freezes on windows when opened with WWW::Mechanize::Chrome by Bod
in thread Chrome freezes on windows when opened with WWW::Mechanize::Chrome by bakiperl

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Your skill will accomplish what the force of many cannot
	PerlMonks