This question already has an answer here:
- What to do with bugs that do not repro? 10 answers
There are instances which cane be seen while testing the application, both by developers and testers, some NullPointerExceptions arriving while clicking on a node in the table, or while doing an action too fast or under a zillion test-cases which do not come under the Test Cases document used in testing the application.
Most times we try to ignore these Ghosts ( i like Phantom bugs) which appear while testing. But the Quality assurance team won't be ready to accept a Phantom exception to occur while using the application. So what they do, they will file a bug along with the test case and the stack trace which occurred while the bug appeared.
When the developer tries to recreate the bug with all sorts of test cases and breakpoints everywhere the bug doesn't appear.
It feels like reading stories of UFO's spotted in some random area at some random time with a weird appearance.
How can a developer deal with these kind of issues before closing the bug or approaching the tester to recreate the bug which never can be recreated ?