A Defect life cycle, also known as a Bug life cycle, is a cycle of a defect from which it goes through covering the different states in its entire life.
This starts as soon as any new defect is found by a tester and comes to an end when a tester closes that defect assuring that it won't get reproduced again
This starts as soon as any new defect is found by a tester and comes to an end when a tester closes that defect assuring that it won't get reproduced again
Introduction of Bug:
Bug can reports by using different reporting tools such as excel sheet, HP-QC Bugzilla, JIRA, Visual task board
Bug Reporting / Bug Life cycle
Severity - represents affect of bug. Its a impact of bug in application. eg. login fail. application has High severity
Priority - How fast your bug is defect time. Important of bug. eg. login fail- High priority
Example:.
1. logo is not display. Severity-low, priority-high. ( doesn't effect any functionality)
- login fail application. Severity -High Priority -High
- In application login, developer design logout instead of login button. but when user click on logout, its login the application. Severity- low , Priority - High ( UI errors, functionality is working)
Bug reporting:
use different tools: Excel, Bugzilla, Jira, HP -QC
Bug Life cycle:
New bug --> report to LEAD --> Analysis --> forward --> Development department --> Analysis --Accept/ Reject / Deferred --> Accept --> Assigned to Developer --> Fix --> Retesting and Regression --> Close --if there is still bug--> Reopen
Defect life cycle:
Defect reporting Tool BUGZILLA
File a bug in Bugzilla
Description:
- Steps to reproduce:
- step 1:
- step 2:
- Expected :
- Actually:
- and add a screenshot.
No comments:
Post a Comment