Find content
Male
But please do remember that the purpose of the beta is to give the devs feedback to make MWO the best game it can possibly be. To that purpose, please keep up to date with, and contribute to the beta/error reporting system in any way you can.
Now, for what is hopefully some useful information on what you might look for/encounter when testing.
Procedural errors:
When certain actions/choices matched together cause unexpected behaviour - In other words: Do A, Do B, Do C = error. To take an example of this sort of error from other games, by equipping/unequipping items in a certain order managing to generate configurations which shouldn't be possible. With a case like this the devs need to know the steps which generate the problem and any other specifics you can find.
Event errors:
When you’re playing along as normal and something unexpected goes wrong. Again to take from other games: clipping issues - where you fall through an object, or even out of the map entirely (Have seen this happen in several different games). In cases like this where we can't see a specific cause the devs need as much relevant information as possible, what mech was being used?, Map?, location?, and just what was happening which lead up to the issue.
Balancing:
The most unspecific category, yet just as critical. Apart from the inevitably ongoing discussion on weapon balancing there are always other balancing issues to consider, such as mech design and tactics. Remember we want to make it do as many things as possible, but avoid having any one thing be outright superior. Players should be allowed to make 'boating' setups, but they should not be outright better than others: also players should be able to use tactics such as 'scout rush' or running mostly assaults, but if one tactic wins 9 times out of 10 then we have a problem.
So, as you play:
Make sure the devs are aware of any problem you encounter.
Check if anyone else has reported the error before opening a new topic; if they have, just add any new information you can to the existing conversation.
And never forget...
HAVE FUN
Additions suggested in the following conversation:
Blackfire1, on 23 May 2012 - 02:49 AM, said:
When you test TRY to break the game in as many ways as possible and tell the Devs about it asap. If you can break it in testing and it get fixed for later. You probably kept an entire string of errors from popping up.... sometimes. 
