This topic is locked
Bugs in programs can be annoying. While some of the more serious bugs that exist in our programs are usually brought to our attention immediately when they happen, some often slip through the radar and can stay in our code for a very long time. We are aware that a lot of our programs haven't been touched up in a long time and are concerned about maintaining the quality of these programs. We came to the conclusion that our quality assurance needs to be stepped up a notch.
In the past, we relied solely on users reporting these bugs to us in our bug tracker. Now whenever a bug appears in the Program Manager, the details of the error (which do not include any sensitive personal information -- don't worry
) are immediately sent to us. Based on how many users report the same error to our system, we can gauge the impact of each bug and prioritize them accordingly. We also log which users are reporting the bug so that we can follow up with them to get more details about how to reproduce the bug, or to get them to test our fix if we can't do so ourselves.Once we get around to addressing the 30 or so bugs we currently have recorded in our system, I'll make another news post of our progress. The bugs come from many areas*, including:
- Score Sender
- Cheat Autoplayer
- Bilge Dice Autoplayer
- SDB Pricer
- Kitchen Quest
- Cellblock Autoplayer
- Scarab 21 Autoplayer
- Neggsweeper Autoplayer
- Abrosia MSAB/Igloo/Attic AB
