Testing methodology and outcomes.

[smythes]

Subjective vs Objective.

Qualitative vs Quantitative.

Would it be an idea to have a sticky thread with guides to these terms and what is helpfully required when it comes to testing/bugs and producing valuable information?

Edited August 6, 2011 by Smythes

[monsjoex]

Very helpfull, always when its open beta i don't really know what to test really.

For example when a patch broke the m10... it wasn't noticed because nobody started up a m10 and tried to drive with it.

[OLDZEKE]

Test it all. If you find a definate bug (not a I don't like this but a this is broke) then try to replicate it.

If you can replicate then post the game version number and bug in the post heading.

Post step by step the how to replicate and a short discription of the bug.

Sooo if for instance you deciede to check a pak36 and find that on deploy it flips on its back. You respawn that same unit and see if it does it again.

If it still flips on it's back on deploy then you post:

Example:

1.34.0.22 Pak36 fliping on deploy

Replication steps of the bug

*Spawn a pak36

*Deploy the pak

*pak flips on it's back

So basicly post if something is broken beound how it currently works (not OMG I still can't kill spits with a flak30!!!11111)

Keep it short and to the point with exact steps on how to replicate the bug.

[monsjoex]

Oldzeke i think we were more talking about in dept testing of new Beta versions.

Not the obvious.

[smythes]

Post is really asking - what is the difference between being Objective/Subjective?

What do both means in terms of value in feedback to the development of the game?

How do you tell one from the other and how do you give the best feedback for what CRS are looking for?

Most importantly - What are the benefits of doing the best sort of feedback?

[Sudden]

Maybe a list of equipment that still needs testing would help. Spawn in, check the list, pick something, test and report.