Detecting and processing defects
The first step is actually detecting the problem. This can sound a bit silly, but it's a quite crucial stage.
While we will mainly use the term "bug" to describe any defect, remember that it may include details like bad performance or unexpected behavior that may not be properly categorized as a "bug." The proper tool to fix the problem could be different, but the detection is normally done in a similar way.
Detecting problems can be done in different ways, and some may be more evident than others. Normally, once the code is in production, defects will be detected by a user, either internally (best case) or externally (worst case), or through monitoring.
Keep in mind that monitoring will only be able to capture obvious, and typically serious, errors.
Based on how problems are detected, we can categorize them into different severities, for example:
- Catastrophic problems that...