Betas and You: A Guide to Beta Games

[Chrysalis]

/* After reading the forums and seeing many posts of confusion on what "beta" means, and what testers are here to do, I decided to write up a little reminder. Hopefully, this information helps new and current players alike in being the best Beta Testers they can be. I'll just assume this is entirely the wrong board for such things though (since it isn't really Gameplay Feedback), and anticipate the thread being moved/locked/deleted. It's okay, I've braced myself. */

As gamers, we live in a world of many luxuries. From user sourced content to feedback boards, the player is now part of game development. In some cases, however, companies wish to take things a step farther than suggestions; they want player feedback before releasing a "finished product." This is where we come in: Beta Testing. Open or Closed, betas are usually similar in purpose. The developers wish to test certain aspects of their game, and need help to do this. From out-of-map glitches, to UI catastrophes, and even full server failure, Beta Testing shows the problems BEFORE they get out to the general public.

Yes, that's right folks, we're not the only ones who will play this game! There are thousands of people who will come pouring in on release day, but what will they find after opening their game? Well, that part is up to us. With HELPFUL, WELL-CONSTRUCTED CRITICISM (positive or negative), we help the developers get pointed in the right direction. By submitting support tickets when things don't work, we help iron out the nasty bugs, so no one else will experience them. Sure, the developers need to bring their A-Game to the table to be successful (no pun intended), but they also rely on a little help along the way.

So, how can we be good beta testers? We can start by following a few easy guidelines.

DO:

Voice your opinion with emphasis on DETAIL

Give specific EXAMPLES when doing so

Submit BUGS you find

Discuss FEATURES you might wish to see

Help NEW USERS in the forums (everyone starts somewhere!)

Ask for COMMUNICATION with Devs

Be POLITE, remembering to say please and thank you

DON'T:

Verbally ATTACK anyone (especially not Devs, are you crazy?)

COMPLAIN without very specific reasoning

BEG for your feature to be implemented

Flip out over BUGS you DIDN'T SUBMIT

Be ANGRY, ever (please?)

Compare a beta to UNRELATED MATERIAL

Expect changes to be IMMEDIATE

It's tough being a developer. Even with showers of praise and the faith of Founders behind their backs, they have feelings much like you or me. Criticism isn't always easy to take, so if you have something negative to say, make it easy to swallow. Include the good with the bad, the bolstering with the butchering. At the end of the day, we'll all walk away better for it, and with much improved games and communities to boot! Okay, so maybe it's an optimistic goal, but the least we could do is try.

Do you have any tips for new beta members? Share them! Remember, we're in this together, and we should make the most of it.

Edited January 13, 2013 by Chrysalis

[Crond]

I think this message should must be displayed right near the "Beta Test Agreement" and EULA.

Edited January 13, 2013 by Crond

[BlackDogCpt]

good post!

[Rusalki]

https://forums.warframe.com/index.php?/topic/28-closed-beta-agreement-read-me/#entry117

Not that anybody reads it.

They really need to make a script that makes sure you read that, and hit "I have read and understand these terms and conditions" before forum accounts are allowed to post.

[AmmokK]

The following post i found a while ago in another forum. It´s pretty useful, so read it.

As a beta tester for many games, I'm particularly experienced with what to do and how to do it in betas. But many people aren't actually aware of what they're supposed to be doing here. (They think this is just a head start or free ride to get into and play a new game; this is far from the true point of being a beta tester.)

The majority of the following comes from guides that have been found while beta testing other games. Such an incredible resource deserves to be shared.

1) Keep a pad of paper and writing utensil next to you at all times. Write down everything you do that has odd/unintended consequences for an accurate report and post the reports. Even better if they provide client side log for further details. Be sure to use a proper format. Here an example i copied from another game:

**For game mechanic bugs**

Step1: (this is the first step to making this bug occur)

Step2: (this is the second step to making this bug occur)

Step3, 4, 5 etc: (if necessary)

Description: (describe what happens)

Expected: (describe what SHOULD have happened.)

*Screen shots encouraged!*

------

**For text bugs (typos, grammatical errors)**

Location of text: (where in the game did you find this text)

Incorrect Text: (type the incorrect text here)

Corrected text: (what the text should look like)

*Screen shots encouraged!*

2) You will likely crash often during testing. Patience is a virtue here and is part of the process. Remember, this is a test wherein you work for the company in providing feedback and making the game better. This is not an opportunity to learn secrets of the game for when it goes live.

3) Every step of the way, you actually are doing your job if you make the game crash. Report what you were doing in a post. Start with the character creation screen. Try multiple combos of clicks and keystrokes, combos of creation options, watch the graphics, try ridiculously stupid possibilities for names (such as names including numbers and punctuation marks), listen for sound artifacts and errors, animation stalls, etc.

4) When in the game, consider the environment. Look for holes, mismatched effects, trees floating in the air, etc. Take notice of your surroundings and the animations. Do avatars move smoothly, are some colors out of whack etc.

5) UI is next. Try everything, even stuff that no one would normally even consider during normal gameplay. The plan is to find problems and break the game, so just go nuts. Try opening trade windows with mobs/guards/villagers, try buffing mailboxes and attacking tables, anything that seems out there try it.

6) Read all dialog and quest descriptions. (I know this step is going to be extremely difficult for most "beta testers".) Check for spelling errors and grammatical issues. Most players gloss over familiar words but make sure to pay attention as sometimes even the simplest things are missed, especially with smaller dev teams working day and night on their vision. Don't miss the forest for the the trees. (Did you see what I just did there? Keep an eye out for that in-game!)

This point is actually not needed in Warframe (for now?), yet it´s useful to know.

7) Experiment with all social options, any available emotes, chat windows, and the controls for those. How is the learning curve; is info available and intuitive to the nature of the game? Even style choices can be a source of beta testing reports if it makes the player experience better.

8 ) Make sure whatever you test, test it again. If you find a bug, try repeating it and write down what you find out. Until a bug can be recreated on a regular basis, it's not really a bug. The more info you can provide in a report, the better.

9) Be creative, do things you wouldn't normally do, and always report what you find.

Anyone with further tips or feedback please post here for benefit of all beta testers. Good luck and happy hunting beta testers of Warframe.

And here another (official one) from the devs of Hawken:

2. In house Beta/Closed Beta.

This is where a majority of all bug are found. As the products and systems get more complex and polish is slowly added. Things don't like to work together. Once a program is 50%-80% done you will see "Closed beta" which is for those special invited few to give a completely untrained perspective to the product. This also includes constructive ideas on making the product better and also thinking outside the box to find the truly bizarre Bugs.

3. Open Beta/ Soft launch.

This is now show time. Depending on the program/product this can make or break it. Games tend to get prejudged on open beta simply because this is a general show off our product time. Yes, bugs are still going to be fixed. Also this is a great time to prepare the servers for the loads its going to meet at Launch.

However, what is a Soft Launch? This is something you will only find in the Free-2-PLay genre. Its there the game is nearly 100% complete however they are perfecting it into something people will buy money for. Its where there are no longer character wipes, patches come preplanned (sometimes), and cash shops open to give those willing the ability to advance farther then others. Its still "in beta" but everything gained from the user side is permanent. The system however is free to change.

4. Launch.

You will find this on most AAA or AAB titles. Most have subscription free. And if it goes BAD. It can very well destroy a game. Its one of the reasons Number 3 had become very popular.

---------------------------------------------------------

I'm now a tester, what do I do?

At all times try to remember you're not here to "just have fun." You as a tester are not ENTITLED to anything. You are lucky to be here and the best thing you can do is make sure the game you are testing is the best it can be. However try to play the game as the Devs would want it played. That isn't to say you can't have fun. Its just not the primary directive. Also think outside the box and try to exploit any type of thing you can. Its one of the only time Exploiting in the game is OK as long as it is reported for the Devs to fix. Think outside the box, smash buttons, and try odd key combos.

Tips & Tricks

1. The install. Make sure you take notes on install location, along with any background programs running at the time. If your antivirus flags and says the game or program is a virus. Turn it off install and turn it back on. If it still says its a virus report it to the Devs. Anti-Virus software looks for virus like programming patterns. Just because its a pattern doesn't mean its a virus however.

2. Take notes.

Write it all down. There will be times you forget things simply because of sensory overload.

Try to keep an idea of your over all experience while playing. What felt right? What felt confusing? Was there any glitches or bugs that you see instantly?

3. Find a bug, try to recreate it.

If you find a problem. Retry to recreate it. Make sure you remember/write down your steps you used to cause the problem in the first place. Chances are if its more then 2-4 steps not everyone has noticed it. This can also including taking pictures of error messages and explaining in detail the results of the problem.

4. Report bug(s).

These can come as graphical errors, typos, ability errors, gameplay problems such as not getting XP, money or rewards, ect.

Generally you will report the bugs as you see them, giving as much information as you can muster. If you can repeat it, tell your steps. Most ways to report bugs are:

Support email - Send them an email of all the NEW bugs you find.

Ingame Bug Report option - Some games have an in-game option to report a bug. Most of the time they are AAA mmo's that take a snap shot of all your current information at the time of the sending. Many F2P games don't have this as most bugs need for information then a simple snap shot.

Forums - This is the place to make your own bug thread not to mention give feedback on general aspects of the game. Does the animations look right, if there clipping, does the AI react to orders properly, does the layout of the GUI work so that its not overly confusing. This is there most of all things reported will be posted. Not to mention it generally gives a more direct contact between the Devs and the Testers. Allowing other testers to see if a bug is common or not.

The forums are also a great place to give CONSTRUCTIVE CRITICISM. Meaning if your going to judge, you better have an idea of fixing something then just complaining.

-------------------------------------------------------------------------------

Patches

1. Read the patch notes and look at whats changed. Keep in mind what is easy to see/experience change wise and what will take some digging in-game to find.

2. Record any problems you find that are caused by the patch or are "fixes" from the patch that went wrong.

3.Re-read your first impression notes to compare and contrast how much this patch benefits the program in a long run. Try to keep an honest opinion. If a patch break entire chunks of game play feel free to mention it. CONSTRUCTIVELY.

-----------------------------------------------------------

Common Tester Format

Problem: (quick description of problem)

Detailed Description (This is where you flood as much information as you can)

Time: (sometimes relevant if soon after patch, could indicate server problems)

Location during issue: (Don't say in my house. Examples: Armory, battle field, middle of logging in, ect)

What you were doing when problem occurred: (Refitting stuff, Buying ingame items, Fighting Monster, crafting, ect.)

Steps to repeat problem: (If you tried to recreate the problem, what did you do to duplicate it.)

Log files and/or DXDiag: Many games take in-game log files during crashes or problems. At times if you can repeat a bug its best to erase the log file folder, cause the bug, and then send the single log file made at the time.

Error codes/pictures would be placed after giving as much information as possible along with your System Specs. A DXDiag can be handy at times as it lists all the programs running at the current time after a crash. Devs during testing are like Detectives. They need all the clues to pinpoint the suspect. Some games also have build in log files the devs can use too. If there is an ability to upload these directally to the devs, do it.

Edited January 13, 2013 by AmmokK

[Chrysalis]

That's a lot of useful information right there. Thanks for the addition!