Hi

Basically what r u saying is traditional approach of working which has alreday been done by our team. Actually our team is scattered two and three geographical place in globe. so its not always possible to have discussion with them about each bug. We are using Excel shared sheet to log bug before final bug raising. & we are working to automate it & same time we are also looking for some automated tool for it. By the way thnx.

Yes

doing re-testing before relasing product.

You want the ability to identify defects raised by multiple testers and to do so efficiently.

Assuming all testers are logging their findings in a common defect tracking database the standard process is:

1. Anticipate defects that could likely be reported by multiple testers

2. Conduct a query in your defect management and reporting tool based on most likely keywords.

3. Consider this method isn't foolproof because the language testers use to report defects invariably differ and some similar defects will be missed by your query. Therefore you may need to be creative to discover all of the same defects.