Skip to main content

Testing ?? what the hell with Defect / Bug Life Cycle !!!!!!


“A mistake in coding is called error ,error found by tester is called defect,  defect accepted by development team then it is called bug ,build does not meet the requirements then it Is failure.”
Defect life cycle is a cycle which a defect goes through during its lifetime. It starts when defect is found and ends when a defect is closed, after ensuring it’s not reproduced. Defect life cycle is related to the bug found during testing.
The bug has different states in the Life Cycle. The Life cycle of the bug can be shown diagrammatically as follows:
Bug or defect life cycle includes following steps or status:
  1. New: When a defect is logged and posted for the first time. It’s state is given as new.
  2. Assigned: After the tester has posted the bug, the lead of the tester approves that the bug is genuine and he assigns the bug to corresponding developer and the developer team. It’s state given as assigned.
  3. Open:  At  this state the developer has started analyzing and working on the defect fix.
  4. Fixed:  When developer makes necessary code changes and verifies the changes then he/she can make bug status as ‘Fixed’ and the bug is passed to testing team.
  5. Pending retest:  After fixing the defect the developer has given that particular code for retesting to the tester. Here the testing is pending on the testers end. Hence its status is pending retest.
  6. Retest:  At this stage the tester do the retesting of the changed code which developer has given to him to check whether the defect got fixed or not.
  7. Verified:  The tester tests the bug again after it got fixed by the developer. If the bug is not present in the software, he approves that the bug is fixed and changes the status to “verified”.
  8. Reopen:  If the bug still exists even after the bug is fixed by the developer, the tester changes the status to “reopened”. The bug goes through the life cycle once again.
  9. Closed:  Once the bug is fixed, it is tested by the tester. If the tester feels that the bug no longer exists in the software, he changes the status of the bug to “closed”. This state means that the bug is fixed, tested and approved.
  10. Duplicate: If the bug is repeated twice or the two bugs mention the same concept of the bug, then one bug status is changed to “duplicate“.
  11. Rejected: If the developer feels that the bug is not genuine, he rejects the bug. Then the state of the bug is changed to “rejected”.
  12. Deferred: The bug, changed to deferred state means the bug is expected to be fixed in next releases. The reasons for changing the bug to this state have many factors. Some of them are priority of the bug may be low, lack of time for the release or the bug may not have major effect on the software. 
  13. Not a bug:  The state given as “Not a bug” if there is no change in the functionality of the application. For an example: If customer asks for some change in the look and field of the application like change of colour of some text then it is not a bug but just some change in the looks of the  application.

Comments

Post a Comment

Popular posts from this blog

Role OF BA in IT Project

Slides how BA communicates in project ensures to client: properly gathered,communicates the same with technical team in UML. Communicates with clients in Business Language. Nurtures the IT team with IT solution. Technical team heads with PM and Team Leader with in time frames. PM,take cares about the technical aspects of project. Teamleader cares about the delivery of project in defined time frames. BA continuously track of the client requirements through all different stages of PLC. Helping technical Team to understand requirements clearly and participates in UAT. Takes ownership from the client to ensure the project is completed according to the clients requirements.
Post a Comment
Read more

Creativity of ChatGPT in putting my wrong prompt into story

Today I am a little bit lazy due to the climate. In that laziness, I wrongly prompted the ChatGPT instead convert requirement into userstory and asked about my requirement for the story. My mistake turned into a beautiful story that I can explain to my team while grooming those stories in future sprints.  Prompt : convert the requirement into story Requirement:  "Show" options: Display number of records onscreen based on selection.  Options are 50 (default), 100, 150, and 250.  Pagination should adjust based on the number of records being displayed.  Disable options that are not relevant - example: if the table only has 40 records, disable the remaining options (100 150 and 250) Selection should be sticky by user within and across sessions.  Display the number of records the user has selected when they navigate away from the page and return (if they were showing 100 records when they left; show 100 records when they return) Pagination is always visible and ...
Post a Comment
Read more

Are Skill Development Missions Successful?

Skill development missions are very common in India and abroad to upscale the skills of rural and urban educated and unemployed youth. Most of the skill development missions have common agenda to create employment with proper training and providing certifications by industrial experts. It’s in positive perspective. Do you think, is it helpful to uproot and groom the skills to create employment with few interactive sessions with industrial experts? There are lot of gaps in those missions. All the missions and objectives are time bound and no one have the accountability in creation of jobs except training. After training we need to put into test in real time and need to gather continues feedback from the attendees. And capture the information with proper questionnaire instead of ‘yes’ or ‘no’ questionnaire which can’t provide proper feedback to understand the attendee’s opinions. Feedback System Feedback system must be very strong and follow ups with attendees must be frequ...
Post a Comment
Read more