Skip to main content

Incident Tracking, Incident Report and Incident Management

Incident is an execution of code that happen during the testing. Incident can be anything , it can be a Fault, Failure, Bug, error, mistake, defect or an Incident. So any incident found during the review process need to reported this is called Incident Reporting.

Incident classified as the misconfiguration, corrupted data and server crash, hardware crash, Service not available.

To reporting of Incident is very beneficial because in any large project there may be 1000's of the incident and you can not process them without reporting. It is very difficult to keep track over those incidents without reporting.

Incident report contains the actual and expected result and others information that need to know why incident occur. Incident report contains the misbehavior of the software that cause the defect.

Incident Management is the process to add the incident, Process/Track that incident and Resolved that incident to meet the software as per the business requirement and client expectation. Incident Management is the full cycle to keep focus on each defects. 

Comments

Popular posts from this blog

Why Jmeter is best option for Performance Testing?

There are multiple tools in market for performance testing of any software but Jmeter is the best solution among all of them due to some reason listed below 1) Jmeter is the open source application so users who use this application will not to pay anything. 2) You can use Jmeter for performance of any web application,  Databases and Web Services (REST and SOAP APIs). 3) Jmeter have the user friendly UI component so it is very easy to use. 4) Jmeter can be used to simulate to put maximum number of concurrent users on a server, network or object to test its strength or to analyze overall performance under different load types. 5) Jmeter also use for functional testing for static( JavaScript and HTML) and dynamic( JSP, Servlets and AJAX) resources. 6) Jmeter provides Verity of graphical representations for performance report so it is easy to understand.

How You Can Test Database?

Now we know the Database Testing which you can learn in my last article. In this article we will discuss about the steps that need to following to test any Database. Database Tester should have some basic knowledge regarding SQL Command like DDL (create/drop),  DML (Insert/Delete/Update) and DCL (Grant/Revoke).

Causes of Software Defects

It is practically impossible that developer develop a bug free software and that software we can deliver without Testing. If the complexity of the software increased then there must be bugs that can harm the users who will use that software.