You are on page 1of 7

Software Planner Defect Management Procedures February 10, 2011

Defect Priority, Status and Severity


Priority

Status Priority 1

Description Fixed ASAP System use will be severely affected until the defect is fixed. Fixed Soon- A workaround exists Fix if Time - can be repaired after more serious defects have been fixed.

Priority 2 Priority 3

Liberate Statuses
Status Assigned to Liberate Rollout Description Defect assigned to the Liberate developer for resolution once confirmed that issue cannot be reproduced on the green screen Defect fixed pending review by the Liberate internal QA group Similar defect is already assigned to the Liberate Rollout team Set By LIME Test Analyst Action Liberate Developer to investigate and provide update

Pending Liberate QA

Liberate Developer

Liberate development team to confirm fix

Duplicate

Liberate Developer/ LIME Test Analyst

LIME Test Analyst to monitor when fixes become available for the defect and retest. This defect will then move from an inactive to an active state. Additional

details are on page 4. By Design The defect is rejected because the feature is working as designed Liberate Developer LIME Test Analyst to review the defect and close if the functionality works the same way on the green screen, else change the status to Re-open and provide evidence

ECR

The defect is rejected because the fix will be handled as an emergency change request The defect is rejected because the feature is not a part of the current release

Liberate Developer

Out of Scope

Liberate Developer

LIME Test Analyst to use the Liberate Scope Navigation Skillset sheet in the shared drive to verify if the feature is a part of the current release. If the feature is on the navigation skillset sheet as a part of the current or previous releases then Test Analyst is to change the defect status to Re-open and add notes supporting the change. If the feature is confirmed as out of scope the defect should remain in out of scope status.

Resolved Pending QA

A fix is available for the defect

Liberate Developer

LIME Test Analyst to test defect fix. Close if the results meet expectation else Re-open and demonstrate in webex session Patni to review the details and provide a new solution

Re-Open

The defect fix provided is unsuccessful The defect is

LIME Test Analyst

Closed

LIME Test

Update the new details in the actual results field on the defect

confirmed resolved

Analyst

and the corresponding test case The test case status will automatically change to passed once the defect is updated as closed

Not Repro

The Liberate Developers are unable to reproduce the defect

Liberate Developer

LIME Test Analyst to verify that all the defect details are updated on software planner. If the LIME Test Analyst confirms that the defect is still valid after reviewing the reason provided by the developer, the defects are to be demonstrated via webex to the developers. Team leads to provide a list of the defects that need to be demonstrated for the weekly webex sessions

Defects related to all other Applications Examples Customer Portal, CIS Green Screen, Tally soft and CIS+GUI

Status Assigned to Developer

Description Defect assigned to developer for resolution

Set By LIME Test Analyst

Action Developer to investigate and provide update

LIME Test Analyst to raise ticket on ITSM, attach defect report from Software Planner on ITSM. The report must include the id, title, country, platform (integrity/alpha), steps, actual results, expected results and priority. Ticket numbers are to be updated in the ITSM ticket # field on the Software Planner defect. NB If several defects are found on a BU machine on the same platform raise one ticket on ITSM and attach the software planner report with all the defects. Duplicate Defect is rejected because a similar LIME Test Analyst

defect already exist By Design The defect is rejected because it is working as designed Liberate Developer Tester to review the defect and close if explanation provided proves correct. Else change the status to Re-open and provide evidence Seek clarification from the BU Lead if required Resolved Pending QA A fix is available for the defect Liberate Developer Tester to evaluate defect fix. Close if the results meet expectation or else Reopen and provide details NB Notification of defect fixes for green screen issues will be sent to testers from London developers via email or update in ITSM Re-Open The defect fix provided is unsuccessful LIME Test Analyst Developer to review the details and provide a new solution

NB Notification of unsuccessful fixes for green screen errors must be reported to the Service Desk Analyst who owns the incident Closed The defect is LIME Test Analyst Update the new details in the actual results

resolved

field on the corresponding test case The test case status will automatically change to passed once the defect is updated as closed

Severity
Severity Crash Description Failure of the complete system or a specific functionality The system produces incorrect, incomplete, or inconsistent results This can be repaired after more serious defects have been fixed. Defect has low business impact This is related to the aesthetics of the system, or is a request for an enhancement

Major Bug

Workaround

Trivial