How to Write Bug Reports that Make Developers Happy
Bugs are everywhere. This statement holds true whether in the wild or on the world wide web. The latter is what this article focuses on, which refers to errors or unexpected results in a computer system.
In a previous blog, I wrote about What is QA Testing?. This article builds on top of that, with a focus on how to write bug reports for technical issues. Whether you are a user, tester, or developer, I hope that you will find this useful and applicable for your everyday life.
If You See Something, Say Something.
“More Code, More Bugs. “ — Software Engineering Proverb
I’m going to take a stance and say that there is no such thing as bug free software. It’s a widely held belief that the more code there is, the more bugs there are. And according to Murphy’s law — anything that can go wrong, will go wrong.
The key point here is that when you encounter a bug, do the community a favor and immediately report it. Can’t create a story on Medium? Report it. Can’t watch videos on Youtube? Report it. Uber can’t find your pickup location…
