It is ok to log an invalid bug

Almost all testers would agree with me on one thing. It hurts when our bugs are marked as invalid or not reproducible or even a duplicate bug. Given the unpredictable nature of software it is quite natural that system behaves differently at times. What we see as an issue at one point of time, may not be seen at a later stage of product development cycle. That however shouldn't prevent a QA from logging that issue. You never know when that would resurface!! Having said that, there is difference between "Not a bug" and an "Invalid bug". " Not a bug " obviously means that it is not a bug at all and a feature of the software, Invalid bugs can either be not reproducible issues or when a functionality changes, the bug cease to exist or it could be anything else. Even the development team acknowledges it as a bug. A vast majority of the invalid bugs could be due to some simple missed things..

Few things that would help any tester avoid the ambiguous bugs are

• Check for the latest version of all files before you begin your testing.
• Check for DB, Server down time , that could lead to lot of not reproducible bugs.
• Check if the credentials that you use are valid.
• Check for all configurations.
• Check for browser, hardware compatibility of the software that you use.
• Check if you have all the prerequisites needed for the application that you intend to test.

When there is an issue, the first thing that any experienced QA would do is take a screenshot of it and then try to reproduce the issue. More important than finding a bug is actually describing it. Video screenshots would help a lot, given that it makes it easy for even the developers to just run the video and find out the issue. If that is not feasible, QA must make sure to describe each and every step that they actually followed. The development team should be able to reproduce the bug based on the steps given in the description. A good bug report can make the life easy for a QA and the developer. Even after all this if the bug is marked as invalid, then take it easy. Try to reproduce it and show them with proper steps. It is not a sin to log an invalid bug, and one does not have to feel sorry for it. Logging an invalid bug is also part of testing:)