abusaud

 Profile Answers by abusaud 

• Jul 1st, 2008

 

jsu tretest the bugs its called restest......then prepare the bug less application then test the full application ...if there any bugs raised make status as new raised bug

prachu_mca07

 Profile Answers by prachu_mca07 

• Jul 25th, 2008

 

In a cycle all bug status appeared as closed, we will go for the recycle else continue with the cycle.

Lipsitas

 Profile Answers by Lipsitas 

• Aug 27th, 2008

 

After fixing the bug we will go for the recycle. Because there may be impact in the other areas due to those bug fixing.

sudhajoyus

 Profile Answers by sudhajoyus 

• Nov 7th, 2008

 

After fixing that bug we will go for recycle, Fixed bug may be affect another module.

akaper

 Profile Answers by akaper 

• Nov 24th, 2008

 

We should go for a recycle

srinivasulub1981

 Profile Answers by srinivasulub1981 Questions by srinivasulub1981

• Nov 29th, 2008

 

By reading the question i came to know that there are 10 cases, 5 failed, 5 passed, so that means complete cycle is over! so there is no scope to continue with this cycle.. so we must definitely go for retesting. If all fixed are closed then again we should go for regression testing.

Srinivas

vk1978

 Profile Answers by vk1978 Questions by vk1978

• Apr 16th, 2009

 

we have to go for recycle...

as 10 test cases are executed and as you said 5 failed testcases were fixed.

shakilag

 Profile Answers by shakilag 

• Jun 23rd, 2009

 

This depends on the priority of the failed test cases and hence of the logged defects too.

So there are two possibilities:

1) If a majority of the defects are of severity - very high/high then a recycle is needed to carry out a bug fix regression.

2) But if the majority of failed test cases are low in priority(checking of a logo/label) then we can continue with the cycle and do an interim check of the status of defects and give a build before the cycle is complete.

saravanan123

 Profile Answers by saravanan123 

• Jul 10th, 2009

 

Once the 5 bugs has been fixed than we have to go for retesting at that time it is passed we can leave it.
Hence we should go for recycle because if the developer are fixing the bug means it is developer modifying the inner data due to modification sometime it can be have to any other new kind of bug may arise in order to overcome we should go for recycle process it will be taking some time but once it has been integrated than at that time it is very difficult to clear.

mathan_vel

 Profile Answers by mathan_vel Questions by mathan_vel

• Aug 12th, 2009

 

After fixing the bug we will go for the recycle, retest the bug and execute all other test cases for the impact(Regression), the cycles should followed on sure of all bugs is Closed.

rajmohan23

 Profile Answers by rajmohan23 Questions by rajmohan23

• Aug 22nd, 2009

 

After fixing the bugs we must go for unit regression testing bcause whether the rectified part cause any errors in the un-tested part. so we must go for re-testing after that only we will continue.

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 25th, 2009

 

The answer to this question depends on whether or not we have met our exit criteria.  If our exit criteria has been met, perhaps it was a mistake to even fix the defects.  How much resources will be required to execute the next test cycle, and do the fixes provide enough added value to warrant the additional costs of testing? 

We will not conduct another test cycle if all of the following conditions are true:

1) The number of defects found in the previous test pass combined with all other non-closed defects are few enough and of low enough priority that we have satisfied our exit criteria.

2) After evaluating the risks of all non-closed defects, it is concluded that there are no significant impacts on the product. 

3) The cost to test the next build exceeds the benefit of adding the current fixes.

If any one of these three conditions is false, then we will likely conduct another test cycle.