> If a bug reporter thoroughly documents a problem (and its attempted workarounds and behaviors) diligently and clearly That is exactly the metric I am referri

> If a bug reporter thoroughly documents a problem (and its attempted workarounds and behaviors) diligently and clearly That is exactly the metric I am referring. Of course, some bugs take longer to solve than others, but I can only start when I am able to reproduce the bug. The less steps to reproduce them, the better. The more concise the bug report, the better. Once you can reproduce it, I consider it essentially fixed, its only up to the developer to wrap their head around it and actually implement the fix it. And on, I am not "damn thankful" for the effort alone; I had to fire testers for showing much effort but not being helpful at all, even after long periods of training. The last time I was awarded for effort alone was in pre-school. When you buy a car that breaks down every 100 miles you probably would return it and not watch the manufacturer try to fix it 20 times, lauding their "effort"? Good testers are worth their weight in gold, they are very rare, they save us developers insane amounts of time and thus the company we work for a lot of money.