Image © Juja Schneider
Many projects have their closed or “won’t fix” bugs commented with remarks such as:
- “Content-related issue”,
- “Won’t happen on live system”, or
- “This is just a data issue”.
Both the development of new features and data maintenance may be accomplished in different environments. For testers, it’s thus difficult to decide on the cause for a certain issue: is a required text missing because pages aren’t implemented the right way or is it simply not there because the corresponding product data aren’t available in this particular test system? Very often testers work on development systems without having access to latest data. The following is a typical scenario:
- Testers report a bug.
- The development resolves this bug as content-related and won’t fix.
- Testers report further bugs of that sort.
- The development gets irritated: “We’ve told them that these are content issues!”
- The relationship between testers and developers might really go downhill from there, seriously threatening the project’s success: the credibility of the test team is damaged, developers don’t take reported bugs seriously anymore, testers get overly cautious and stop reporting content-related problems…
Inevitably, potential bugs don’t get reported and reported bugs never get retested before the project goes live. This is even more true in poorly managed projects because no one really feels responsible to solve this problem.