Scribd
Upload
432 views2 pages

Defect Report Template

The document provides a template for reporting software defects or problems. It includes required and optional fields to describe the defect such as the ID, author, release number, date opened and closed, problem area, type, priority, severity, status, and information about who detected the issue and how it was detected. Fields also track who the issue is assigned to, the planned fix, and build number. The template aims to standardize the information collected for each reported software issue.

Uploaded by

Yyy Ttt
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
432 views2 pages

Defect Report Template

The document provides a template for reporting software defects or problems. It includes required and optional fields to describe the defect such as the ID, author, release number, date opened and closed, problem area, type, priority, severity, status, and information about who detected the issue and how it was detected. Fields also track who the issue is assigned to, the planned fix, and build number. The template aims to standardize the information collected for each reported software issue.

Uploaded by

Yyy Ttt
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

Sample Template for Defect Report / Software Problem Report

Defect ID: System generated


(Required)
Author: System generated
(Required)
Release/Build # Build where issue was discovered
(Required)
Open Date: System generated
(Required)
Close Date: System generated when QA closes
(Required)
Problem Area: Describe the problem area
(Required)
Defect or  Defect (Default)
Enhancement:  Enhancement
(Required)
Problem Title: Short one-line description
(Required)
Problem A precise problem description with screen shots, if possible
Description:
(Required)
Current E.g. Win95 / Oracle 4.0 NT
Environment:
(Required)
Other E.g., WinNT / Oracle 4.0 NT
Environment(s):
Defect Type:  Functionality (Default)
(Required)  Architectural
 Connectivity
 Consistency
 Database Integrity
 Documentation
 GUI
 Installation
 Memory
 Performance
 Security and Controls
 Standards and Conventions
 Stress
 Usability

Who Detected:  Quality Assurance (Default)


(Required)  External Customer
 Internal Customer
 Development

How Detected:  Testing (Default)


(Required)  Review
 Walkthrough
 JAD
Assigned To: Individual assigned to investigate problem
(Required)
Priority:  High (Default)
(Required)  Critical
 Medium
 Low

Severity:  High (Default)


(Required)  Critical
 Medium
 Low

Status:  Open (Default)


(Required)  Being Reviewed by Development
 Returned by Development
 Ready for Testing in the Next Build
 Closed (QA)
 Returned by (QA)
 Deferred to the Next Release

Status (Required when)


Description: Status = “Returned by Development,”
“Ready for Testing in the Next Build”
Fixed by: (Required when)
Status = “Ready for Testing in the Next Build”

Planned Fix (Required when)


Build #: Status = “Ready for Testing in the Next Build”

http://www.softwaretestinggenius.com

You might also like