I have a lot of Quality Assurance questions and I'm still a newbie. Our QA department categorize bugs into several categories.
1. Bugs that are reported by customers
2. Bugs that we find upon testing new functionality (through internal software builds)
3. Bugs that we find ongoing basis (if we have time to test random areas)
My coworker and I started our jobs on the same day. I noticed that my coworker took the initiative to find bugs in 1. 2. and 3 during the first couple of months. However, my coworker doesn't do 3. anymore. I asked her "what you are doing these days?".Basically, she rarely does 3. anymore because the person who report the bug will have to verify it at the end (MORE WORK TO DO).
I still do 1. 2. and 3. And I do noticed that I am super while my coworker is free doing nothing. Is this how it works in QA? The person who finds the bug will have to work on it at the end?
In my shop, everyone is busy. People aren't sitting around doing nothing. If one person has less to do than another, they might be told to help their more-busy co-worker, or they might told to work on something else.
In my shop, if I found out that a person intentionally wasn't bothering to perform some testing because they thought it might mean more work, they would be reprimanded, then fired if that behavior continued.
In my shop when we report a bug/defect
we write its description and steps to reproduce.
ITs expected result and actual result with screen captures.
Also test data used during testing.
Usually the one who finds the bug and has reported it gets it for reteseting after developer has made the fix.
but this is no rule.Its just that it is quicker as that tester is aware of the scenario and does not have to start from scratch to understand test case and defect.
defect can be retested by any test engineer wihthin the team if all the above mentioned defect details are entered properly.
in your case if your team member is idle and you are over burden with work then you need to raise this point to your team lead/manager.
I agree with the fact that defect should be distributed. But having said that it is a preference that the person who logged the defect should ideally test it also. Because many times we have seen the other person wrongly closed the defect. But again I am sure there are some bugs which are very straight forward and anybody can test. So you can assign those defects to your coworker. And Btw I assume you also do some regression test around the function where you had that bug. So she should atleast do the regression testing.