How to write Awesome Bug Reports to Pick Up Chicks and Impress Your Friends

cwright's picture

When filing bug reports at http://bugreporter.apple.com, a few little details can go a long way.

First, make your sample compositions as simple as possible -- ideally, a 3-patch composition is desired (because it takes almost no time to figure out what's going on). Getting gigantic, complex compositions is a sure-fire way to get delayed (behind all the small-composition bug reports).

Make sure you're not using any plugins. At all. If you think a plugin is causing a bug, take it up with the plugin author.

Include notes on what things you've tried, detailed steps on how to reproduce it (as simply as you know how), and any cases where it may not apply (i.e. if it worked in 10.5, but not in 10.6, that's good to know. If it worked in 10.5.7, but not in 10.5.8, that's good to know. If it works when iTunes is running, but doesn't work when Mail's running, that's good to know). If it happened once, randomly, and never again, it's not too helpful unfortunately :/

It might be a good idea to team up with someone who's experienced in testing/bug reporting, and bounce some cases back and forth before submitting -- this can help refine the bug (and its associated notes) even more. (No, I cannot be your bug buddy, so please don't ask.) Asking here can be a good start (unless it's a sensitive issue, then it shouldn't be discussed in public).

If there are any other good tips (or disputed points above ;), stick 'em in a comment :)

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

bbinkovitz's picture
Re: How to write Awesome Bug Reports to Pick Up Chicks and ...

Do QC bug reports go directly to the QC team, or does someone who doesn't have any special knowledge of QC filter them (as some people have implied to me)? Do we have to make them look important to laypeople to get them passed on?

jpld's picture
Re: How to write Awesome Bug Reports to Pick Up Chicks and ...

i should think conveying the significance of the defect, lay or not, would be valuable.

cwright's picture
Re: How to write Awesome Bug Reports to Pick Up Chicks and ...

that is -- I was hoping that'd be implied :) Most important is keeping the steps to reproduce it concise, and the demo simple (getting hundred-patch compositions or following 57-step directions both get old really quickly)