Software Testing Bubble
Aim to provide the clear and understandable Software Testing Concepts and the real time industry practices, approaches to the software testing aspirants with the perspective of beginners, experienced and advanced professionals. - Manual Testing - Performance Testing - Automation Testing
Wednesday, 18 June 2014
Software Testing Bubble: Software Defect Life Cycle and its Process.
Software Testing Bubble blog will speaks about concepts of Software Testing. This blog is newly started and will keep posting new topics and get in touch with you all.
Tuesday, 10 June 2014
Defect:
A deviation from given requirements (non-conformance of
requirements).
As we have Software Development Life Cycle (SDLC), A defect
is also have its own life cycle starts from its identification to Closure.
Below is the diagram which depicts its entire life cycle.
Defect Life Cycle Diagram:
Defect Life Cycle and Process:
- New/Open: Testers will raise a defect with this status
- Assigned: BA will analyze the defects raised by testers and assign them to respective developers
- Deferred: Defect raised on this functionalities are deferred till further development and taken care later
- Pending: Defect status can be pending when there is no clarity or need further discussion on that
- Rejected: BA can reject the defect if it is invalid / Developers can reject if it is not a defect actually
- Duplicate: BA can mark the defect if it is dupe of another defect / Developers can mark if it is a duplicate
- Work as Designed: BA/Developers can mark it as WAD if it is working as per design or not reproducible
- Returned to QA: If defect is not reproducible after Re-Open then developers can re-assign back to QA for re-verification.
- Fixed: Once developer fix the defect will marked as fixed
- Returned to Dev: Defect status can be pending
- Closed: If the issue what is being addressed and fixed then tester will close it after verification.
Severity and its Definition:
Severity: Severity
describes/defines how seriously (impact) the defect/issue is affecting the system. In other
words the seriousness (impact) of the defect/issue.
- Severity 1-Fatal: System crashes, system inoperable.
- Severity 2-Critical: Key function is inoperable, no workaround.
- Severity 3-Severe: Key function is inoperable, workaround available.
- Severity 4-Significant: Minor function is inoperable, no workaround available.
- Severity 5-Minor: Non-functional impact, cosmetic, workaround available.
Subscribe to:
Posts (Atom)