<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: What if there isn&#8217;t enough time for thorough testing</title>
	<atom:link href="http://www.softwaretestinghelp.com/what-if-there-isnt-enough-time-for-thorough-testing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.softwaretestinghelp.com/what-if-there-isnt-enough-time-for-thorough-testing/</link>
	<description>Software Testing Complete Guide</description>
	<lastBuildDate>Fri, 10 Sep 2010 15:44:41 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Indu Sharma</title>
		<link>http://www.softwaretestinghelp.com/what-if-there-isnt-enough-time-for-thorough-testing/comment-page-1/#comment-70285</link>
		<dc:creator>Indu Sharma</dc:creator>
		<pubDate>Wed, 25 Aug 2010 12:18:09 +0000</pubDate>
		<guid isPermaLink="false">http://softwaretestinghelp.com/?p=31#comment-70285</guid>
		<description>Effort estimation is very simple:

&gt;&gt;1st u have to find out all the possible scenarios in all features.
&gt;&gt;Then Make a traceability matrix i.e. for each requirements how many test cases are required.
&gt;&gt;Suppose if u have 100 testcases, then calculate how many test cases one person can execute in a day(here u have to consider difficult and easy both types of test cases)
&gt;&gt;If one person can do 5 test cases in a day then in 20 days all test can be executed.i.e effort=20PD or 4PW.
&gt;&gt; Now u have to add following facters:
1. What if 30% Testcases failed in Run1, then u have to rerun all those test cases. So u have to consider 35 testcases failure i.e 7PD or 1.4 PW
2. What if say 10% testcases failed in Run2 then i have to re-run 10 testcases again. so its 2PD or 0.4 PW

Now, Total effort= 4PW+1.4PW+0.4PW=5.8PW(Person week)

This is just a example i gave... u can add if there are any opther variants which impact ur execution.

regards,
Indu</description>
		<content:encoded><![CDATA[<p>Effort estimation is very simple:</p>
<p>&gt;&gt;1st u have to find out all the possible scenarios in all features.<br />
&gt;&gt;Then Make a traceability matrix i.e. for each requirements how many test cases are required.<br />
&gt;&gt;Suppose if u have 100 testcases, then calculate how many test cases one person can execute in a day(here u have to consider difficult and easy both types of test cases)<br />
&gt;&gt;If one person can do 5 test cases in a day then in 20 days all test can be executed.i.e effort=20PD or 4PW.<br />
&gt;&gt; Now u have to add following facters:<br />
1. What if 30% Testcases failed in Run1, then u have to rerun all those test cases. So u have to consider 35 testcases failure i.e 7PD or 1.4 PW<br />
2. What if say 10% testcases failed in Run2 then i have to re-run 10 testcases again. so its 2PD or 0.4 PW</p>
<p>Now, Total effort= 4PW+1.4PW+0.4PW=5.8PW(Person week)</p>
<p>This is just a example i gave&#8230; u can add if there are any opther variants which impact ur execution.</p>
<p>regards,<br />
Indu</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: krishna</title>
		<link>http://www.softwaretestinghelp.com/what-if-there-isnt-enough-time-for-thorough-testing/comment-page-1/#comment-70160</link>
		<dc:creator>krishna</dc:creator>
		<pubDate>Tue, 24 Aug 2010 13:58:13 +0000</pubDate>
		<guid isPermaLink="false">http://softwaretestinghelp.com/?p=31#comment-70160</guid>
		<description>can you please tell me and send the documents on how to calculate test estimation</description>
		<content:encoded><![CDATA[<p>can you please tell me and send the documents on how to calculate test estimation</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Indu Sharma</title>
		<link>http://www.softwaretestinghelp.com/what-if-there-isnt-enough-time-for-thorough-testing/comment-page-1/#comment-42646</link>
		<dc:creator>Indu Sharma</dc:creator>
		<pubDate>Sat, 21 Nov 2009 21:55:51 +0000</pubDate>
		<guid isPermaLink="false">http://softwaretestinghelp.com/?p=31#comment-42646</guid>
		<description>Its good ..i enjoyed reading this. I will try to incorporate this in my testing....:)</description>
		<content:encoded><![CDATA[<p>Its good ..i enjoyed reading this. I will try to incorporate this in my testing&#8230;.:)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: G.Mallikarjun</title>
		<link>http://www.softwaretestinghelp.com/what-if-there-isnt-enough-time-for-thorough-testing/comment-page-1/#comment-32220</link>
		<dc:creator>G.Mallikarjun</dc:creator>
		<pubDate>Tue, 25 Aug 2009 11:02:41 +0000</pubDate>
		<guid isPermaLink="false">http://softwaretestinghelp.com/?p=31#comment-32220</guid>
		<description>Shivali, plz read this article to get ur answer.
Use risk analysis to determine where testing should be focused.
Since it&#039;s rarely possible to test every possible aspect of an application, every possible combination of events, every dependency, or everything that could go wrong, risk analysis is appropriate to most software development projects. This requires judgement skills, common sense, and experience. (If warranted, formal methods are also available.) Considerations can include: 
• Which functionality is most important to the project&#039;s intended purpose? 
• Which functionality is most visible to the user? 
• Which functionality has the largest safety impact? 
• Which functionality has the largest financial impact on users? 
• Which aspects of the application are most important to the customer? 
• Which aspects of the application can be tested early in the development cycle? 
• Which parts of the code are most complex, and thus most subject to errors? 
• Which parts of the application were developed in rush or panic mode? 
• Which aspects of similar/related previous projects caused problems? 
• Which aspects of similar/related previous projects had large maintenance expenses? 
• Which parts of the requirements and design are unclear or poorly thought out? 
• What do the developers think are the highest-risk aspects of the application? 
• What kinds of problems would cause the worst publicity? 
• What kinds of problems would cause the most customer service complaints? 
• What kinds of tests could easily cover multiple functionalities? 
• Which tests will have the best high-risk-coverage to time-required ratio?</description>
		<content:encoded><![CDATA[<p>Shivali, plz read this article to get ur answer.<br />
Use risk analysis to determine where testing should be focused.<br />
Since it&#8217;s rarely possible to test every possible aspect of an application, every possible combination of events, every dependency, or everything that could go wrong, risk analysis is appropriate to most software development projects. This requires judgement skills, common sense, and experience. (If warranted, formal methods are also available.) Considerations can include:<br />
• Which functionality is most important to the project&#8217;s intended purpose?<br />
• Which functionality is most visible to the user?<br />
• Which functionality has the largest safety impact?<br />
• Which functionality has the largest financial impact on users?<br />
• Which aspects of the application are most important to the customer?<br />
• Which aspects of the application can be tested early in the development cycle?<br />
• Which parts of the code are most complex, and thus most subject to errors?<br />
• Which parts of the application were developed in rush or panic mode?<br />
• Which aspects of similar/related previous projects caused problems?<br />
• Which aspects of similar/related previous projects had large maintenance expenses?<br />
• Which parts of the requirements and design are unclear or poorly thought out?<br />
• What do the developers think are the highest-risk aspects of the application?<br />
• What kinds of problems would cause the worst publicity?<br />
• What kinds of problems would cause the most customer service complaints?<br />
• What kinds of tests could easily cover multiple functionalities?<br />
• Which tests will have the best high-risk-coverage to time-required ratio?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shivali</title>
		<link>http://www.softwaretestinghelp.com/what-if-there-isnt-enough-time-for-thorough-testing/comment-page-1/#comment-32214</link>
		<dc:creator>shivali</dc:creator>
		<pubDate>Tue, 25 Aug 2009 08:57:19 +0000</pubDate>
		<guid isPermaLink="false">http://softwaretestinghelp.com/?p=31#comment-32214</guid>
		<description>Can you please tell me if i can get some projects of software testing which i can do at home?</description>
		<content:encoded><![CDATA[<p>Can you please tell me if i can get some projects of software testing which i can do at home?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jagdish R</title>
		<link>http://www.softwaretestinghelp.com/what-if-there-isnt-enough-time-for-thorough-testing/comment-page-1/#comment-31220</link>
		<dc:creator>Jagdish R</dc:creator>
		<pubDate>Tue, 18 Aug 2009 05:41:16 +0000</pubDate>
		<guid isPermaLink="false">http://softwaretestinghelp.com/?p=31#comment-31220</guid>
		<description>Hi SHivali....

When to stop testing?depends on the below:

1. When all the test cases are exected successfully
2. When the budjet allocation is over
3. When the time/scheduled for testing is met
4.When the delivery date is met to deliver the application</description>
		<content:encoded><![CDATA[<p>Hi SHivali&#8230;.</p>
<p>When to stop testing?depends on the below:</p>
<p>1. When all the test cases are exected successfully<br />
2. When the budjet allocation is over<br />
3. When the time/scheduled for testing is met<br />
4.When the delivery date is met to deliver the application</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shivali</title>
		<link>http://www.softwaretestinghelp.com/what-if-there-isnt-enough-time-for-thorough-testing/comment-page-1/#comment-31218</link>
		<dc:creator>shivali</dc:creator>
		<pubDate>Tue, 18 Aug 2009 05:34:46 +0000</pubDate>
		<guid isPermaLink="false">http://softwaretestinghelp.com/?p=31#comment-31218</guid>
		<description>Can you plz tell me how to prepare and clear ISTQB foundation level paper?</description>
		<content:encoded><![CDATA[<p>Can you plz tell me how to prepare and clear ISTQB foundation level paper?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Raja</title>
		<link>http://www.softwaretestinghelp.com/what-if-there-isnt-enough-time-for-thorough-testing/comment-page-1/#comment-31177</link>
		<dc:creator>Raja</dc:creator>
		<pubDate>Tue, 18 Aug 2009 01:43:10 +0000</pubDate>
		<guid isPermaLink="false">http://softwaretestinghelp.com/?p=31#comment-31177</guid>
		<description>Hi SHIVALI ,

Send me a test mail, i will reply to that mail with testing resume, test cases and some testing white papers.

My mail id:
rajamurugesh.b@gmail.com</description>
		<content:encoded><![CDATA[<p>Hi SHIVALI ,</p>
<p>Send me a test mail, i will reply to that mail with testing resume, test cases and some testing white papers.</p>
<p>My mail id:<br />
<a href="mailto:rajamurugesh.b@gmail.com">rajamurugesh.b@gmail.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SHIVALI</title>
		<link>http://www.softwaretestinghelp.com/what-if-there-isnt-enough-time-for-thorough-testing/comment-page-1/#comment-31087</link>
		<dc:creator>SHIVALI</dc:creator>
		<pubDate>Mon, 17 Aug 2009 10:31:53 +0000</pubDate>
		<guid isPermaLink="false">http://softwaretestinghelp.com/?p=31#comment-31087</guid>
		<description>May i know when to stop testing? Can i get some testing resumes?





Thank you</description>
		<content:encoded><![CDATA[<p>May i know when to stop testing? Can i get some testing resumes?</p>
<p>Thank you</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Raja</title>
		<link>http://www.softwaretestinghelp.com/what-if-there-isnt-enough-time-for-thorough-testing/comment-page-1/#comment-30186</link>
		<dc:creator>Raja</dc:creator>
		<pubDate>Wed, 12 Aug 2009 06:09:36 +0000</pubDate>
		<guid isPermaLink="false">http://softwaretestinghelp.com/?p=31#comment-30186</guid>
		<description>SNo-Objective-Test Case-	Navigation-Inputs-ExpectedOutputs-Test Result (Pass/Fail)

1-aim-steps/procedure-link/event-data-what we except-pass/Fail</description>
		<content:encoded><![CDATA[<p>SNo-Objective-Test Case-	Navigation-Inputs-ExpectedOutputs-Test Result (Pass/Fail)</p>
<p>1-aim-steps/procedure-link/event-data-what we except-pass/Fail</p>
]]></content:encoded>
	</item>
</channel>
</rss>
