Index Overview Risks Models Strategy Plans Designs
Cases Procedures Execution Bugs Change Reports Downloads

Incident (Bug) Reports
Incident Reports show:


What failed


Where the failure occurred


What is planned to correct the problem


When it will be fixed


Who is fixing it



The Test Lead Incident Reporting system allows you to track all errors identified during a test execution run and, if required, any errors which occur once the application has been moved into production. All details of the problem are input to the bug report, which is then assessed by development personnel. The creation date, assess by date, resolution by date, re-test date and completed dates are all recorded, and can be used during bug tracking. Incidents can be tracked by type, by due date, by originator, by function, by severity and several other factors, and all due or overdue items can be listed by selected date.

Incidents can be cross referenced to test cases and to other Incident Reports, and all incident data can be analyzed to identify and chart results based on many different factors including reason, elapsed time, fix time (and therefore cost), function, function group, version and other factors. These charts help you to measure test progress and results, product stability, release readiness and many other items.

...Next Topic - Change RequestsNext

Top
BackBack to Test Lead Index       
Test Lead Index | Test Lead Technical Overview | Risk Register | Application Models | Test Strategy | Test Plans | Test Design | Test Cases | Test Procedures | Test Execution | Bug Tracking | Change Requests | Reports and Charts | Downloads

Please send your comments and feedback to testlead@talc2000.com

© 2002, Tallecom Software. All Rights Reserved.