Do you ever get sidetracked when you find a bug that’s outside the scope of the feature you’re currently testing? What do you do? Do you stop and raise a bug report there and then, or do you continue with your original testing and make a note of it for later?
I recently encountered such a bug while creating test data, and came to the conclusion it, while not a show-stopper, it was a little more than a minor annoyance and needed to be logged. It probably helped that I was able to isolate and repeat the bug while creating my test data, so didn’t end up chasing down rabbit holes in the process.
After logging the bug it turned out that another tester had noticed the problem much like I had, but hadn’t logged it at the time because of tight time constraints. I think that justified my logging it.
