Hi Kelipski,
We appreciate your great suggestion and I can assure you we plan to provide plenty of guidance on what we'd like tested, how to verify and report issues, omni-validation, etc..
Once it is appropriate and we are closer to our Alpha I, II, Beta I, and Beta II development phases, we'll release more details to those who will be participating.
Thank you!
"Stupid questions make more sense than stupid mistakes."
Hopefully the alpha clients will come with log output, but describing the exact nature of when your issue occurred, what you were doing etc is the most obvious start point. The more detail, usually the better. Aside from the error or bug details, if applicable, logs, technical specs etc may be desirable. You can get a summary relatively easily via dxdiag (run it from your run prompt and save the output).
I suspect everything from technical bugs to exploits and things not working properly are welcome as well as typically and constructive feedback you can come up with.
That said, watch out for SBS posts - these guys are the authority ;)
Go in everything, hit everything, try to jump over everything, try to go under everything, try every emote, everywhere, the list is quite endless as to how you can effectively help test as there's no wrong way to go about it though I assume your question is referring to how to test effectively and make proper reports.
