Bug Life Cycle Or Defect Life Cycle

Defect (Bug) Life Cycle

A Defect/Bug Life Cycle is made up of series of phases.

1. New
    When the bug is identified and logged in bug tracking tool for the first time, its state will be "NEW".
2. Open / Closed
    After a QA has posted a bug, the QA lead validates the bug. If bug is valid then he changes the state as "OPEN" and if the bug is invalid then the lead changes its state to "CLOSED".
3. Assign
    After QA lead changes the state as "OPEN", he assigns the bug to corresponding developer or developer team lead and the bug status is changed to "ASSIGN".
4. Rejected:
    If the developer feels that the bug is not valid or it has some technical limitations and cannot be fixed, he rejects the bug. He changes the state of bug to "REJECTED".
5. Duplicate:
    If the bug is logged is repeated twice or the two bugs reported has alike results and steps to reproduce, then one bug status is changed to "DUPLICATE".   
6. Deferred:
    If the development team lead decides to fix the bug in next release due to lack of time or the priority of the bug is low then he changes the state to "DEFERRED", which is later changes to "ASSIGN" when the bug is taken in consideration to be fixed.
7. InTest
    Once the developer fixes the bug, he assigns the bug to the testing team for next round of testing. Before that he changes the state of bug to "IN TEST". It specifies that the bug has been fixed and is released to testing team.
8. Verified
    Once the bug is fixed and the status is changed to "IN TEST", the tester tests the bug. If the bug is not reproducible in the software, he changes the status to "VERIFIED".
9. Reopened
    Once the bug is fixed and the status is changed to "IN TEST", the tester tests the bug. If the bug is reproducible in the software, he changes the status to "REOPENED".
10. Closed
    After the bug status is changes to "REJECTED" or "DUPLICATE" or "VERIFIED" the QA Lead verifies the comments added by the development or Testing team. When he is satisfied with the comments he changes the state to "CLOSED".

Note: There are different process and methodologies followed in various organizations. The above content is as per my experience in industry so far.

Please feel free to write comments if you like my post or else if your opinion is different or you may like to add any more points in them.

Testing /QA Interview Questions And Answers

1) Software testing:  Software testing is a methodology to find bugs in the software

2) Software Development Life Cycle( SDLC):

3) Software Testing life Cycle (STLC):  Click Her For Detail

4) Positive test case: - Test to check whether the system do what it is suppose to do.ie, checking for valid values only.

5) Negative Test Case: - Test to check whether the system will do what it is not supposed to do.ie, checking for invalid values.

6) Verification: It is a set of activity which confirms that the software is created accordance to the specification

7) Validation: Is a set of activity which confirms software is created is linked to user requirement or not

8) Retesting: Failed test case are executed to ensure that defect is really fixed

9) Regression: all passed test cases are executed on related module to verify that there is no injection of new defect to change in one of the module

10) Static: Reviewing artifacts rather than executing code

11) Dynamic: Testing Perform by executing code by giving i/p and verify o/p

12) Smoke: Is a simple test condition to ensure that the software is working properly at gross level so that further testing is done

13) Sanity: It perform to verify whether the application function according to specification or not

14) Defect: Defect indicate difference between expected and actual behavior

15) Defect Life cycle Or Bug Life Cycle: Click Here For More Details

16) White Box: It is done by developer. This require knowledge of internal structure and code of that application

17) Type of white box: 1) Statement 2) Decision3) Condition 4) path 5) loop

18) Black box: This is done by tester it mainly focus on functional requirement. By providing set of I/P and observe output.

19) Black box type: 1) BVA 2)    Equivalence class partitioning               3) state transition

 20) Alpha: It is done at developer side under controlled environment. Here developer is present

21) Beta: It is conducted at one or more customer site in live environment by end user .here developer is not present

22) Agile testing: It is testing methodology goes hand in hand to an agile software development model. Here release are quicker (within 2-3 week) and incremental are iterative in nature

23) Development Model:

1) Waterfall: It is sequential model which process through Requirement-> Design->Coding->Testing

2) Spiral: Divided into 4 phase 1) Plan2) Design3) Prototype4) test .In this model software in series of incremental realized. As we process through iteration more complete versioned is engineered product are visible. It is useful when user/developer are not cleared about the solution to developed and needs evaluator approach 

3) Agile: Here release as frequently as every week rather than month and continuous changes in requirement and welcome to be integrated

24) V-Model:
         It is extension of water fall model .here both the aspect  quality control and quality assurance are covered. Indicates that testing exits in every phase of SDLC life cycle
 

25) Test Case: test case is a set of input and output .here we pass the set of input and observe the output and system behavior

26) Test Scenario: Test scenario is a high level definition .here one can write one or more test cases

Example login

27) Test plan: Defines purpose, scope, approach, resource, responsibility of testing activities

Steps: Test Id, Intro, Scope and limitation, Test Objective, Assumption, Risk analysis, feature to be tested/Not to be, Roles and Responsibility, schedule, Test environment