H&K's suggestion is spot on!
I would include some form of debug-logging with your beta release, at least to give YOU soe idea of what crashes and where, even if your testers are unable to identify the exact reason. Have them email you the debuglogs or something in event of crashes/errors.
Prior to a Beta release, you should have held an Alpha Testing session, (mainly just yourself, other developers or people from H&K's "first group").
The Alpha session will ensure the game is pretty free of most crashing and code errors, while the Beta test is to evaluate gameplay, compatibility issues, exploits etc. finally, tweaking.
I would include some form of debug-logging with your beta release, at least to give YOU soe idea of what crashes and where, even if your testers are unable to identify the exact reason. Have them email you the debuglogs or something in event of crashes/errors.
Prior to a Beta release, you should have held an Alpha Testing session, (mainly just yourself, other developers or people from H&K's "first group").
The Alpha session will ensure the game is pretty free of most crashing and code errors, while the Beta test is to evaluate gameplay, compatibility issues, exploits etc. finally, tweaking.