Software Testing - Bug Life Cycles

Comments on article "Software Testing - Bug Life Cycles"
Name Views and CommentsDate
Rahul Soni It is good Nilesh. 6/24/2011
madhav this bug life cycle is very complicated.this life cycle not easy for undstanding 6/2/2011
Manesh This is good explaination given. previously, i had some doubt on these conxcepts. But as soon as i read this atricle, i cleared my doubt.. Finally, a nice article.. 11/18/2010
Rose lee It is very great article, but little bit confusing point. plz explain Dear. thanksssssssss 11/16/2010
kavita pillai entered information is partially correct. 11/16/2010
Dinesh kangabam It is piece of damn good article 9/11/2010
LATHASARAVANAN Its easy to unterstand 9/2/2010
prits very cleare answer. 8/4/2010
Dayakar Jale Nice article Nilesh, Bug life cycle is very well defined. 5/24/2010
venkatesh the artcile I read for Software Testing is all good and very useful with good illustrative
flow diagrams.		 3/30/2010
Mahendar Reddy It is a very useful and explained in detail.
thank you.		 12/13/2009
Srinivas HI Nilesh,

This is Srinivas, Software quality associate from Chennai. I just want to share my views on your publish.
You have done a very good job here. I agree to all the scenarios you stated here.
However, I just want to make one point clear here that a bug will never be postponed or deferred. Its actually lies on the development team members that they conclude that the system or code that needs to fix the Fix is critical and time consuming.
In this scenario the bug status will be marked as "delayed".

Actually the "Postponed" status is marked by Test team lead,

When testing of a particular bug has to be postponed for an indefinite period. This situation may occur because of many reasons, such as unavailability of Test data, unavailability of particular functionality etc. That time, the bug is marked with ‘Postponed’ status. Where as the "delayed" is marked by the development team member.

Please let me know what do you think.

Thanks for your time!

I appreciate your work here.		 9/23/2009
Nilesh Nagose Very well said Nilesh,

Thanks,

regards,
nil		 9/17/2009
little girl Thank you, Nilesh. It's great. Thanks for ur sharing 7/28/2009
venu 9955 Good one, thanks 4/28/2009
SAJ Any One have more Idea about Bug Closing Templete. 9/12/2008
lokesh I can understand the meaning easily with this step by step method and also the diagram shows how clearly the bug lifecycle is working 7/10/2008
little awesome 5/7/2008
Abhishek good explanation and totally up to the point. 4/7/2008
ali helpful articles about software testing....keep up the work 2/21/2008
Nandhini Really you answers are detailed in nature...One can come to know what exactly they look for... 2/12/2008
jay I m very thankful 2 u for given me this facility...........really u r nice person....... 2/8/2008
Bhanu Chowdary Very good explanation . Thank u so much Nilesh. 12/10/2007
raj Thank you very much Nilesh.Nice article on bug life cycle.
I was searching for it since long......
 12/5/2007
shankar Very good explanation 9/4/2007
anil katragadda excellent explanation about bug life cycles 8/20/2007
Venu Kumar This is used for all and special thanks to MR.Nelesh Parekh 8/10/2007
sudheer its very easy to understand for the beginers...thanking u for providing such a optimum notes .. 8/8/2007
Thiru very very exceland pic & description 7/30/2007
Madhumitha thanks a lot........really helped me .......... 7/23/2007
suman the topic is very well explained and really needs to be appreciated....
The diagram drawn is really the best....		 7/19/2007
Mayank the bug life cycle is explained properly. thanx for it 7/9/2007
bharathi wonderful....awesome article on bug life cycle 7/4/2007
parekhnileshp Hi Ajay,
Most of the times, it depends on the company and set of standards it has defined for bug tracking. For example a company may decide to keep bug priority, bug status, bug severity and bug resolution as four parameters in bug tracking ... where as another may decide to go only for bug priority and bug status ... it surely depends on the use or requirement.

But most of the companies follow, standard definitions/terms in order to be consistent with market (as already mentioned .. they may go for additional things/columns/info). Tools like Bugzilla are based on standard terms and definitions used in software testing field ... most of the times its common (same) for companies.

Hope this will be of some help for you ...
Don't forget to give us your feedback ...
Nilesh Parekh		 6/5/2007
ajay kumar rai i am using Bugzilla and in this there are two thing status and resolution.I would like to know each company use different method for Bug Tracking.
or there is a standardization of this process. I am looking for ur valuable response. Thanks in advance.		 6/4/2007
seenu Nice Description 6/4/2007
parekhnileshp Hi Geeta,
Winrunner is a software testing automation tool. It helps in automating (execute number of test cases in a series without human intervention) test cases.
You can refer to the answer I provided to question from Deepu for understanding of how winrunner can be used.

Hope this helps,
Nilesh Parekh		 5/27/2007
geeta what is winrunner and what script do in winrunner can u explain in simple words? 5/26/2007
raj good 5/24/2007
deepu thank u so much 5/13/2007
parekhnileshp Hi Deepu,
It solely depends on the owner (company) of the software who may think of to use an automated testing or manual testing depending upon requirements.
Generally, automation is used when there are huge number of test cases which differ in values or differ very slightly ... say for example ... you need to check a field which should accept number between range 1000 and 2000 and should not accept number from 2001 to 4300 and then accept number from 4301 onwards (this is just an example) ... so in order to thoroughly test this scenario ... you may need to run the same test with 10000 different values ... here if you go for manual testing, it may take lot of time ... hence you may chose to use automation.

Secondly, if you want to go for rigorous testing ... that time you may wish to go for automation.

There are several different criterias ... such as direct cost of using automation, need of automation, depth of testing, time in hand etc. which also help in deciding the right option to chose between manual testing and automated testing.

Hope this helps ...

Please do correct me in case if there is any misconception from my side, after all I am also a learner!
Nilesh Parekh		 5/13/2007
deepu can u please explain when to automate the pruduct?
and
when manual testing is easy why we need to automate the product?		 5/12/2007
deepu It is very useful site i learn a lot from this site thank u so much 5/12/2007
Krithika Hi this article about Bug life cysle is really very professional and clear 4/10/2007
santhosh your answers are very specific and good 3/5/2007
J.Asir JasonRaj bug life cycle here given is very good to understand
but the flow chart is not so good . i learnt many things from this
brief notes..
 3/1/2007
Veena Excellent and is very easy to understand 1/2/2007
anupam what ia valid and invalid bug 11/8/2006
parekhnileshp Hi Sri,
The priority of a bug can be High, Medium or Low based on the necessity to handle it. For example, if the business (i.e. your client) thinks that the bug you have uncovered needs to be tested before any other bug in the que, then the priority of the bug will be high, which also means that the client/developer thinks that the clearance of that bug is very important which might have a varying impact on the development and testing process in all. Same way the other priorities are also decided.
Many a times, the priority of the bug is decided based on combined result of many factors.
Hope this helps!
Nilesh Parekh		 10/23/2006
Sri hi,
nilesh can u tell me how can we consider the priority of bug as high,medium and low (i mean on what basis).		 10/23/2006
parekhnileshp Hi Srilatha,
Can you please re-phrase your question? Or may be you can contact me at catchnilu at rediffmail for direct communication.
Regards		 10/19/2006
Srilatha HI, Nilesh
can u give me an explanation how can we consider a test case that comes under basicflow,alternate flow and exception flow		 10/18/2006
Ramakrishnan Hi,

first of all congrats for ur contribution towards Testing. I always feel that Software testing has to gain importance as Software Development.

i was looking into the bug life cycle. its really nice.. but i think it can be consolidated and make it much simpler.

every time when a bug is produced, u can add a process called "Investigation" by the same tester instead of forwarding to Test Team. For example, for a day if the testers raise 50 bugs, it will be a difficult task for the test team leader to analyse the bugs.

you know that the test team lead cant spend much of the time in analysing the bug.

This is just a suggestion and i agree that process changes from Company to Company..		 9/5/2006
nandita Excellent job Nilesh 8/29/2006
parekhnileshp Hi Venkat,
Well .. .about Open ... its a state in which some action (fixing bug and asking it for Retest, Reject a bug, Assigning it to some developer) is needed to be taken.

If Pending Rejected status given by Deve Lead after some sort of analysis Test Lead felt that bug was really bug then second time, then its status will be REOPEN.

Hope that helps.		 8/24/2006
Venkat Raju If Pending Rejected status given by Deve Lead after some sort of analysis Test Lead felt that bug was really bug then second time what would be the status of bug ?New or Reopen? 8/24/2006
Venkat Raju Dear Nilesh,
You haven't explain about Open??
 8/24/2006
manish yes it really helpfull and easy to understand 8/19/2006
raja c hi very nice explanation of life cycle.it is useful for beginners.i got some doubt about when i stop testing?explain me. 8/16/2006
padmasri it's quite good! i would like to know about brief information about Boundary value analysis and Equivalance partitioning 8/15/2006
ganesh R.V ur article is good! i would like to know the seviority of bug and priority give me brief 8/15/2006
Pushpita Very useful page, helpmed me a lot for preparing for QA interview.
thanks
 6/29/2006
SV it's very gud atticle THANKS PAREKH 6/24/2006
Vijai Ur article is good. It is very usefull for begineers in Testing...... 5/22/2006
Mania good info provided 5/17/2006
Hi Sandeep,
Well if the bug is duplicated, then there can be two things ... either the bug (assumed) is not actually a bug, but an understanding problem ... this can be easily solved with the help of discussion with Team Lead or Developer ... in second case, the bug can be a bug which was fixed previously, but has surfaced after some process/operation ... in this case ... as IT IS INDEED A BUG ... you have to raise it to the developer, and you can either give fresh information such as screenshots and description or just give a reference of the original bug (e.g. Refer bug #123) ... and then the normal bug life cycle will be followed ... Hope this helps!		 4/25/2006
Sandeep What if the bug is duplicate 4/24/2006
Bhaskar Very nicely described ...thanks a lot Buddy . 4/24/2006
Daly Sunil Hi
The information provided by you on bug life cycle is extremely good .The material is very informative.
Thank you,
Daly		 4/11/2006
Thank you very much Alpa.
Regarding your point, I would just like to say that YES the status is in deed important for any bug. Otherwise it will be very hard to keep track of the bug and its history. Also ... if you miss on that bug .. just because you do not know which status it is in & not perform any operation accordingly ... then there can be a real big problem!		 3/24/2006
Alpa shah Hello,
I Read complete article. Very good collective summary of Defect life cycle. Only one thing I wanted to mention that the status used here for dev. lead & Test lead are really useful? If status of bugs can be putted simply as a New (by test team)..........Open(by Dev. team) ............Assigned/Reassigned (by Dev. team) ........Fixed(by Dev. team) ..............retest (Dev to Test team, & tested by tester)............. Closed(by tester).
Good Article		 3/23/2006
Nagaraju Vaidya Superb explaination 11/7/2005
Hi Krishnarao, it depends on the practice that a team leader follows. But best practice says ... and indeed it is true that the bug should be reported first to the team lead as soon as possible. The reason is very simple, suppose if you find a bug (that's what you think of it ... or may be it is really a bug), then in that case if you ask your team lead for confirmation ... then if it is really a bug ... probably you can proceed or if it is a problem in your understanding ...then discussion with your team lead would help you in getting ahead with the testing. Hope this will help! 9/19/2005
krishnarao Does the each and every bug found by the tester need to be report to test lead which he found or collect all the bugs and then report to test lead.which one is feasible. 9/19/2005
L.Sam It is good and understandable
 8/9/2005
Hari This is the simple way of explaining.
If the same(old) Bug already occured in the previous application. What is the Step.		 7/30/2005
Gangadhar it's very great to look and read this page 7/23/2005
Praveen This page will give information , whether bug is new bug or old , and whether the bug is fixed or rejected 7/8/2005
Use the feedback form below to submit your comments.
Your Comments:
Your Name:
Use the form below to email this article to your friends.
Recipient Email Address:
 Separate multiple email addresses by ;
Your Name:
Your Email Address:
More: Computers & Internet