Incident management tool is also known as a defect-tracking tool, a defect-management tool, a bug-tracking tool or a bug-management tool. However, ‘incident management tool’ is perhaps a better name for it because not all of the things tracked are actually defects or bugs; incidents may also be perceived problems, anomalies that are not necessarily be defects. Also what is normally recorded is information about the failure (not the defect) that was generated at the time of testing and the information about the defect that caused that failure would come to light when someone (e.g. a developer) begins to look into the failure. [Read more…]
A good incident report is a technical document. We have few rules of thumb that can help you write a better incident report:
- First, use a careful, attentive approach to execute your tests. You never know when you are going to find a problem. If you are pounding on the keyboard while gossiping with office mates or thinking about a movie you just saw, you might miss few of the strange behaviors. [Read more…]
After logging the incidents that occur in the field or after deployment of the system we also need some way of reporting, tracking, and managing them. It is most common to find defects reported against the code or the system itself. However, there are cases where defects are reported against requirements and design specifications, user and operator guides and tests also. [Read more…]
- When we talk about incidents we mean to indicate the possibility that a questionable behavior is not necessarily a true defect. We log these incidents so that we can keep the record of what we observed and can follow up the incident and track what is done to correct it.
- While executing a test, you might observe that the actual results vary from expected results. When the actual result is different from the expected result then it is called as incidents, bugs, defects, problems or issues. [Read more…]