This is a read-only archive of the old Scratch 1.x Forums.
Try searching the current Scratch discussion forums.

#1 2012-03-28 11:07:48

roijac
Scratcher
Registered: 2010-01-19
Posts: 1000+

How to Write Bug Reports so People Can Help You

Well, in the last time there are a lot of people posting things like "Scratch is broken! What can I do!?" or "The website is broken please help me!". This messages do NOT help at any point.
If you want people to be able to help you, it would be helpful if you helped them!
A bug report should at least contain information about what the bug was, otherwise it's not really a bug report.
So this is how to write bug reports:

First part: describe what you were doing, and what exactly happened. It would be really helpful if you would also try to repeat the same thing and see if it happens again.
If it's a bug in the browser, please try to reproduce the bug in another browser and see if it happens again.

Second part: describe things about your computer related to the bug. It wouldn't help much if you wrote that your browser is Firefox if you write about a Scratch 1.4 bug, but it would be helpful if you can't log in. If you think it's maybe memory leak, report how much RAM you have. ALWAYS write your operating system (linux/OSX etc.) and your computer's architecture (32/64 bit).

Third part (optional, but REALLY recommended): Screenshot. Then upload it to imgur or any other image hosting website, and link to it.

Done. Now wait for the answer which is now something else than "Could you please tell us more about the problem?".

Last edited by roijac (2012-03-29 12:01:04)

Offline

 

#2 2012-03-28 19:48:24

trinary
Scratcher
Registered: 2012-01-29
Posts: 1000+

Re: How to Write Bug Reports so People Can Help You

Very informative guide.


http://trinary.tk/images/signature_.php

Offline

 

#3 2012-03-28 19:56:53

CheeseMunchy
Scratcher
Registered: 2008-10-13
Posts: 1000+

Re: How to Write Bug Reports so People Can Help You

It's common logic for most people though.


6418,

Offline

 

#4 2012-03-29 09:33:34

Mokat
Scratcher
Registered: 2011-12-08
Posts: 1000+

Re: How to Write Bug Reports so People Can Help You

It's a great guide, but a bit hard to read since you put it all in code  hmm


http://www.eggcave.com/egg/977371.pnghttp://www.eggcave.com/egg/977376.pnghttp://www.eggcave.com/egg/1005291.pnghttp://www.eggcave.com/egg/996745.png

Offline

 

#5 2012-03-29 12:01:32

roijac
Scratcher
Registered: 2010-01-19
Posts: 1000+

Re: How to Write Bug Reports so People Can Help You

Mokat wrote:

It's a great guide, but a bit hard to read since you put it all in code  hmm

oh, yeah  smile
fixed now  roll

Offline

 

#6 2012-03-29 19:43:29

bobbybee
Scratcher
Registered: 2009-10-18
Posts: 1000+

Re: How to Write Bug Reports so People Can Help You

From a user's point of view, I'd skip it. Make it nicely formatted, and make it catch the users eye. (advanced BBCode seems to come to mind)


I support the Free Software Foundation. Protect our digital rights!

Offline

 

#7 2012-04-01 13:52:19

scimonster
Community Moderator
Registered: 2010-06-13
Posts: 1000+

Re: How to Write Bug Reports so People Can Help You

CheeseMunchy wrote:

It's common logic for most people though.

Some people don't use common logic when posting. Like, haven't you seen these topics? When someone's computer acts up, and they were Scratching, they blame it on Scratch. And then there are the legitimate bugs that aren't reported properly.

Offline

 

#8 2012-04-17 17:05:58

chanmanpartyman
Scratcher
Registered: 2011-05-30
Posts: 500+

Re: How to Write Bug Reports so People Can Help You

I don't know why you redirected me. I followed all of these except for like one. The third one.

Last edited by chanmanpartyman (2012-04-17 17:06:21)

Offline

 

#9 2012-04-18 20:31:50

FunDude
Scratcher
Registered: 2010-06-29
Posts: 500+

Re: How to Write Bug Reports so People Can Help You

bump


LOL signature fail

Offline

 

#10 2012-04-19 00:20:39

roijac
Scratcher
Registered: 2010-01-19
Posts: 1000+

Re: How to Write Bug Reports so People Can Help You

chanmanpartyman wrote:

I don't know why you redirected me. I followed all of these except for like one. The third one.

me wrote:

ALWAYS write your operating system (linux/OSX etc.) and your computer's architecture (32/64 bit).

Offline

 

Board footer