Incident Management in Software Testing

An incident is any essential, unplanned event that happens at the time of software testing that requires posterior investigation and amendment.

Incidents are increased in the case when expected and actual test results are differ from each other.

Incidents may be raised against documentation as well as code or a system under test.

Incidents may be analyzed to observe software testing process and to assistance in its betterment.

Incidents should be logged when someone (not the author of the product) conducts software testing.

In general the information logged on an incident should comprise:

  • expected and actual results
  • software under test id
  • scope
  • test environment
  • names of software testers
  • severity
  • priority
  • any other relevant information to fixing the potential software bugs

Incidents should be tracked from inception through different phases to close out and resolution after all.