Do's
- Have hardware and an internet connection that meets the minimum system requirements
- Read the notes and messages when provided with beta access. They will often be unique to the beta and provide information critical to testing and submitting feedback.
- Be patient – there will be some time spent downloading, installing and patching, it’s part of being involved in the beta.
- Keep a pad and pen handy for scribbling down your thoughts and details of bugs and exploits
- Try and play across all game modes, factions, maps, characters and unit types.
- Focus on overall game balance to make the game better for everyone
- The unexpected – try things that the developers might not have considered.
- Try and reproduce a bug before reporting it
- Check the forum for known bugs first when you find a bug, if it’s already been reported there’s no need to report again but do add to the thread if you find something new
- Submit clear, methodical and well structured reports with suggestions for improvement - use the B3TA connect template as a guide to submitting reports
- Submit proof where possible, screenshots are generally a good idea.
Don't
- Expect the software to work perfectly, that’s the whole point of a beta test – to iron out the bugs before launch
- Complain about server downtime, bugs and patches, if these things bother you’re probably not cut out for beta testing
- Use a lot of jargon, acronyms, or abusive language on forums or in reports
- Start a new thread if the subject is already logged or resurrect old threads from a previous beta
- Spend time make subjective calls on design or styling, a beta is first and foremost about functionality
- Continue to exploit bugs once you find them, this could get you banned from participating in the testing.
- Respond to trolls, they are trolls.
Anything to add? Submit your comments below.
Comments
Post a Comment