The scope, type and risk of code bug fixes varies wildly, from one-liner fixes through to complete code system restructures. With thousands of bugs being fixed in a game project, it's critical that each and every tester is able to assess the scope and risk of bug fixes and take the appropriate action.

In this article I’ll share some stories of when myself or other testers have spent a lot of time chasing ghosts, often with no productive outcome at all.

No legitimate bug. It was pure wasted time. Through being aware of these examples you can be better equipped to identify when this is happening in your own teams and take action sooner to prevent frustration and wasted time.