Bug Life Cycle / Defect Life Cycle


Bug Life Cycle / Defect Life Cycle


Before going into details, first understand few terms:

Bug: A flaw in a component or system that can cause the component or system to fail to
Perform its required function, e.g. an incorrect statement or data definition. A defect, if
Encountered during execution, may cause a failure of the component or system. [ISTQB-Glossary]
Any deviation from the expected with actual this means there is some issue in application and software.
There are many reasons for this deviation.

In term of software testing we difference between actual and expected results we can say it is a bug.

Life Cycle: Total time span between to two stages, to Birth till to its Death. We can take example to evaporation life cycle, in that there are many stages, each stage has its own recognition and has its own importance in entire cycle. If any of the cycle does not work properly then whole cycle gets misbalance
 In Bug life cycle we mean to illustrate what are the possible stages by which a single bug travels in entire life.

By seeing bug count we cannot suspect on capabilities of developer. Human has nature to do mistakes. Mistakes are unplanned errors. It is very hard to find out the bugs in self-developed code. It is just like destruction of self-constructive task.

Now we take bug life cycle in detail:
There are many stages in BUG LIFECYCLE

                        



1. New – As a discrepancy between Actual and Expected, software test engineer report it into bug tracking toll and keeping its stage as new. This reported new bug is marked either to QA / QC manager or QC Team Lead.

2. Reviewing of raised bug (Open / Closed) –As software test engineer report a bug, it start showing on QA / QC Manager Dash board. QA /QC manager review this defect; if He / She find it a valid bug then they change the status of raised bug to Open and marked it Development Manager / Development Team Lead. Otherwise He / She close the bug. It is not necessary raised bugs always review by Development manager / Development Team Lead, it should reviewed by Functional Head (Domain Expert) and Business Analyst  

3. Assign – After marking bug to concern Development Manager /Development Team lead at this stage state of bug is Assign.

4. Rejected – At this stage Development Manager Review concern raised bug and if it looks a valid one then Development Manager take it into action otherwise it marked it as rejected. As manager marked as Rejected then they should have valid reasons for it.

5. Duplicate – There may be possibility that number of test engineer are working on one project and one application module is assigned to more than one tester  in that cases possibility of identifying same bug increases. Resulting duplicate bug reporting.  It is not fruit full to reporting duplicate bug.
               
6. Deferred – As raised bug is review by concern person, they take a decision to when and how to entertain raised bug. In that cases review person finds that we should take this bug in coming version / releases. There may be possibility that requirements are not clear at a point of instance and severity / priority of raised bug is not a anxiety in current release. In that cases bug is valid BUT its state is Deferred.

7. In Test – Once the bug is approved by concern authorities, development team member start working on it. As all the valid are completed from the development team they provide new release to testing team. In new release there may be possibilities to have new points as well as fixed bugs.
While working on bugs’ development team members come across on various practical challenges:
- Unable to replicate the raised bug in development environment.
- Incomplete details provide by tester (Missing of Log file / Attachment is missing, etc.)
- Due some constraints (Project level / Technical / Manpower, etc.) and many more.

8. Verifying / Retesting – As development is done then all bug are clubbed into one release and again send to QA / QC team to retest them. In this tester again doing testing of raised bugs. If  tester find the bug still occurring then they marked as reopen otherwise they marked as closed. While resting the bugs
Testers are performing regression testing also. In regression testing they are trying to find out bugs which are produced by the reworking on bugs by team. There are few bugs there occurrence is very rare, we can say one in thousand these type of bugs called intermittent bugs.
               

                       
         Bug Life Cycle | Defect Life Cycle |Bug | Life Cycle | Retesting | Regression testing |

Comments

Post a Comment

Popular posts from this blog

Interview Question Part Three

Interview Question Part Three      1- How to click on the button in front of the name in webtable?    2- How to access the excel as a database using adodb.connection? How to specify columns?    3- How to come out of the function when error occurs.    4- Explain use of on error resume next, raise error, err object in QTP?    5- Can we create classes in VB script or QTP?    6- How to create constructor in class in vbscript? What are the default methods in class?    7- Explain Loadfunctionlibrary in QTP.    8- on error resume next will jump after next line or block?    9- How to do automation estimations like efforts required to design framework, automate app?   10- How to trigger the web element events like click, mouseover, mousedown in QTP?   11- How to calculate return on investment (ROI) for automation projects?   12- What are the diffe...
Read more

Interview Question - Part Four

Interview Question - Part Four asked in Tech M / JP Morgan & Clear2Pay - How many types of Object repositories are there in QTP (Ans: Share & Local) - Tell me about yourself. - What are the Repository features (Ans: Object locator, Add, Merging, Comparing) - How to create a recovery scenario? What does recovery scenario manager do? - How to calculate number of Web links in a web Application using descriptive programming? - Open a word file and modified with some value using QTP? - How to create a excel file using QTP? - How to retrieve a value from web table? (Ans: Get Celldata(row, col)) - What is QC requirement tab do? And how to map the requirements? - What is defect Life Cycle? - What is difference between smoke testing and sanity testing? - What are the main content in the Test plan? - How to create environmental variable? - How to create Action? - How many types of action are there in the QTP? (Ans: Non-reusable, Reusable, Ext...
Read more

QTP Fundamental - Part One

QTP Fundamental - Part One  - Example 1: Validate if a webtable exist boolExist = Browser(…).page(…).webtable(…).exist - Example 2 : To Find number of rows and columns in a web table intRowCnt=Browser("Google").Page("title:=.*").WebTable(“name:= TTable").RowCount For r=1 to intRowCnt ‘’ This will loop through each row and tell count of column in each row. intColCnt=Browser("Google").Page("title:=.*").WebTable(“name:=TTable").ColumnCount(r) MsgBox intColCnt Next - Example 3: How to get data in a particular cell in the data table strData= Browser("Google").Page("title:=.*").WebTable(“name:=TTable").GetCellData(r,c) Where r = row number and c = column number - Example 4: Using childObject method to find objects of a particular type within a webtable Public Function func_findObjectinaWebTable(strObjType) Set objDesc=Description.Create objDesc("micclass").value=strobjType set objChild=Browser("Goog...
Read more