When i find a bug, i don't resolve it, i notice it into the Bug-database. The development fix it and i retest it.
I don't realy understand what you need?
Want you tell in the interview: I know someone, who realy find a bug [img]images/icons/wink.gif[/img]
The normal way is: you find a bug, report it and the development fix it. Sometimes you help the development to reproduce the Error. When the fix is complete you will retest the bug to close the trouble ticket.
Iam a tester and found this bug in our company's product. BlackBox functionality worked fine and it failed in WhiteBox functionality. let me give you example.. a text file with html tags is fed as input for our application interface and again html page is to be displayed by clicking "show" button in same interface.The HTML page is displayed accordingly after the processing the html tags using code which is written in perl.
like the text in should be displayed as bold in html page after clicking the show button.
Hope Iam not wrong in expressing my interesting bug I found..
A good example of a bug?!? You can find so many examples.
I will give you also an example:
An Appointment can be in the Morning or in the Afternoon. Morning = AM and Afternoon = PM. That's logica.
But in the Detail HTML view is Morning = PM and Afternoon = AM.
This is a BUG.
What have I done: Well first I'll try it again with another Appointment. Same Problem. I added the defect in ClearQuest with a scenario. The developers will fix the bug. They use the scenario to reconstruct the problem.
A tester will never resolve a bug only find them and reporting them. Of course you can help the developer with reconstructing the bug.