The most important thing in bug testing is to
TRY TO REPEAT THE BUG. Try closing the application and restarting Little Reader, and see if the bugs you encounter are still there.
In some cases, the problem disappears after you restart the program or even your computer. But nevertheless, we'd still like to know about the issues, so we hope you can report them to us
AS CLEARLY AS YOU CAN.
If you'd like to report an error or a bug, please use the format below:Error description:Please give us a step-by-step instruction on how you got the error and how we can reproduce it. If you can't give us a step-by-step instruction, a short summary of the error may suffice.
In case you get an error message, please copy and paste the error code. You can find the code on the error message as shown below:
And if it's a bit hard to describe, you can also choose to just send us a
screenshot of the error message.
To learn how to take a screenshot, please click here.Your Error LogLittle Reader takes note of most of the errors your program is encountering. To enable us to fix bugs faster, we will need the data from the error.log of your Little Reader. We encourage you to post here in the forums as soon you encounter a bug, and to try to attach your error log as often as possible.
Here’s how to access the Error Log:1. From your computer Desktop, click on My Documents.
2. Click on the folder entitled BrillKids, then click on the folder entitled Little Reader.
3. Open the folder entitled DATA.
4. Your will now see two or three files, namely Little Reader.mdb, Little Reader, and error.log (for some people, you will only see the file named “error”.)
The ERROR.LOG is the file which you must attach to your error post in the forums.
Your computer specs: - Tell what OS you're using (Windows 98, 2000, XP, or Vista)
- Your computer processor (if you know it)
What internet browser are you using? - Internet Explorer, Firefox, Opera, Safari
Internet connection type: - Dial-Up, Broadband, DSL, T1, T3, LAN
Digg
