Sim_Master
24 Mar 2001, 10:46 PM
Well, I snagged this off of Beta Bites and thought I would post it here. Please don't be mad at me Lockup.
This is based on beta testing games for the most part. Any Way, enjoy the article.
quote:
--------------------------------------------------------------------------------
If so, you need to ask yourself---Do you really want to test the game or the product, or are you looking for a Freebee? You should not even consider testing if all you want is the product. The Companies go to a lot of expense to hold their tests, and the least you can do is uphold your end of the bargain. A very good article entitled, To Test… or Not to Test? - Qualities of an Exceptional Beta Tester has been written by Gaile of Diabloii.net. You may want to check it out first to see whether you can really cut the mustard.
The Example
Ooh!!! You have just signed up to test that really cool looking new action game, ABC! Today, you received news from the game company, an acknowledgement that YOU have been accepted to test ABC. Now what? How do you test a game?
First, remember that the game companies have given you this opportunity to test their game. Sure you get to check out what the game is like, but you have been recruited to find the bugs in the beta game. Testing is what you have been recruited for not playing the game!
Second, anytime you test an Alpha or Beta game, you agree to a disclaimer not to reveal, communicate, or otherwise, publish any information regarding the game. Do not under estimate this oath. You have been selected to test, and to keep confidential all elements of the testing procedure unless you have received a written or verbal agreement.
Last, if you cannot meet the game companies testing requirements, don't sign-up for the test. If you agree to test for 6 hours a week, then you better be able to put in that amount of time each week. The system testing requirements are very important. If the game company wants a Pentium II with at least 233Mhz. & 32 RAM, and you own a Pentium 133Mhz. with 16 RAM, don't fake it --- because you don't have the power that the game company needs to test game ABC. You will be having bugs due just to your computer system.
The mail has just arrived, and guess what? Your ABC Beta CD has just arrived in your mailbox! YeeHaw! It's testing time. Now wait! Hold on a minute---before you rip open that cellophane wrapping that is childproof---READ the materials sent with the game. Anytime you test a product (because it is an Alpha or Beta), it is most definitely going to have BUGS. Those bugs can begin with the installation. So, read, and re-read the information sent to you. Everything from incompatible sound or video cards should be in the materials IF it is known...and the possible fixes that can be done for these incompatibilities .
The Preparation
Tools of the trade---what do you need? Well, first throw the cat off the keyboard, it makes for rather difficult testing. Make sure you have read the manual, and know the keyboard/mouse controls. It doesn't do you much good to test if you don't know how to play the game. Always play a couple of games of single player before attempting multiplayer.
You MUST always have paper & pen handy...I don't care if the product has its own bug reporting tool. It never fails--- your system freezes or crashes and an error is reported, but you must shutdown and reboot. Unless you have a photographic memory, write that sucker down because the bug reporting tool is also going to be frozen. Now, I have crashed and received errors (even little ones), and I think I will remember them until I finally realize I have forgotten through the troubles of rebooting and scanning disk
I always like to have either my clipboard or notepad opened and sitting in the taskbar for easy access. Here's why: You have just got a bug (cute little devil until it wrecks havoc with your PC), and windows is reporting an error. Read the "details" of the java error box, and copy and paste that sucker into the clipboard or notepad for safe keeping. Remember to "save as" or all maybe lost. If you have a bug reporting tool, then copy the error details into the reporter (and save)! You never know just what is going to happen when you "close" that error box---sometimes, you just end the game---sometimes, nothing happens and yes, it's time to shutdown, and reboot once again.
Bug Reporting Tools: These are great tools to have when testing because there is generally an option to set up your personal and system information in them. Many have the option of sending reports right from the tool (see the next page for types of tools).
Now, sit back and relax---it's time to test!
It's Testing Time!
The game is installed and all installation bugs have been recorded. Installation can always be a big downfall for if you can't get the product to install, you can't test it. Now grab your favorite beverage, and start the game. The first time you play it may be difficult to tell what is a bug or glitch, and what is not. Be sure and note anything out of the ordinary.
Crash!!! Yeppers, you just got your first bug. Now, don't panic! If you're going to be a tester, you need to realize there are going to be system freezes, windows errors, & crashes. Do not forget the famous CTRL+ALT+DELETE to help you get out of these messes. Record exactly:
* What you were doing at the time you bit the big one
* Report any strange occurrences before you bit the big one
* Were you doing anything else at the time while testing (ex: using ICQ)
* Report exactly what the Company has requested (some want stack files, some don't)
* Steps To Duplicate (STD)---The exact steps you took when the problem occurred .
Ex:
1) Located a server
2) Joined the Multiplayer game
3) Launched and loaded
4) System Froze on loading
5) CTRL+ALT+DELETE to exit
* Now in your head re-visit the scene, and see if you left any detail out (sometimes it's the little things that causes the big crashes)
* Send off the Report and it's wise to keep a copy in the Bug Safe (folder).
Continue to test, and report your problems to the company. Be sure and check out the forum boards for problems other testers have encountered---don't expect the QA Department to resolve all your problems. This is generally left to testers helping testers (although, I have been in some tests where the QA Dept. is very helpful---don't count on it though)! Plus, you can expect multiple updates and patches to download.
Congrats! You are an official Beta Tester!
--------------------------------------------------------------------------------
------------------
"So you call this your free country; Tell me why it cost so much to live"
This is based on beta testing games for the most part. Any Way, enjoy the article.
quote:
--------------------------------------------------------------------------------
If so, you need to ask yourself---Do you really want to test the game or the product, or are you looking for a Freebee? You should not even consider testing if all you want is the product. The Companies go to a lot of expense to hold their tests, and the least you can do is uphold your end of the bargain. A very good article entitled, To Test… or Not to Test? - Qualities of an Exceptional Beta Tester has been written by Gaile of Diabloii.net. You may want to check it out first to see whether you can really cut the mustard.
The Example
Ooh!!! You have just signed up to test that really cool looking new action game, ABC! Today, you received news from the game company, an acknowledgement that YOU have been accepted to test ABC. Now what? How do you test a game?
First, remember that the game companies have given you this opportunity to test their game. Sure you get to check out what the game is like, but you have been recruited to find the bugs in the beta game. Testing is what you have been recruited for not playing the game!
Second, anytime you test an Alpha or Beta game, you agree to a disclaimer not to reveal, communicate, or otherwise, publish any information regarding the game. Do not under estimate this oath. You have been selected to test, and to keep confidential all elements of the testing procedure unless you have received a written or verbal agreement.
Last, if you cannot meet the game companies testing requirements, don't sign-up for the test. If you agree to test for 6 hours a week, then you better be able to put in that amount of time each week. The system testing requirements are very important. If the game company wants a Pentium II with at least 233Mhz. & 32 RAM, and you own a Pentium 133Mhz. with 16 RAM, don't fake it --- because you don't have the power that the game company needs to test game ABC. You will be having bugs due just to your computer system.
The mail has just arrived, and guess what? Your ABC Beta CD has just arrived in your mailbox! YeeHaw! It's testing time. Now wait! Hold on a minute---before you rip open that cellophane wrapping that is childproof---READ the materials sent with the game. Anytime you test a product (because it is an Alpha or Beta), it is most definitely going to have BUGS. Those bugs can begin with the installation. So, read, and re-read the information sent to you. Everything from incompatible sound or video cards should be in the materials IF it is known...and the possible fixes that can be done for these incompatibilities .
The Preparation
Tools of the trade---what do you need? Well, first throw the cat off the keyboard, it makes for rather difficult testing. Make sure you have read the manual, and know the keyboard/mouse controls. It doesn't do you much good to test if you don't know how to play the game. Always play a couple of games of single player before attempting multiplayer.
You MUST always have paper & pen handy...I don't care if the product has its own bug reporting tool. It never fails--- your system freezes or crashes and an error is reported, but you must shutdown and reboot. Unless you have a photographic memory, write that sucker down because the bug reporting tool is also going to be frozen. Now, I have crashed and received errors (even little ones), and I think I will remember them until I finally realize I have forgotten through the troubles of rebooting and scanning disk
I always like to have either my clipboard or notepad opened and sitting in the taskbar for easy access. Here's why: You have just got a bug (cute little devil until it wrecks havoc with your PC), and windows is reporting an error. Read the "details" of the java error box, and copy and paste that sucker into the clipboard or notepad for safe keeping. Remember to "save as" or all maybe lost. If you have a bug reporting tool, then copy the error details into the reporter (and save)! You never know just what is going to happen when you "close" that error box---sometimes, you just end the game---sometimes, nothing happens and yes, it's time to shutdown, and reboot once again.
Bug Reporting Tools: These are great tools to have when testing because there is generally an option to set up your personal and system information in them. Many have the option of sending reports right from the tool (see the next page for types of tools).
Now, sit back and relax---it's time to test!
It's Testing Time!
The game is installed and all installation bugs have been recorded. Installation can always be a big downfall for if you can't get the product to install, you can't test it. Now grab your favorite beverage, and start the game. The first time you play it may be difficult to tell what is a bug or glitch, and what is not. Be sure and note anything out of the ordinary.
Crash!!! Yeppers, you just got your first bug. Now, don't panic! If you're going to be a tester, you need to realize there are going to be system freezes, windows errors, & crashes. Do not forget the famous CTRL+ALT+DELETE to help you get out of these messes. Record exactly:
* What you were doing at the time you bit the big one
* Report any strange occurrences before you bit the big one
* Were you doing anything else at the time while testing (ex: using ICQ)
* Report exactly what the Company has requested (some want stack files, some don't)
* Steps To Duplicate (STD)---The exact steps you took when the problem occurred .
Ex:
1) Located a server
2) Joined the Multiplayer game
3) Launched and loaded
4) System Froze on loading
5) CTRL+ALT+DELETE to exit
* Now in your head re-visit the scene, and see if you left any detail out (sometimes it's the little things that causes the big crashes)
* Send off the Report and it's wise to keep a copy in the Bug Safe (folder).
Continue to test, and report your problems to the company. Be sure and check out the forum boards for problems other testers have encountered---don't expect the QA Department to resolve all your problems. This is generally left to testers helping testers (although, I have been in some tests where the QA Dept. is very helpful---don't count on it though)! Plus, you can expect multiple updates and patches to download.
Congrats! You are an official Beta Tester!
--------------------------------------------------------------------------------
------------------
"So you call this your free country; Tell me why it cost so much to live"