GeekInterview.com
Series: Subject: Topic:
Question: 305 of 321

Define Bug Life Cycle?
What is Metrics

Plz give me the answer
Asked by: Interview Candidate | Asked on: Sep 22nd, 2005
Showing Answers 1 - 30 of 30 Answers
arulmozhi

Answered On : Oct 3rd, 2005

View all answers by arulmozhi

  
Login to rate this answer.
surendra

Answered On : Oct 8th, 2005

 hi this is surendra                        the answer to ur query is  when tester found the bug for first time the status is NEW and then report the defect in buh racking tool the status is OPEN ,  then the developer  fixes the defect and changes the staus to RESOLVED , then tester retest it to check it correctly fixed or not . and hegives it status as CLOSED.  if the same defect raises status is  REOPEN                                             SURENDRA

  
Login to rate this answer.
selvaraj

Answered On : Oct 24th, 2005

The different stages that a defect undergoes during the test life cycle of an application.The various stages the a defect changes areNew: when a bug is found for the first time.Open: when the bug is assigned to Test lead or DeveloperFixed : when the defect is solvedretest: when the defect is retested after fixed by the developer.Duplicate: When the same defect is raised for more than one time by the same tester or else otherDeffered: A defect that can be fixed in the next release build or versionreject: when the developer does n't accept with tester

Yes  2 Users have rated as useful.
  
Login to rate this answer.
Fayyaz

Answered On : Oct 24th, 2005

Bug Life Cycle - When error, goof, glitch or bug has been identified in the software going under test. The defect should be reported to the log file manually or to the automated management tool. Once this has been submitted to the system. Based on the severity level of the defect it can be fix by its priority level. It should assign back to the developer for fixes. Once it fixed this should be retested again to make sure the error is not reproduce able.  Metrics - Metrics is a tool that can be use to track progress of the testin life cycle. Metrics allow to keep track of the test development, test execution and test restults. It keeps aware management and tester of the testing progress.

Yes  1 User has rated as useful.
  
Login to rate this answer.
srinivas

Answered On : Oct 27th, 2005

What is a Bug Life Cycle?

  
Login to rate this answer.
saraswathi

Answered On : Nov 2nd, 2005

bug detectionbug analysisbug fixingbug analysisbug closure

  
Login to rate this answer.
saraswathi

Answered On : Nov 2nd, 2005

bug detectionbug analysisbug fixingbug analysisbug closure

  
Login to rate this answer.
kalyan

Answered On : Nov 4th, 2005

Bug life cycle begins when the bug is found by the tester and it will send to the developer, developer fix the bug ,after fixing the bug he will resend to tester , tester test the bug again if the bug is fixed , it will be closed if not it will reopen and again he will send the bug to the developer .That is the Bug life cycle.

Yes  1 User has rated as useful.
  
Login to rate this answer.
chandu

Answered On : Nov 7th, 2005

Whenever I find a bug I would check it 3 or 4 times before logging it as a bug. I use Test Director as a bug tracking tool. If I find a bug I would log that bug and attach the snap shots of it, and also information like where it occurred, under what circumstances, and the test data given, and then send it to the developer. Then the status of the bug will be given as NEW. When the developer sees it he would change the status to OPEN, which means he is working on fixing the bug. Once the bug is fixed, he would change the status to FIXED. And I would test the application again by doing regression testing. If I am satisfied I would close the bug and the new status of the bug will be CLOSED. If I am not satisfied I would re-open the bug and here the status will be RE-OPEN.

  
Login to rate this answer.
jyothirmayi

Answered On : Nov 11th, 2005

Metrics is the system that deals with the tasks in quatifying the details to have the clarity over it to deside whether the task is profitable.

Yes  1 User has rated as useful.
  
Login to rate this answer.
Paramjit

Answered On : Nov 16th, 2005

1. find a defect in the system.2. Write the steps to reproduce, actual result, expected result, hardware used.3. Log the bug into the defect tracking system like Silk Radar.4. The status of Bug now is Open for QA.5. Now it It is confirmed by some other QE member.6. After confirmation, its status changes to the Open for Development.7. It is then assigned to developer's inbox in the deftect tracking system.8. Developer fixes the bug and Mark it is Fixed.9. Now again bug status changes to the Open for QA.10 Now QE member who filed the defect, test the bug as per steps to reproduce.11 IF the bug is fixed, The bug is closed.12 If the bug is not fixed, it is rejected and it again goes to developer's inbos.13 Unless the bug is fixed, Same procedure is followed given after step 8.

Yes  1 User has rated as useful.
  
Login to rate this answer.
thricool_10

Answered On : Nov 25th, 2005

View all answers by thricool_10

Metric is a mathematical Number that shows a relationship between two variables.A quantitative measure of the degree to which a system component or process possess a given attribute.

  
Login to rate this answer.

The Bug life cycle starts when the tester found a bug. It's as followsNew/Open: When developer found Bug at first timeFixed: When developer accepts the Bug is BugTesters Errors: When developer not accept the Bug and it's Tester side error . ie it's not a bug according to FRS.Hold:There is a clash between Developer and Test engineer about the bug.Reopen: When the bug is again arised even the Developer change the status of the Bug as 'Fixed'

  
Login to rate this answer.
Uttam Thakur

Answered On : Dec 5th, 2005

  The Bug Life Cycle::                    1)       Tester found bug.                                (Open)                                 ...........Status        [Tester give the brief and where the actual Problem occuers in a document]                   2)    Bug is assign to the developer ,devloper takes the problem right from there and try to fix or fix it.                           (Open)                 .............Status  3)    After fixing bug it again assign to Tester for retesting or regression testing.                                                                (Open)         ................Status4)  Tester retest or regression test that the problem is resolved or bug is fixed and ensure that it is fixed and there is no more effect of that particular bug.                                       (closed) .........................Status5)  Now Bug is closed(Status) that it get fixed.

  
Login to rate this answer.
uttam79

Answered On : Dec 5th, 2005

View all answers by uttam79

There are Four stages of bug Life Cycle:                        1)    Tester Found Bug.[ he give a detailed discription of that bug and where it actually occures]                               Status( OPEN)                  2) Bug is assign to the programmer .[ Programmer get the information provided by the tester in a Document and take the right there where the actual problem occurs]                                   ( OPEN)                   3) Programmer fix the Bug and send it back to the tester for retesting or reresssion testing.                                        ( OPEN)                  4) After retesting or regression testing Tester ansure that the Bug is fixed and it is no  more effective,Tester now close the bug.                                      (Closed) 

  
Login to rate this answer.
sowmya

Answered On : Jan 5th, 2006

New,close etc are the status of bugs.Life cycle is:- 1.Bug detection 2.Bug reproducible 3. Bug reporting. 4.bug fixing 5.Bug resolving 6.Bug closingMetrics also refers to traceability matrix which is a document that helps to trace the requirements and also verify whether the testcases developed are mapping all the requirements

  
Login to rate this answer.
Pushpa

Answered On : Feb 15th, 2006

Bug Life Cycle :Bug Life Cycle starts with bug detection by the testing team and is checked out whether the bug is reproduceable continuously or rarely. After confirming this, bug is reported to the development team. There will be a triage meeting in which QA lead is explaining the bug to the development team while development team lead is asking questions. Here the bug may be accepted/rejected/deferred based on various factors. Once it is accepted as a bug by the development team, then development team will assign this bug to the appropriate person to fix it. After fixing it, they will subimit it to the QA team. They will conduct regression testing to check out whether the bug is fixed properly or not. If is it fixed, the bug will be closed else the cycle repeats until the bug is fixed.Detecting the bug ( birth place of the bug )Reproducing bug ( checking whether it is reproduceable or not )Reporting the bug ( through IEEE format )Bug fixing ( Accepted/Rejected/Deferred )Bug ResolvingBug Closing ( death stage of the bug )

  
Login to rate this answer.
pravesh gupta

Answered On : Mar 16th, 2006

When a Bug found1. Lock the bug using bug tracking toolStatus Follows:2. New - Tester3. Open - Developer While removing4. Fix - When removed and go to back to tester for retest5. Closed - Tester finds that bug has removedOr5. ReOpen - Not Fixed By Tester6. Reject - By Dev Senior - That this is not bug.

  
Login to rate this answer.
hari

Answered On : Apr 9th, 2006

Bug life cycle steps:1)detect defect2)reproduce defect3)report defect4)bug fixing 5)bug resolving6)bug closing

Yes  1 User has rated as useful.
  
Login to rate this answer.
supriyac

Answered On : Apr 14th, 2006

View all answers by supriyac

U r correct surendra but it's not necessary that everytime developer fixes the bug sometimes the status given by developer could be defer/ not a bug /pending also due to some reasons.

  
Login to rate this answer.
tulasi

Answered On : Apr 24th, 2006

Defect detectionDefect repoducivityDefect fixingBUg ResolvingBug closing through regression

  
Login to rate this answer.
harsha

Answered On : Jun 29th, 2006

chandu excelent and clear answerthanks

  
Login to rate this answer.
visitor

Answered On : Oct 15th, 2006

HiBug Life Cycle: If Test Director is used for tracking defects thenReport DefectsSet Repair PrioritiesRepair Open DefectsTest New BuildAnalyze Defect Data.Cheers

  
Login to rate this answer.
sujatha

Answered On : Jul 6th, 2007

Bug Life Cycle:1. Finding the bug.2. Reporting the bug - status - open.3. fixing the bug4. retesting the bug5. closed -if the bug is no more bug.6. reopen if the bug is still open.Metric :In Quality Assurance, the quality of the product is measured in metrics.

  
Login to rate this answer.
Sujatars

Answered On : Aug 15th, 2007

View all answers by Sujatars

Bug life cycle is tracking the bug from the time it is opened till it is closed .

  
Login to rate this answer.
vishalnaib

Answered On : May 12th, 2008

View all answers by vishalnaib

The Bug since it is detected goes through many phases .The moment it is discovered it is in the NEW state.Then there is a discussion between the testing team and the development team where it is decided that whether it is actually a defect or not .In case it is concluded that there is a defect(drfit from the expected result), the defect moves to OPEN state.The development team then fixes the defect and it goes for Re-Testing. If the defect is removed , then it goes to the Fixed state . After Re-Testing we often perform Regression Testing, to ensure that no other defect has come up due to the changes made . In case the Regression Test passes successfully, the defect moves to the CLOSES/TERMINATED state. Metrics : Software metrics are numerical data related to software development. Metrics strongly support software project management activities. They relate to the four functions of management as follows: 1. Planning - Metrics serve as a basis of cost estimating, training planning, resource planning, scheduling, and budgeting. 2. Organizing - Size and schedule metrics influence a project's organization. 3. Controlling - Metrics are used to status and track software development activities for compliance to plans. 4. Improving - Metrics are used as a tool for process improvement and to identify where improvement efforts should be concentrated and measure the effects of process improvement efforts.

  
Login to rate this answer.

Hi AllBug life cycle starts when the defect is reported by the Tester.The various stages of Bug Life cycle are:1. OPEN: When defect is found and reported2. ASSIGN: When defect is assigned to the development team after discussion with the PL.3.FIXED : The Developer fixes the defect4. RETEST: The Tester has to confirm that the fixes are completed by the Develper5.CLOSED: When the team accepts that the bug is fixed. There can be a DEFERRED or Duplicate state when the defect can be fixed in next release or is a duplicate issue reported.Thanks

  
Login to rate this answer.

The different stages that a defect undergoes during the test life cycle of an
application.
The various stages the a defect changes are
New: when a bug is found for the first time.
Open: when the bug is assigned to Test lead or Developer
Fixed: when the defect is solved
Retest: when the defect is retested after fixed by the developer.
Duplicate: When the same defect is raised for more than one time by the same
tester or else other
Deffered: A defect that can be fixed in the next release build or version
Reject: when the developer does not accept with tester
some others are also the part of defect life cycle.
1-New
2- Inprogress
3-Awaiting Sign-off
4-Passed/Closed
5-Failed/Refix
6-Canclled/Closed
7-Invalid/Closed
8- After XSLT/UAT deploy
New
In-Progress
Awaiting Sign-off
Passed & Closed
Failed/ Refix
Cancelled/Closed
Invalid/ Closed
After XSLT/ UAT Deploy

Metrics - Metrics is a tool that can be use to track progress of the testing
life cycle. Metrics allow to keep track of the test development test execution
and test results.
It keeps aware management and tester of the testing progress

Yes  1 User has rated as useful.
  
Login to rate this answer.

Bug Life Cycle:New : Logged the bug by TEOpen: After review it by team lead then changed it's status to open Fixed : Once dev agree with that he can change the status to fixed once fixed that issueClosed: If issue was fixed properly then TE will retest it then he will closed itRe-open: If Issue was not fixed properly then TE can change the status to Re-openDeffered: If issue is out of scope, or dev thought that he can do it in next release then he can change the status to Deffered.In-progress: If issue still under process of fixing the dev will change status to InprogressNot a bug: If issue was not an issue then dev will change status to NOt a bugNot Reproduceble: If issue was not able to reproduce as per steps given by TE then will change status to NOt Reproducable.Metrics: Quantifying the work in terms of excel sheets.

Yes  1 User has rated as useful.
  
Login to rate this answer.

Bug Life  cycle is a process of identifying the defect and subject to rectification.Metrics means measures.(what are all the measures taken to identify the defect)

  
Login to rate this answer.

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

Related Open Questions

Ads

Connect

twitter fb Linkedin GPlus RSS

Ads

Interview Question

 Ask Interview Question?

 

Latest Questions

Interview & Career Tips

Get invaluable Interview and Career Tips delivered directly to your inbox. Get your news alert set up today, Once you confirm your Email subscription, you will be able to download Job Inteview Questions Ebook . Please contact me if you there is any issue with the download.