| Name |
Views and Comments | Date |
| Girish |
what is the role of BA in defect life cycle |
9/30/2009 |
| c.yuvaraj |
its nice to have a overlook about bugs |
7/10/2009 |
| Midhun |
Excellent information... |
7/9/2009 |
| Koushik Datta |
It Really helped me.
Thanks. |
1/23/2009 |
| krishna kumar. |
Thanks for giving the good statements... |
9/16/2008 |
| sheeba |
It is good and I want information about bug resolution |
7/1/2008 |
| Rajesh |
what are following bug statuses
As designed,
Patched,
Query,
|
2/27/2008 |
| Sheela.K |
And also I need the information about,How to test Mobile devices like Visiontek, Microfex,PDA, etc., |
1/11/2008 |
| Sheela.K |
Generally Is there any procedure for Mobile Testing? If it is there means,what kind of procedure is following for Mobile Testing?. |
1/11/2008 |
| Sheela.K |
Can u send me the Mobile Application Testing Documents? and Types of Mobile Testing etc. |
1/11/2008 |
| Sheela.K |
Hai Nilesh,
I studied ur testing documents. It's simply Superb. It's very simple and easily to understand. |
1/11/2008 |
| vijay |
In QC in ths testplan tab on wt basis i have to create folders(ex: functional,GUI,contetnt,navigation) or can i write all the test cases under on folder ?? can any one can answere for my question. |
11/19/2007 |
| purushotham |
Exlent ,very good
thank u |
10/31/2007 |
| Nataraj |
As per my knowladge when new bug is found its status is NEW. After that team lead test it and if it is valid then he give its status OPEN. Once the team lead change the status as OPEN, H assigns the bug to corresponding developer or developing team,then the state of the bug is chaged to ASSIGN. after that same as u written. |
10/7/2007 |
| senthil |
wat is a bug life cycle and how we maintain? |
6/29/2007 |
| Jayshri |
what is implement? can tester also do this role? how? |
6/22/2007 |
| parekhnileshp |
Hi Sachit,
Generally Tester or Test Leader changes the status of the bug to Deferred. But it also depends on the privileges awarded to an individual.
Hope this will help ...
Nilesh Parekh |
6/6/2007 |
| Sachit |
Q. In some cases a particular bug stands no importance and is needed to be/can be avoided, that time it is marked with ‘Deferred’ status, but who market it as 'Deferred'? |
6/6/2007 |
| parekhnileshp |
Hi Devi,
Its a business need or may be decision that has to be taken by Team Lead. Developer in any case needs to consult with his/her Team Lead before changing the bug status to Deferred!
But for your question ... yes ... Developer can change the bug status to Deferred ... but this again depends on the practice being followed ... for example ... there might be certain statuses that only Team Lead or Business Analyst can change and not developer ... Hope this helps!
Regards,
Nilesh Parekh |
4/19/2007 |
| Devi |
Nilesh Hi,
Have a doubt.... Is the Deffered status set by the developer when that bug is valid and that has to fix in the next release because of low priority or when the bug has no importance...? |
4/18/2007 |
| parekhnileshp |
Hi Sailaja,
As far as I know ... regression testing is itself a type of testing ... whereas RETESTING is a test performed to make it sure that the particulare functionality is working fine or any previously unveiled bug is fixed or not. You can take it this way ... eating complete pie is regression testing ... cause you will be doing the same action again and again ... no matter what's the result (meaning even if you eat more create at a time or less) ... but retest is ... you eat once and have a doubt that the pie is stale and now you want to confirm that your doubt is valid so you will eat it one more bite!
Hope this helps ... please let me know if any of concepts presented here has any flaw ... we will like to improve on our content to help readers!
Thanks and regards,
Nilesh Parekh |
4/13/2007 |
| sailaja |
Answers are very nice.Can u tell me diffrence between retesting and regresion testing |
4/12/2007 |
| prasad |
very noice |
3/9/2007 |
| Rashmi Patel |
Hi,
I like very much ,your articles are too good and help full.
Thanks |
3/8/2007 |
| parekhnileshp |
Hi Shaun Merrill,
A typo does not mean I don't know anything about grammar. Your invaluable suggestions are always welcome!
Thank you very much for your help in improving our content!
Nilesh Parekh |
2/21/2007 |
| Shaun Merrill |
Nilesh: Your "Pending Rejected" description is unintelligible. Please correct your grammar. |
2/21/2007 |
| Amit |
it's wonderful, very easy to learn. |
2/3/2007 |
| pradeep |
it's best to read. |
2/1/2007 |
| pitchireddy |
it is very excellent. 100% Every one understood , |
11/20/2006 |
| Rajiv |
Its a very good documentation covering most of the testing content in a very simple way. Great work indeed. |
11/14/2006 |
| raja |
it's good and useful |
11/13/2006 |
| Uday Kumar T.V. |
Thank you very much for this article. It has given a clear real time idea of the Bug life cycle which is a big confusion. |
11/6/2006 |
| Sangeetha |
Really Superb . Very easy to follow and keep in mind. |
10/25/2006 |
| bprajeshwar rao |
its so nice but we need more |
10/18/2006 |
| Neeraj Kr.Dutta |
sir i want to know the software bugs and its life cycle and how it is reported and fixed??
my email address is neerajk_dutta@yahoo.co.in |
10/10/2006 |
| saroj singh |
very good |
9/16/2006 |
| abhijit |
Send me Check List For Software Tester While Doing Testing |
9/11/2006 |
| Bhavesh Patel |
in case of defered bug there may be case that bug need discusion to fix it not bz of time issue or fixing of it eill influence retesting of many module and time is less for this so it can be put to defer case |
8/30/2006 |
| ram |
no doubt it is very document on bug life cycle.In this one also one mistake is there. Actually "open"status is given by test lead any where.check it |
8/30/2006 |
| suma |
Hey thanx ,for the good description of the bug life cycle...it helped me understand better than my institute.
|
8/14/2006 |
| parekhnileshp |
In an another scenario, if some external factor such as network connection is not working properly, environment required for the software is not set or anything else causes the software under test to behave in a way, which it is not supposed to ... and if the tester considers it to be a bug (e.g. if you are trying to open buzzle portal site index page and your network connection is not working fine and you get PAGE NOT FOUND error page ... would it be buzzle portal problem or your network problem?) ... in this case also developer can reject the bug (Here developer has to analyse and provide proof of external factor influence and also solution for such condition if possible).
Hopefully the above scenarios will help you understand what you are looking for. |
8/8/2006 |
| parekhnileshp |
Take it this way Abhishek, when a tester finds out a bug (according to a tester ... ) he/she will be sending it across to a developer. Now if the developer finds the CONDITION (particular scenario and software behavior) mentioned by the tester as a bug is not actually a bug ... but is a problem in tester's understanding ... then in that case ... developer may reject it saying its a mistake in requirement understanding and not a bug (developer has to provide proof of it). |
8/8/2006 |
| Abhishek Jain |
I have a Question , Can you Please answer it.
In What Cases Developer Reject the Bug reported by the tester
|
8/7/2006 |
| ManjuShree |
in bug life cycle the order should come as new ,open then assigned
not asigned ,open |
6/14/2006 |
| Dharamvir |
diagrams r very important........include some |
6/8/2006 |
| Hema |
It is good explaination about the bug life cycle. Thank you for giving the information about this. |
5/18/2006 |
| Das |
good but show using images/pictures |
5/9/2006 |
| Anand.Y |
It was simple and easy to understand...
It will be better if you explain with a neat diagram |
4/13/2006 |
| Mantas |
very nice article! |
12/1/2005 |
| manish |
this article has been compiled very nicely |
8/31/2005 |
