Topic: When to stop testing ?

Message

   I received Build 1 from Developer and re-tested all issues fixed in Build 1 I also logged issues against Build 1.

I informed the Developer I was ready for Build 2 because I had finished re-testing all of the issues fixed in Build 1.

However, I noticed some additional items with Build 1 and logged. 

The
challenging Developer stated "I thought you were finished with testing.
I said no I told you I was finished re-testing the issues fixed in
Build 1 and that I was ready for a new build with fixes for issues
identified in Build 1."

My question is:
Should I have kept
testing or just waited til I received another build? I just happened to
notice more issues with the current BUILD 1 that I have installed and
logged the issue. I don't see the problem since we are in the testing
phase.

Author	Message
Sucheta Newbie Joined: 27Apr2007 Online Status: Offline Posts: 1	Topic: When to stop testing ? Posted: 27Apr2007 at 11:35pm
	I received Build 1 from Developer and re-tested all issues fixed in Build 1 I also logged issues against Build 1. I informed the Developer I was ready for Build 2 because I had finished re-testing all of the issues fixed in Build 1. However, I noticed some additional items with Build 1 and logged. The challenging Developer stated "I thought you were finished with testing. I said no I told you I was finished re-testing the issues fixed in Build 1 and that I was ready for a new build with fixes for issues identified in Build 1." My question is: Should I have kept testing or just waited til I received another build? I just happened to notice more issues with the current BUILD 1 that I have installed and logged the issue. I don't see the problem since we are in the testing phase. Post Resume: Click here to Upload your Resume & Apply for Jobs

	IP Logged

Piyali_2004 Newbie Joined: 28Apr2007 Online Status: Offline Posts: 1	Posted: 28Apr2007 at 4:53am
	It's so hard to give a simple answer to this one. It depends so much on the product, the build release frequency, the "alpha-ness" of the builds, etc. In our group, we EXPECT people to keep testing a build until the next one shows up. But then again, for a product that is batted back and forth like a ping-pong ball between one tester and one developer, I agree that it can get a little irritating to the developer to be told about yet another bug when he/she has just created a new build.
	IP Logged

Zakir Newbie Joined: 27Jun2007 Location: United Kingdom Online Status: Offline Posts: 1	Posted: 29Jun2007 at 12:42am
	The purpose of Softwre Testing is to ensure the functionality of the software is as per the FRS, so the simple way to deside when to stop the testing is, test case should have covered all the functionality of the application or the bug rate at certain level is very low.
	IP Logged


One Stop Testing Forum : Types Of Software Testing @ OneStopTesting : Functional Testing @ OneStopTesting