Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How to write a bug report that actually gets resolved – and why everyone should

lucidchart.com

Post reply on HN
Print view View original

1–10 of 18 posts

Re: How to write a bug report that actually gets resolved – and why everyone should

#3

Post by zenincognito »

Reporting the bug is important but highlighting what are the implications of the bug is equally important.

With one simple string , I was able to find 45 bugs in different software and every time I reported the bugs I decided to tell them what were the implications of the bugs.

With no professional background in security, I was able to claim 18K in bug bounty rewards by being professional, clear and providing clear implications of the bug.

It is quite possible that people fixing the bugs may not be well versed in some components of the bug and are likely to not understand the implication of the bugs until you tell them so.

Re: How to write a bug report that actually gets resolved – and why everyone should

#4

Post by scoot »

zenincognito wrote: post #3

Reporting the bug is important but highlighting what are the implications of the bug is equally important. With one simple string , I was able to find 45 bugs in different software and every time I reported the bugs I decided to tell them what were the implications of the bugs. With no professional background in security, I was able to claim 18K in bug bounty rewards by being professional, clear and providing clear i…

Good old SQL injection?

Re: How to write a bug report that actually gets resolved – and why everyone should

#5

Post by zenincognito »

scoot wrote: post #4
zenincognito wrote: post #3

Reporting the bug is important but highlighting what are the implications of the bug is equally important. With one simple string , I was able to find 45 bugs in different software and every time I reported the bugs I decided to tell them what were the implications of the bugs. With no professional background in security, I was able to claim 18K in bug bounty rewards by being professional, clear and providing clear i…

Good old SQL injection?

Good old >'>">

Re: How to write a bug report that actually gets resolved – and why everyone should

#6

Post by arbesfeld »

Great post. I'm surprised that this topic doesn't get visited more given how much time we [developers] spend on bug fixing.

Shameless self-promotion: we are working on LogRocket [1] specifically so that you don't have to ask users for steps to reproduce.

[1] https://logrocket.com

Re: How to write a bug report that actually gets resolved – and why everyone should

#8

Post by delecti »

It's absolutely stunning how many testers I've worked with didn't understand the "Preconditions/Actions/Expected/Actual" as a bare minimum for a bug report.

> Avoid using ambiguous words like “broken” or “not working.”

Holy crap yes, this. So many infuriating waste of time bugs. And adding screenshots is good to call out. "X looks wrong", is useless, "X looks wrong " might still be useless, but at least you're trying.

Post reply on HN