How often we are waiting for a fix for that defect we found at the last minute? Everybody is stressed and the blaming game started immediately. So, the spotlight is put on to testers quickly as they are the show stopper. Why don't they found that defect earlier? I am not going to discuss that blaming game here. Instead, let's have a look at the feasible ways to resolve a defect and meet the deadline.
When a defect is found, it is far too often that we jump to the conclusion that it needs to be fixed before the software to be released. However, is it true that there is only one option in resolving a defect?
Theoretically, there are unlimited ways to resolve a defect. However, they can be summarized into the following 4 options:
- Fix the defect in the current release;
- Fix the defect in a future release;
- Patch the defect in the current release and fix it in a future release;
- Accept the defect as a limitation of the system.
By accepting a defect as a limitation of the system, it means that the defect does not justify a fix. In other words, the defect does not worth to be fixed at all. However, workaround may be required for this option to keep the system going.
