1. What is Bug life cycle?2. Test case biggest number of given three numbers?

Questions by dkarthikmca   answers by dkarthikmca

Showing Answers 1 - 9 of 9 Answers

arjun

  • Jul 7th, 2006
 

Bug life cycle contain the detail about the bug which we found during the testing.like

1:Defect ID

2:defect discription

3:status

4:severity

5:preority

Q2:Techniques of writing test cases

 1:equivalance class partioning

2:boundry value analysis

3:error guessing

  Was this answer useful?  Yes

sudhakar

  • Aug 9th, 2006
 

Bug life is the work flow between the developer and tester. At first tester  receiving of the build from developer. The  Testing of build when you recieved developer is called as New. Then the Bug get sloved and place in Defect tracking

  Was this answer useful?  Yes

sudhakar2068

  • Sep 23rd, 2006
 

Bug life cycle is the work flow between the developer and tester. when tester assign the bug to the developer he fixes the bug and  given to the tester for

retesting.

verify the  numbers of the biggest.

sudhakar kolla.

My Email:kollasudhakar2005@yahoo.co.in.

My Number:09819859346.

  Was this answer useful?  Yes

Anitta

  • Nov 30th, 2006
 

Hi,

Bug Life Cycle: Bug life cycle is the work flow between the developer and the tester. The Life of a Bug starts from when it is logged and ends when, its Fixed by the Developer & Verified/Closed by the Tester.

There are different stages/status that a bug goes through,such as the following.

1) Open

2) Fixed

3) Defferred

4) Duplicate

5) Fix Later

6) Verified

7) Closed

Regards,

Anitta

  Was this answer useful?  Yes

skiran19

  • Oct 25th, 2007
 

Bug Tracking is the process/series of steps followed from the time a bug is found, fixed and closed. The steps followed are:-

1.) As soon as the bug is found it is entered into defect tracking system and assigned the status "NEW".
2.) Once its been analysed and accepted as a geneuine defect, the status is changed to "OPEN". If the bug is found to be invalid the status is changed to "REJECT".
3.) Its then assigned to a developer, status is changes to "ASSIGNED TO".
4.) Once its been fixed by developer status changes to "FIXED/READY TO TEST".
5.) Tester then re-test the fix and if fix works fine, he/she set the status to "CLOSED". If the fix doesnot work its changed to "RE-OPEN'.
6.) In some cases, if the bug is a major fix then it is posponed to future realeses in which case the status is changed to "DEFFERED' and consider for future release.

  Was this answer useful?  Yes

Give your answer:

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

 

Related Answered Questions

 

Related Open Questions