So it is better that my module doesn't stop the website from working, it allows the site creator to check for errors and get an idea of what the error is
Yes Bod, you're on the right track here. While unit tests help the developer create better quality modules, that is a different problem to remotely supporting a software product!
As mentioned in passing here, effectively supporting a complex product remotely isn't easy. Unit tests are not enough. You'll need to provide some sort of logging and notification mechanism, without degrading user experience. (For a gentle introduction to Log::Log4perl, see Logging with Log4perl (perlmaven)).
Unfortunately, I am not qualified to comment on how best to support and troubleshoot a Stripe Payment Gateway. Have you researched how others do it?
In reply to Re: Error handling in a module
by eyepopslikeamosquito
in thread Error handling in a module
by Bod
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |