This is the place for information on how to write good bug reports. Good bug reports get bugs fixed faster, so we strongly encourage you to study the information below to make sure your bug is fixed.
Good bug reports can take some time to research and write up, so to minimize the amount of time you spend posting bugs that have already been found, please check the Hot Issues page regularly. Here we will try to keep a current list of known bugs so you do not waste time researching them again.
Bug reports contain most if not all of the following items.
- Short title for the report.
- Steps required to reproduce the bug as described in title and description.
- The results from following the steps listed above.
- The expected outcome.
- An accurate selection of the category the bug is in.
- Connection information and computer configuration.
- Additional comments that may help to understand what is happening.
A short one sentence description of the bug helps us to know at a glance what the bug is.
Examples:
- My computer crashes while navigating the Backgammon help pages.
- ActiveX controls do not load on game pages.
- Could not setup to an external hard drive.
The steps necessary to reproduce the bug are very important. They allow us to quickly see the bug and more importantly, see the sequence of events leading up to the bug. Many times the fix for the bug will come from one of these lead up events.
When trying to reproduce a bug, try to find the simplest, shortest, and most general conditions that will cause the bug to happen. If possible, try to find alternative methods as well, or note methods that do not cause the bug, but seem similar enough that they should.
Example:
- Log into the Zone and click "Upgrade software."
- Change the path to a Zip drive (H:)
- Click the "Complete Install" option.
The result of all the steps listed to reproduce the bug should be listed as well. Many times this will be a restatement of the title, but add some finality to the repro steps.
Example:
- Log into the Zone and click "Upgrade software."
- Change the path to a Zip drive (H:)
- Click the "Complete Install" option.
- Result: Error message stating that the drive is invalid, but this is my Zip drive.
The expected result is the result that you would like to see.
Example:
- Expected: To be able to install to my Zip drive.
The bug reporting page has a section at the top that asks you to select a statement that best describes the report. This field is very important is directing the bug to the correct people.
Please follow the guidelines below to ensure your bug is sent to the correct group.
Categories:
- Bug: Crashed my computer / browser. (This is a very special category for very serious crashing bugs. If your bug did not crash your browser or computer, then do not select this category. Steps to reproduce this type of bug are vital.)
- Bug: Feature/Game does not work. (This is used to mark a bug as serious. Use this category if you are prevented from playing games or cannot use a feature.)
- Bug: Feature/Game works, but not quite as I expected. (This is the most common area for bugs. If you say to yourself, "That can't be right," then enter a bug under this category.)
- Bug: Web page typos and broken links. (Sometimes links break and sometimes we can't type. It happens. Tell us where they are and we will fix them.)
- Suggestion: Make the Zone better. (Suggestions for our current Zone games? Got game ideas? Post 'em and we will see what we can do.)
- Comment: Message to the Zone. (Kudos, comments or complaints? Also, let us know if you like this bug/suggestion reporting site.)
This type of information is nice for us to have so that we can take into consideration your machines configuration.
Examples:
- Pentium 90, 16MB RAM, Win95, 2MB video card (brand name)
- 486 66, 8MB RAM, Win95, 1MB video card
- Pentium II 266, 64MB RAM, NT4.0, 4MB video card
This area gives you a place to state your concerns about the bug and provide more details that you feel did not fit into the categories above.
Examples:
- The software would not install to my Zip drive, but it would install to a network drive.
- This bug may have something to do with the fact that I had just installed a new hard drive.
- Even though I cannot reproduce this bug anymore, I have talked with many people who have had the same problems. I told them to enter their bugs with my member ID in the title so that you can get more information from them as well.