Becoming a Super Bug Reporter
I take exception with the entire premise of this thread. No self-respecting super-villain is going to file a bug report, it's easier to cause mayhem when things aren't working right. Hell, super-villains are the main cause of most bugs. Sometimes giant ones with radioactive eyebeams!
"You don't lose levels. You don't have equipment to wear out, repair, or lose, or that anyone can steal from you. About the only thing lighter than debt they could do is have an NPC walk by, point and laugh before you can go to the hospital or base." -Memphis_Bill
We will honor the past, and fight to the last, it will be a good way to die...
Is there a badge in it for me?
"Mastermind Pets operate...differently, and aren't as easily fixed. Especially the Bruiser. I want to take him out behind the woodshed and pull an "old yeller" on him at times." - Castle
hey guys i found a bug purple ios still work on preimium lol well not really but set bonuses anyway im typing on my phone so dont h8 on the spelling lol!!! later doods
I bet if we institute a ban on talking about animated hair that would work.
Liberty Server (@enderbean)
Arcs on Live
#1460 Hometown Rivalry
I don't see him trying to get rid of any real heroes.
Where to now?
Check out all my guides and fiction pieces on my blog.
The MFing Warshade | The Last Rule of Tanking | The Got Dam Mastermind
Everything Dark Armor | The Softcap
don'T attempt to read tHis mEssaGe, And believe Me, it is not a codE.
What supervillain does his taxes?
Quote:
Soooooo...I'm guessing you work in QA?
We're all super villains, right (Golden Girl, go away)? We know what it means to be super. Everything we do is super: be it kicking puppies (SUPER kicking), eating breakfast cereal, and filing our taxes. If you're not going to be super about it, then why bother? Where's the flair? The finesse?
Today, I'm going to talk to you about not only how to submit a software bug report, but to submit a super bug report! Let's go over the basics. * Identifying a Bug - A bug may be somewhat loosely defined, but everyone seems to agree on it meaning one thing: the software doesn't work as advertised. Don't worry about definitions, though, because they're not important. When submitting a bug report, you can submit it about anything you want, including any of the following... A feature exists but you don't know where it is. A data error is present that may as well be a program error. A feature exists but you don't know how to use it. You are using an entirely different application. And this one's my favorite: You are unable to do something that the software doesn't even claim to do. * Ticket Title - When looking over the list of fatal errors and life-changing problems caused by their software, the developers don't really like to waste their time trying to pick through long, complicated ticket captions. When submitting a report, make sure you call it something short and easy to read, such as "bug problem" or "doesnt work." Be sure to use all-lowercase and exclude punctuation, since consistency is much easier on the eyes. * Bug Description - In order for the developers to be able to fix the problem you are reporting, you should give some minimalist information about it. Don't be verbose or otherwise understandible--again, it's about looking through reports quickly and developers are all psychics anyway (C++ is short for "psychic"). Identify the most general aspect of the program in which you've encountered a problem, and say that the feature in its entirety is completely non-functional. * User Information - Sometimes it's a matter of the user's computer that can cause problems. However, self-contained applications are becoming less and less about how you have your system configured and more about what operating system you are running, so be sure to mention that. For added convenience, if you're using the same operating system as the software authors, be sure to use the phrase "if that makes a difference." For example: "I'm running Windows 7 64-bit, if that makes a difference." * Your Problem is Important - Last but not least, forget about everyone else. The bug you've encountered applies to you, first and foremost. Don't bother looking two or three threads down for a solution, workaround or simple acknowledgment of the same problem; just start a new report thread. After all, the simpler a problem is, and the more people who have it, the more the developers like to hear about it (they get to make the most people happy fastest with the least amount of effort). And there you have it. Follow these simple guidelines and you too can be a super bug reporter! |
What are these "software bugs" you're talking about?
--NT
They all laughed at me when I said I wanted to be a comedian.
But I showed them, and nobody's laughing at me now!
If I became a red name, I would be all "and what would you mere mortals like to entertain me with today, mu hu ha ha ha!" ~Arcanaville
Quote:
I thought you were only testing the new Titan Sentinel with an extremely limited amount of people...
We're all super villains, right (Golden Girl, go away)? We know what it means to be super. Everything we do is super: be it kicking puppies (SUPER kicking), eating breakfast cereal, and filing our taxes. If you're not going to be super about it, then why bother? Where's the flair? The finesse?
Today, I'm going to talk to you about not only how to submit a software bug report, but to submit a super bug report! Let's go over the basics. |
![Smile](images/smilies/smile.gif)
![](http://i55.photobucket.com/albums/g151/vg-mmorpg/ForumAvatars/snowglobesig.png)
![](http://i55.photobucket.com/albums/g151/vg-mmorpg/ForumAvatars/SnowGlobe_sigprotest_zps7dee0180.png)
Triumph: White Succubus: 50 Ill/Emp/PF Snow Globe: 50 Ice/FF/Ice Strobe: 50 PB Shi Otomi: 50 Ninja/Ninjistu/GW Stalker My other characters
We're all super villains, right (Golden Girl, go away)? We know what it means to be super. Everything we do is super: be it kicking puppies (SUPER kicking), eating breakfast cereal, and filing our taxes. If you're not going to be super about it, then why bother? Where's the flair? The finesse?
Today, I'm going to talk to you about not only how to submit a software bug report, but to submit a super bug report! Let's go over the basics.
* Identifying a Bug - A bug may be somewhat loosely defined, but everyone seems to agree on it meaning one thing: the software doesn't work as advertised. Don't worry about definitions, though, because they're not important. When submitting a bug report, you can submit it about anything you want, including any of the following... A feature exists but you don't know where it is. A data error is present that may as well be a program error. A feature exists but you don't know how to use it. You are using an entirely different application. And this one's my favorite: You are unable to do something that the software doesn't even claim to do.
* Ticket Title - When looking over the list of fatal errors and life-changing problems caused by their software, the developers don't really like to waste their time trying to pick through long, complicated ticket captions. When submitting a report, make sure you call it something short and easy to read, such as "bug problem" or "doesnt work." Be sure to use all-lowercase and exclude punctuation, since consistency is much easier on the eyes.
* Bug Description - In order for the developers to be able to fix the problem you are reporting, you should give some minimalist information about it. Don't be verbose or otherwise understandible--again, it's about looking through reports quickly and developers are all psychics anyway (C++ is short for "psychic"). Identify the most general aspect of the program in which you've encountered a problem, and say that the feature in its entirety is completely non-functional.
* User Information - Sometimes it's a matter of the user's computer that can cause problems. However, self-contained applications are becoming less and less about how you have your system configured and more about what operating system you are running, so be sure to mention that. For added convenience, if you're using the same operating system as the software authors, be sure to use the phrase "if that makes a difference." For example: "I'm running Windows 7 64-bit, if that makes a difference."
* Your Problem is Important - Last but not least, forget about everyone else. The bug you've encountered applies to you, first and foremost. Don't bother looking two or three threads down for a solution, workaround or simple acknowledgment of the same problem; just start a new report thread. After all, the simpler a problem is, and the more people who have it, the more the developers like to hear about it (they get to make the most people happy fastest with the least amount of effort).
And there you have it. Follow these simple guidelines and you too can be a super bug reporter!