Hi All.
This is a silly question, but I’m open to ideas.
I have a program that is ready to “deploy” but I would like to have it beta tested so all of the bugs can be worked out of it… you know the ones the programmers don’t do but regular humans do (smile) WITHOUT deploying on something like the App or Play stores.
Any ideas?
Regards
I have a couple of customers who do beta testing for me.
Humans are generally lazy, even beta testers. Don’t expect most people seeing bugs to report them, unless they are really affected by it.
I recently had a bug that affected 600+ people. I got only one email reporting the error.
Make sure exception reports are sent to you automatically, you can use https://sentry.io with the XojoSentry set of classes I host on Github.
If you are looking to hire beta testers, you can try https://upwork.com
Make sure to prepare step-by-step instructions of what to do and a report to send back to you.
Is possible to get a brief explanation how Sentry works in order to know what to expect when implementing a solution like the one proposed by @Jeremie_L ?
Sure, Sentry is used for Application performance and error monitoring.
The free tier allows up to 5,000 errors (exception reports) per month, it took me almost two years of using Sentry to exceed that limit.
The greatest advantage in my point of view is error grouping which helps working on most urgent errors first.
I know many of us have written their own error report tool, even I did. But re-inventing the wheel is time consuming 
Exceptions are sometimes very difficult to reproduce. The amount of information sent to Sentry with each error report has been a huge help in fixing some exceptions.
Such as seeing that exception X only happens on Windows, or exception Y only happens to users running the app in Spanish.
Error reports can be completely anonymous which makes it GDPR compliant.
Here is what a Sentry error report looks like:
But that is only a small portion of the report.
Here is what I see below the fold:
Breadcrumbs allow me to see exactly what happened before the exception.
File attachment and screenshots can also be sent with exception reports.
Tags and Key/Value pairs can be added, for example to return the parameters of a URLConnection.ContentReceived event and understanding why an exception happened.
Don’t want to derail this topic so I will be opening a new one for discussing Sentry very soon.
