" Live as if you were to die tomorrow. Learn as if you were to live forever.. "
- Mahatma Gandhi
" Live as if you were to die tomorrow. Learn as if you were to live forever.. "
- Mahatma Gandhi
|
1. Keyword Driven Bug Submission: First of all before submitting any bug to Defect tracking tool analyze your bug thoroughly. Then try to submit the bug having some unique keywords. For example if you are getting the internal error message like “404 error on Page” then the keyword could be ‘404 error’. Before submitting the bug you can also search for similar kind of bugs in your own defect tracking tool. In search results you may find many bugs related to the specific keyword that you used in your search criteria. Then you can always go through the bug of your interest to review its profile in full. (Product version and build in which bug was reported, Environment, Full path to reproduce the bug etc).
2. Although it is very easy to search bug using specific keyword, still it is not so much effective as the you may not find the clone/duplicate issues due to the mistakes done by the tester. For instance bug summary of duplicate bug may have contain Keywords like ‘internal error’, ‘Crasher’,’Error on Page’ etc.
So it is advisable when you are searching for duplicate issues use the correlated keywords.
|
|
3. If you want to optimize your search to its best then you can search using some other filter criteria. Because it is seen that the tester reported a bug using good formatted structure but used the direct path of bug like Server Admin > Utilities > Server Tools – Page on Error’. In this case you can use the section name/Page name to find the duplicate issue.
|