Defect Life Cycle

-
The bug life cycle is the cycle that a defect covers in its lifetime. This cycle starts when a tester finds a new bug and ends when a bug closed. The bug life cycle is also known as defect life cycle.  

 There are some steps which a bug covers during the bug life cycle are: 

New: ​ 
When a tester finds a new bug it come under the new state.
  
Open:​ 
In this stage, the developer Analyzes the bug and if he finds that the bug is valid then start working on it. 
● Duplicate:​ If the developer finds the same bug assigned earlier he change the status of that bug to duplicate. 
● Deferred:​ If the developer feels that this functionality in which bug is found is under construction or it will come in the next phase then he changes the state of that bug in Deferred. 
● Not a Defect:​ If the developer feels that bug is invalid or the requirement is changed then he changes its state to not a bug.  

Assign to developer​: 
After finding a new bug the head tester assigns it to the developer. This process comes under assign to developer state.  

Fixed by Developer:​ 
When a developer fixes the bug it comes under fixed by Developer state.  

Retest: ​After fixing the bug by developer he assigns it to tester and tester retest the bug that it is fixed or not.  a.​ If bug is fixed tester go on verify stage b.​ If bug is not fixed tester reopen the bug.  

Verified:​ 
If bug if fixed and pass in retesting then it is verified by Tester.  

Reopen:​ 
If bug fails in retesting then tester reopens the bug and reassigns it to the developer. After reassign, the process restarts from the third step and runs till the bug is not closed.  

Closed:​ 
When a bug is fixed and the test passes in retesting then the tester closes the bug. 

Comments

Post a Comment

Popular posts from this blog

Implicit and Explicit requirements

-
Implicit and Explicit requirements Explicit Requirements​ :    ● The Things business analyst Wrote Down.  ● These are the requirements explicitly stated or mentioned by the customer.  ● Explicit requirements are most commonly found in documents communicated by stakeholders to the development team.   ● This is the simplest type and the easiest to test.  ● The development team might take the form of an elaborate design specification, a set of acceptance criteria.  ● Explicit requirements in the form of claims that is, communications to end-users about things the software can do.   Implicit Requirements​ :  ● The Things client Will Expect  ● These are the requirements that are not explicitly stated by the customer, but implied or derived from the requirement stated by the customer.  ● These are all the things that users are going to expect that were not captured explicitly.  ● Examples include performance...
Read more

Software Configuration Management (SCM)

-
Software configuration management (SC) is a software engineering discipline consisting of standard processes and techniques often used by organizations to manage the changes introduced to its software products. SC helps in identifying individual elements and configurations tracing changes and version selection control and baselining.   SC is also known as software control management. SC aims to control changes introduced to large complex software systems through reliable version selection and version control.   Software Configuration Management does​ ​   ● Introduction to Software Configuration management and Configuration management for software Testers.  ● Software configuration management (SC) is the discipline for systematically controlling the changes that tae place during Software evelopment.  ● Software development software consists of a collection of items (such as program documents etc..) that can easily be changed. uring software...
Read more

Identified for Configuration Management

-
The term configuration item (CI) refers to the fundamental structural unit of a configuration management system. Examples of CIs include individual requirements documents software models and plans. The configuration-management system oversees the life of the CIs through a combination of processes and tools by implementing and enabling the fundamental elements of identification change management status accounting and audits. This system aims to avoid the introduction of errors related to lack of testing as well as incompatibilities with other CIs.     Configuration Management Activities ​:     1. ​Configuration Item Identification ​:  ​In this phase, the item will be identified for making changes.  Example: ​Requirement document design document source code etc    2. ​Change Control ​: ​ Controlling the release and changes of the product throw out the software life cycle here CCB team will approve or disapprove changes prioritize the change...
Read more