And by steps, I don’t imply “Open the purpose of sale, promote one thing, pay with a bank card, and see the error.” That’s not adequate. You should give each single motion taken, all the way down to the mouse clicks and keystrokes. The extra element within the steps, the higher. In case you are a QA particular person and the developer says, “There are too many detailed steps!”, pat your self on the again and inform him to suck it up. You’ve performed your job properly.
Precise vs. anticipated habits
Each bug happens as a result of one factor is meant to occur however one thing else occurs as a substitute. Typically it’s the flawed output. Typically it’s a crash. No matter it’s, a very good bug report will outline what ought to occur when the steps are adopted after which very clearly element what truly occurs as a substitute. You possibly can’t repair incorrect habits in the event you don’t know what the proper habits is. Each bug report ought to make that very clear.
Context and system particulars
No bug lives in a vacuum. Present related context or system data that could be useful. Embrace data on how the bug is impacting the shopper, working programs used, browser varieties, a question to run on the info to see the problem, and so on. Embrace something that may assist clarify the issue and its influence.
