<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:media="http://search.yahoo.com/mrss/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0"><channel><title>Software Testing (Manual Methodology)</title><link>http://softwaretestingexpertise.blogspot.com/</link><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/SoftwareTestingExpertise" /><description>Testing Tutorial,Testing Interview Questions, Testing Videos, Test cases Examples ...</description><language>en</language><managingEditor>noreply@blogger.com (Brijesh)</managingEditor><lastBuildDate>Wed, 15 Feb 2012 23:33:55 PST</lastBuildDate><generator>Blogger http://www.blogger.com</generator><openSearch:totalResults xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/">164</openSearch:totalResults><openSearch:startIndex xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/">1</openSearch:startIndex><openSearch:itemsPerPage xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/">25</openSearch:itemsPerPage><feedburner:info uri="softwaretestingexpertise" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><media:category scheme="http://www.itunes.com/dtds/podcast-1.0.dtd">Technology/Software How-To</media:category><itunes:owner><itunes:email>noreply@blogger.com</itunes:email></itunes:owner><itunes:explicit>no</itunes:explicit><itunes:subtitle>Testing Tutorial,Testing Interview Questions, Testing Videos, Test cases Examples ...</itunes:subtitle><itunes:category text="Technology"><itunes:category text="Software How-To" /></itunes:category><creativeCommons:license>http://creativecommons.org/licenses/by-nd/3.0/</creativeCommons:license><image><link>http://creativecommons.org/licenses/by-nd/3.0/</link><url>http://creativecommons.org/images/public/somerights20.gif</url><title>Some Rights Reserved</title></image><feedburner:emailServiceId>SoftwareTestingExpertise</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><feedburner:feedFlare href="http://add.my.yahoo.com/rss?url=http%3A%2F%2Ffeeds.feedburner.com%2FSoftwareTestingExpertise" src="http://us.i1.yimg.com/us.yimg.com/i/us/my/addtomyyahoo4.gif">Subscribe with My Yahoo!</feedburner:feedFlare><feedburner:feedFlare href="http://www.newsgator.com/ngs/subscriber/subext.aspx?url=http%3A%2F%2Ffeeds.feedburner.com%2FSoftwareTestingExpertise" src="http://www.newsgator.com/images/ngsub1.gif">Subscribe with NewsGator</feedburner:feedFlare><feedburner:feedFlare href="http://feeds.my.aol.com/add.jsp?url=http%3A%2F%2Ffeeds.feedburner.com%2FSoftwareTestingExpertise" src="http://o.aolcdn.com/favorites.my.aol.com/webmaster/ffclient/webroot/locale/en-US/images/myAOLButtonSmall.gif">Subscribe with My AOL</feedburner:feedFlare><feedburner:feedFlare href="http://www.bloglines.com/sub/http://feeds.feedburner.com/SoftwareTestingExpertise" src="http://www.bloglines.com/images/sub_modern11.gif">Subscribe with Bloglines</feedburner:feedFlare><feedburner:feedFlare href="http://www.netvibes.com/subscribe.php?url=http%3A%2F%2Ffeeds.feedburner.com%2FSoftwareTestingExpertise" src="http://www.netvibes.com/img/add2netvibes.gif">Subscribe with Netvibes</feedburner:feedFlare><feedburner:feedFlare href="http://fusion.google.com/add?feedurl=http%3A%2F%2Ffeeds.feedburner.com%2FSoftwareTestingExpertise" src="http://buttons.googlesyndication.com/fusion/add.gif">Subscribe with Google</feedburner:feedFlare><feedburner:feedFlare href="http://www.pageflakes.com/subscribe.aspx?url=http%3A%2F%2Ffeeds.feedburner.com%2FSoftwareTestingExpertise" src="http://www.pageflakes.com/ImageFile.ashx?instanceId=Static_4&amp;fileName=ATP_blu_91x17.gif">Subscribe with Pageflakes</feedburner:feedFlare><feedburner:feedFlare href="http://www.plusmo.com/add?url=http%3A%2F%2Ffeeds.feedburner.com%2FSoftwareTestingExpertise" src="http://plusmo.com/res/graphics/fbplusmo.gif">Subscribe with Plusmo</feedburner:feedFlare><feedburner:feedFlare href="http://www.thefreedictionary.com/_/hp/AddRSS.aspx?http%3A%2F%2Ffeeds.feedburner.com%2FSoftwareTestingExpertise" src="http://img.tfd.com/hp/addToTheFreeDictionary.gif">Subscribe with The Free Dictionary</feedburner:feedFlare><feedburner:feedFlare href="http://www.bitty.com/manual/?contenttype=rssfeed&amp;contentvalue=http%3A%2F%2Ffeeds.feedburner.com%2FSoftwareTestingExpertise" src="http://www.bitty.com/img/bittychicklet_91x17.gif">Subscribe with Bitty Browser</feedburner:feedFlare><feedburner:feedFlare href="http://www.newsalloy.com/?rss=http%3A%2F%2Ffeeds.feedburner.com%2FSoftwareTestingExpertise" src="http://www.newsalloy.com/subrss3.gif">Subscribe with NewsAlloy</feedburner:feedFlare><feedburner:feedFlare href="http://www.live.com/?add=http%3A%2F%2Ffeeds.feedburner.com%2FSoftwareTestingExpertise" src="http://tkfiles.storage.msn.com/x1piYkpqHC_35nIp1gLE68-wvzLZO8iXl_JMledmJQXP-XTBOLfmQv4zhj4MhcWEJh_GtoBIiAl1Mjh-ndp9k47If7hTaFno0mxW9_i3p_5qQw">Subscribe with Live.com</feedburner:feedFlare><feedburner:feedFlare href="http://mix.excite.eu/add?feedurl=http%3A%2F%2Ffeeds.feedburner.com%2FSoftwareTestingExpertise" src="http://image.excite.co.uk/mix/addtomix.gif">Subscribe with Excite MIX</feedburner:feedFlare><feedburner:feedFlare href="http://download.attensa.com/app/get_attensa.html?feedurl=http%3A%2F%2Ffeeds.feedburner.com%2FSoftwareTestingExpertise" src="http://www.attensa.com/blogs/attensa/WindowsLiveWriter/BadgeredintoBadges_10C02/attensa_feed_button5.gif">Subscribe with Attensa for Outlook</feedburner:feedFlare><feedburner:feedFlare href="http://www.webwag.com/wwgthis.php?url=http%3A%2F%2Ffeeds.feedburner.com%2FSoftwareTestingExpertise" src="http://www.webwag.com/images/wwgthis.gif">Subscribe with Webwag</feedburner:feedFlare><feedburner:feedFlare href="http://www.podcastready.com/oneclick_bookmark.php?url=http%3A%2F%2Ffeeds.feedburner.com%2FSoftwareTestingExpertise" src="http://www.podcastready.com/images/podcastready_button.gif">Subscribe with Podcast Ready</feedburner:feedFlare><feedburner:feedFlare href="http://www.flurry.com/pushRssFeed.do?r=fb&amp;url=http%3A%2F%2Ffeeds.feedburner.com%2FSoftwareTestingExpertise" src="http://www.flurry.com/images/flurry_rss_logo2.gif">Subscribe with Flurry</feedburner:feedFlare><feedburner:feedFlare href="http://www.wikio.com/subscribe?url=http%3A%2F%2Ffeeds.feedburner.com%2FSoftwareTestingExpertise" src="http://www.wikio.com/shared/img/add2wikio.gif">Subscribe with Wikio</feedburner:feedFlare><feedburner:feedFlare href="http://www.dailyrotation.com/index.php?feed=http%3A%2F%2Ffeeds.feedburner.com%2FSoftwareTestingExpertise" src="http://www.dailyrotation.com/rss-dr2.gif">Subscribe with Daily Rotation</feedburner:feedFlare><item><title>Unit Testing</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/1gcmvUVlHOg/unit-testing.html</link><category>Unit Testing</category><category>Software Testing</category><author>noreply@blogger.com (Brijesh)</author><pubDate>Sun, 25 Dec 2011 09:32:00 PST</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-3777992857867373782</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-25T23:02:00.247+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>The Objective of the Unit testing is to ensure the steps to be
followed to confirm that it meets the functional requirements as specified in
Program Specifications.



This procedure covers: 



Testing of the user interface to ensure that
     information properly flows into and out of the program unit under testing. 
Examine the local data structure
     to ensure that data stored temporarily...
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/Oou0n5LPAhjxXzzR1t_LtwwOAfY/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Oou0n5LPAhjxXzzR1t_LtwwOAfY/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/Oou0n5LPAhjxXzzR1t_LtwwOAfY/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Oou0n5LPAhjxXzzR1t_LtwwOAfY/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=1gcmvUVlHOg:3LqTYqKBweo:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=1gcmvUVlHOg:3LqTYqKBweo:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=1gcmvUVlHOg:3LqTYqKBweo:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/1gcmvUVlHOg" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2011/12/unit-testing.html</feedburner:origLink></item><item><title>Test Case Creation</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/Eh5g33vQ9IM/test-case-creation.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Tue, 20 Dec 2011 06:57:35 PST</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-6412656497447743250</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-20T20:27:35.326+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Test cases are designed using test techniques as identified in test strategy. Test cases should be designed by stepwise elaboration of test condition. Test design includes identification of preconditions, test data requirement, expected result and post conditions.



Each test case should be:





-&amp;gt; Repeatable

-&amp;gt; Verifiable

-&amp;gt; Traceable back to...
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/Fd0bxddBWaLI346AJD5oF25XNw4/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Fd0bxddBWaLI346AJD5oF25XNw4/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/Fd0bxddBWaLI346AJD5oF25XNw4/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Fd0bxddBWaLI346AJD5oF25XNw4/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=Eh5g33vQ9IM:s3_hnrWxiZ4:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=Eh5g33vQ9IM:s3_hnrWxiZ4:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=Eh5g33vQ9IM:s3_hnrWxiZ4:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/Eh5g33vQ9IM" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2011/07/test-case-creation.html</feedburner:origLink></item><item><title>How to report a defect having no test case in SIT?</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/Anph72VOtSI/how-to-report-defect-having-to-test.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Thu, 22 Dec 2011 01:58:37 PST</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-6159712437156108632</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-22T15:28:37.119+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>Hi Friends,



Sometimes during testing or I will say during execution of an existing SIT, it happens that a tester get a defect for which no test cases is mentioned in SIT. Then what we tester should do? Tester should not report the bug or should report it?



Let me clarify these questions. Tester should report every bug he/she get during testing. Tester should clearly mentioned the 'Steps to...
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/xQeroyYd_xHMst4H7A0WZwS2gHo/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/xQeroyYd_xHMst4H7A0WZwS2gHo/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/xQeroyYd_xHMst4H7A0WZwS2gHo/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/xQeroyYd_xHMst4H7A0WZwS2gHo/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=Anph72VOtSI:H7aOCX9TSuA:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=Anph72VOtSI:H7aOCX9TSuA:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=Anph72VOtSI:H7aOCX9TSuA:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/Anph72VOtSI" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2011/12/how-to-report-defect-having-to-test.html</feedburner:origLink></item><item><title>Software Testing Process</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/JBfAcc8TTXQ/software-testing-process.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Tue, 20 Dec 2011 06:48:19 PST</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-7631586183878923582</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-20T20:18:19.486+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/CnvkgWEC2rDw8D40O5cc_HKe5vA/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/CnvkgWEC2rDw8D40O5cc_HKe5vA/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/CnvkgWEC2rDw8D40O5cc_HKe5vA/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/CnvkgWEC2rDw8D40O5cc_HKe5vA/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=JBfAcc8TTXQ:pm23sga6Iv4:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=JBfAcc8TTXQ:pm23sga6Iv4:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=JBfAcc8TTXQ:pm23sga6Iv4:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/JBfAcc8TTXQ" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2011/12/software-testing-process.html</feedburner:origLink></item><item><title>Software Test Design</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/S8AWs8Fs5GE/software.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Sat, 17 Dec 2011 02:40:18 PST</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-4713441442142845843</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-17T16:10:18.798+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>Software Test design



Once the test plan for a level of testing has been written, the next 
stage is to specify a set of test cases for each item to 
be tested at that level. A number of test cases will be identified for 
each item to be tested at each level of testing.



Each test case will specify how the implementation of a particular 
requirement or design is to be tested, what will be the...
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/svwKRKKpIvijTtvzEE-BV2ne1qI/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/svwKRKKpIvijTtvzEE-BV2ne1qI/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/svwKRKKpIvijTtvzEE-BV2ne1qI/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/svwKRKKpIvijTtvzEE-BV2ne1qI/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=S8AWs8Fs5GE:16QCq9j0gPU:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=S8AWs8Fs5GE:16QCq9j0gPU:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=S8AWs8Fs5GE:16QCq9j0gPU:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/S8AWs8Fs5GE" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2011/12/software.html</feedburner:origLink></item><item><title>When you start software testing, remember ...</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/ZdHoT0Gzrvk/when-you-start-software-testing.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Wed, 14 Dec 2011 08:02:22 PST</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-4634889534380345178</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-14T21:32:22.687+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>1) All tests should be traceable to requirements.

Use
 requirement traceability matrix to trace test cases which you need to 
execute when do testing. It will give you confidence that all 
requirements have been covered.




2) Remember pareto principle – 80% defects are in 20% code.

So, 
drill down the module/page/feature more and more, where you found even a
 single bug. Don't stop testing...
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/HwJAiFQZW_fb1AXKi1TcUUgkXH0/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/HwJAiFQZW_fb1AXKi1TcUUgkXH0/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/HwJAiFQZW_fb1AXKi1TcUUgkXH0/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/HwJAiFQZW_fb1AXKi1TcUUgkXH0/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=ZdHoT0Gzrvk:PCW5Bycwuks:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=ZdHoT0Gzrvk:PCW5Bycwuks:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=ZdHoT0Gzrvk:PCW5Bycwuks:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/ZdHoT0Gzrvk" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2011/12/when-you-start-software-testing.html</feedburner:origLink></item><item><title>What about bugs found in application post delivery at developer/tester end?</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/0eiKdO1KbiQ/what-about-bugs-found-in-application.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Sat, 10 Dec 2011 00:36:47 PST</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-7177457874868444260</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-10T14:06:47.053+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>Hi Friends,



How are you? It's long time when I am posting this post. Sorry for that actually I was very active on internet due to time constraints. Here I am again with one more experience. Why experience, because I always try to post only that material on my blog which actually I have faced.



I am sure if if any you have worked on a project, where you replaced an existing tester, you have...
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/njslt28ggE6juRb8icocufCdeY0/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/njslt28ggE6juRb8icocufCdeY0/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/njslt28ggE6juRb8icocufCdeY0/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/njslt28ggE6juRb8icocufCdeY0/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=0eiKdO1KbiQ:cdmT0s_-yew:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=0eiKdO1KbiQ:cdmT0s_-yew:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=0eiKdO1KbiQ:cdmT0s_-yew:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/0eiKdO1KbiQ" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2011/12/what-about-bugs-found-in-application.html</feedburner:origLink></item><item><title>User Acceptance Testing</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/iJSYDhpqQow/user-acceptance-testing.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Mon, 13 Dec 2010 20:00:38 PST</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-6340905516907090991</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2010-12-14T09:30:38.910+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>UAT testing and test cases are generally sub set of system testing. If you have done your system testing faithfully then you need not to worry about UAT, still the functionality and test cases demanded in UAT should pass for maintain your golden customer.

Why we have UAT when we have completed the system testing is a good question.

Actually what so ever we test in Unit testing, Integration...
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/X5g1dusq4pKin727um6fuEGwc34/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/X5g1dusq4pKin727um6fuEGwc34/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/X5g1dusq4pKin727um6fuEGwc34/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/X5g1dusq4pKin727um6fuEGwc34/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=iJSYDhpqQow:-gKegriG83g:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=iJSYDhpqQow:-gKegriG83g:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=iJSYDhpqQow:-gKegriG83g:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/iJSYDhpqQow" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2010/12/user-acceptance-testing.html</feedburner:origLink></item><item><title>Why we need testing?</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/SkQ6i5P8kO8/why-we-need-testing.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Sat, 11 Dec 2010 22:30:39 PST</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-855398052563096390</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2010-12-12T12:00:39.182+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><description>Why we need testing?
Is it to find bugs?ORIs it to prove that software have issues?
Actually the common need of testing is not only to prove that software have issues or to uncover bugs only. What really testing does is very important question. Let we take an example.
Today laser surgery for removing glasses is very common, but if you have to go for it, how you will be sure that it will OK for...
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/0ek33N9bwqB81p2Cr6lPm2r6CF0/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/0ek33N9bwqB81p2Cr6lPm2r6CF0/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/0ek33N9bwqB81p2Cr6lPm2r6CF0/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/0ek33N9bwqB81p2Cr6lPm2r6CF0/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=SkQ6i5P8kO8:bH4QAhBFaVE:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=SkQ6i5P8kO8:bH4QAhBFaVE:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=SkQ6i5P8kO8:bH4QAhBFaVE:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/SkQ6i5P8kO8" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2010/12/why-we-need-testing.html</feedburner:origLink></item><item><title>Different Test Plan</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/jrFqDf75btw/different-test-plan.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Sat, 11 Dec 2010 01:49:55 PST</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-6912039358691761090</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2010-12-11T15:19:55.930+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>What are the different Test Plan?





A test plan is created at each level of testing.



If we are doing Unit testing then that will be done against Unit test plan.



If we are doing Integration testing then that will be done against Integration test plan.



If we are doing System testing then that will be done against System test plan.



And above all is master test plan that is&amp;nbsp;...
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/ZL7XrG1BtIKewXpFsPYQAqmG0uY/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ZL7XrG1BtIKewXpFsPYQAqmG0uY/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/ZL7XrG1BtIKewXpFsPYQAqmG0uY/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ZL7XrG1BtIKewXpFsPYQAqmG0uY/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=jrFqDf75btw:r3V4yISvRX8:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=jrFqDf75btw:r3V4yISvRX8:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=jrFqDf75btw:r3V4yISvRX8:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/jrFqDf75btw" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2010/12/different-test-plan.html</feedburner:origLink></item><item><title>State transition test case writing technique</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/Irw1_VFaUIY/state-transition-test-case-writing.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Thu, 12 Aug 2010 05:45:08 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-1432163378918768697</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2010-08-12T18:15:08.463+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>Hi,
Today We will discuss about &amp;quot;State transition test case writing technique&amp;quot;.   
Actually When we have to test something we need to write test cases and to to write test cases we need to follow some technique. Most general testing techniques are:   
1) Equivalence class partitioning   2) Boundary Value analysis3) Error Guessing   
One more is &amp;#39;State transition test case...
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/KffutmuVH9RIQmZY-fEBL4RAXzA/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/KffutmuVH9RIQmZY-fEBL4RAXzA/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/KffutmuVH9RIQmZY-fEBL4RAXzA/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/KffutmuVH9RIQmZY-fEBL4RAXzA/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=Irw1_VFaUIY:yjGChRRj28g:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=Irw1_VFaUIY:yjGChRRj28g:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=Irw1_VFaUIY:yjGChRRj28g:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/Irw1_VFaUIY" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2010/08/state-transition-test-case-writing.html</feedburner:origLink></item><item><title>Example to explain how developer environment and production  environment could be different</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/ViKm7eUeSPs/example-to-explain-how-developer.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Thu, 08 Jul 2010 23:10:23 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-5917360107338047459</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2010-07-09T11:40:23.790+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>Hi,
An example to explain how developer environment and production environment could be different:
The best example is web application. Most of the companies are using opensource tools now. So, it may be case that developer m/c is Linux m/c not windows. But this website can be accessed by a user having window m/c or even mac m/c. After all web is open for all. Other example could be developers...
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/IwZdPnyMNxZrcfO_lBnCEfmEgc8/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/IwZdPnyMNxZrcfO_lBnCEfmEgc8/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/IwZdPnyMNxZrcfO_lBnCEfmEgc8/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/IwZdPnyMNxZrcfO_lBnCEfmEgc8/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=ViKm7eUeSPs:jX3AIESt5kA:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=ViKm7eUeSPs:jX3AIESt5kA:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=ViKm7eUeSPs:jX3AIESt5kA:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/ViKm7eUeSPs" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2010/07/example-to-explain-how-developer.html</feedburner:origLink></item><item><title>Always test error messages</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/6N8UIpNDOY8/always-test-error-messages.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Mon, 19 Apr 2010 23:35:47 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-2491180981850123382</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2010-04-20T12:05:47.416+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>Error messages are generally othere type of help for the users which provided to them when they mistakes. After all we are here to help users. We guide them before using application, we guide them after doing mistakes. So, always test for error message (help).  It&amp;#39;s  also very difficult for testers to find and display all the error messages but if you will try all combination of test cases...
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/y6LswOWqEVPo9CegPo8F_n_cFNs/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/y6LswOWqEVPo9CegPo8F_n_cFNs/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/y6LswOWqEVPo9CegPo8F_n_cFNs/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/y6LswOWqEVPo9CegPo8F_n_cFNs/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=6N8UIpNDOY8:KuTAmHpciiU:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=6N8UIpNDOY8:KuTAmHpciiU:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=6N8UIpNDOY8:KuTAmHpciiU:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/6N8UIpNDOY8" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2010/04/always-test-error-messages.html</feedburner:origLink></item><item><title>When I completed testing with PayPal</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/ryzyutAauwI/when-i-completed-testing-with-paypal.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Fri, 12 Mar 2010 04:24:12 PST</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-680106963676919664</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2010-03-12T17:54:12.072+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total><description>Hi,

I have posted my earlier posts related to PayPal, because currently I was involved in integration testing of PayPal with my project cart module. I am not explaining here what Issues I got in my application or what was my test cases. But I want to say that when you do test, you can&amp;#39;t sure that PayPal is working 100% fine, because no software is 100% bug free :) I am here going to prove...
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/xx-gIMFb7qi49LkYKCuCfIK1jbI/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/xx-gIMFb7qi49LkYKCuCfIK1jbI/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/xx-gIMFb7qi49LkYKCuCfIK1jbI/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/xx-gIMFb7qi49LkYKCuCfIK1jbI/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=ryzyutAauwI:tahiJ9RaZX8:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=ryzyutAauwI:tahiJ9RaZX8:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=ryzyutAauwI:tahiJ9RaZX8:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/ryzyutAauwI" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2010/03/when-i-completed-testing-with-paypal.html</feedburner:origLink></item><item><title>Testing with test card for order payments</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/9Lpg3CqDVG4/testing-with-test-card-for-order.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Tue, 09 Mar 2010 22:52:09 PST</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-481418264258649550</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2010-03-10T12:22:09.281+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>Hi,

I get a real scenario when we can say that we can&amp;#39;t believe on test results using test card numbers. I was doing testing of my application order process module with payment gateway PayPal integration. The test card I used for payment on my test server give me a test pass result for a scenario when user place an order and use Gift card also during checkout, but the same scenario fails...
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/hB9LVrbO0WoC5NIdfg_47JQ08_c/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/hB9LVrbO0WoC5NIdfg_47JQ08_c/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/hB9LVrbO0WoC5NIdfg_47JQ08_c/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/hB9LVrbO0WoC5NIdfg_47JQ08_c/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=9Lpg3CqDVG4:xYrfFwO-Cnw:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=9Lpg3CqDVG4:xYrfFwO-Cnw:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=9Lpg3CqDVG4:xYrfFwO-Cnw:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/9Lpg3CqDVG4" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2010/03/testing-with-test-card-for-order.html</feedburner:origLink></item><item><title>If you are doing website testing</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/7sCTSnSls2U/if-you-are-doing-website-testing.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Mon, 22 Feb 2010 22:14:01 PST</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-8193940965936310430</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2010-02-23T11:44:01.573+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>Hi,

   Web page is a complex entity. A web page is made of html, scripts, CSS, images and many more things. When a developer fix any issue or update the build, you may see the UI is same but don&amp;#39;t know which script or CSS etc has been changed. So, make it a habit when doing testing/re-testing on web page, always reset your browser. If you are doing automation it is must do thing for better...
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/_4rrvwJiXa497wzH-RAPzu8Lt4Q/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/_4rrvwJiXa497wzH-RAPzu8Lt4Q/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/_4rrvwJiXa497wzH-RAPzu8Lt4Q/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/_4rrvwJiXa497wzH-RAPzu8Lt4Q/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=7sCTSnSls2U:eVL4pjoDfgM:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=7sCTSnSls2U:eVL4pjoDfgM:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=7sCTSnSls2U:eVL4pjoDfgM:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/7sCTSnSls2U" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2010/02/if-you-are-doing-website-testing.html</feedburner:origLink></item><item><title>Test cases for payment gateway</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/E-ht6iOjw5g/test-cases-for-payment-gateway.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Thu, 21 Jan 2010 04:05:43 PST</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-6510857714976559352</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2010-01-21T17:35:43.167+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>Test cases for payment gateway:

My example is PayPal manager based:-

1) Test with valid card number with valid expiry but invalid CVV.
2) Test with valid card number with invalid expiry but valid CVV.
3) Test with valid card number with invalid expiry and CVV.
 4) Test with  valid details of expired/blocked card.
5) Test with valid card number, CVV and expiry date.
6) Test for reference...
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/G_aTn1d6RE2VvilgmhJzXj_EaJ4/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/G_aTn1d6RE2VvilgmhJzXj_EaJ4/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/G_aTn1d6RE2VvilgmhJzXj_EaJ4/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/G_aTn1d6RE2VvilgmhJzXj_EaJ4/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=E-ht6iOjw5g:HN9Y-SpmndU:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=E-ht6iOjw5g:HN9Y-SpmndU:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=E-ht6iOjw5g:HN9Y-SpmndU:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/E-ht6iOjw5g" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2010/01/test-cases-for-payment-gateway.html</feedburner:origLink></item><item><title>When testing any application admin/backend module</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/lp7kumpdf4o/when-testing-any-application.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Fri, 15 Jan 2010 04:01:36 PST</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-3790608467158355230</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2010-01-15T17:31:36.881+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>Hi,

Whenever you get chance for  testing any web application admin/backend module and there is any option for disabling users, then always test for admin active/disable link.

Either you application should be under control of superadmin user or there should no link to disable admin user.
 
I have faced it during my project testing and my first case was same and as expected, &amp;quot;Backend...
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/hAn8Kb0Mj2VYSIxGOUSnaF7hvR8/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/hAn8Kb0Mj2VYSIxGOUSnaF7hvR8/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/hAn8Kb0Mj2VYSIxGOUSnaF7hvR8/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/hAn8Kb0Mj2VYSIxGOUSnaF7hvR8/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=lp7kumpdf4o:u2Y-sRkVJV4:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=lp7kumpdf4o:u2Y-sRkVJV4:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=lp7kumpdf4o:u2Y-sRkVJV4:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/lp7kumpdf4o" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2010/01/when-testing-any-application.html</feedburner:origLink></item><item><title>Real Testing - Real Experience(2)</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/9zHiwXcjQzY/2-real-testing-real-experience.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Sat, 10 Dec 2011 00:38:58 PST</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-5744411229047495637</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-10T14:08:58.412+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>Hi,



Another one real experience shared.



Definitely you all have tested registration/login module, if you have tested any web application. How many of you have tested the "login redirection" when user is already logged in, from login page?



Always test it and it should redirected.



Thanks.



Friends, why don't you share your such experience as comments for this post? I hope you will,...
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/h75XpMs2dp_CrxfpNR_K9wPAl3c/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/h75XpMs2dp_CrxfpNR_K9wPAl3c/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/h75XpMs2dp_CrxfpNR_K9wPAl3c/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/h75XpMs2dp_CrxfpNR_K9wPAl3c/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=9zHiwXcjQzY:zgC6iiDCIdA:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=9zHiwXcjQzY:zgC6iiDCIdA:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=9zHiwXcjQzY:zgC6iiDCIdA:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/9zHiwXcjQzY" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2009/11/2-real-testing-real-experience.html</feedburner:origLink></item><item><title>Real Testing - Real Experience</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/Y6-7NrnbXdU/real-testing-real-experience.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Wed, 04 Nov 2009 01:09:52 PST</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-2885701886676054538</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2009-11-04T14:39:52.981+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>Hi,

    Sometimes candidates are asked for some real time bugs you face when did testing of your project. So, here I am giving you an example that you can use as a test case also as well as your answer for the interviewer question.
     
  When testing terms and condition page, usually there should be a &amp;quot;print&amp;quot; button/link to print terms and conditions agreement. Always test it with...
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/ShGGpfKIBVQC0y29CcXaMKcGLro/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ShGGpfKIBVQC0y29CcXaMKcGLro/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/ShGGpfKIBVQC0y29CcXaMKcGLro/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ShGGpfKIBVQC0y29CcXaMKcGLro/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=Y6-7NrnbXdU:ZYmuBPlcBd4:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=Y6-7NrnbXdU:ZYmuBPlcBd4:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=Y6-7NrnbXdU:ZYmuBPlcBd4:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/Y6-7NrnbXdU" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2009/11/real-testing-real-experience.html</feedburner:origLink></item><item><title>Bug of the Month</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/MUYLl9qdPIA/bug-of-month.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Thu, 29 Oct 2009 22:05:38 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-1134108136116867631</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-30T10:35:38.858+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>&amp;nbsp;&amp;nbsp; 'Known Software Bug' Disrupts Brain-Tumor Zapping: The maker of a life-saving radiation therapy device has patched a software bug that could cause the system's emergency stop button to fail to stop, following an incident at a Cleveland hospital in which medical staff had to physically pull a patient from the maw of the machine. (Thanks to Wired)

Source:-...
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/XsiX60jLGjxGjbCNewqjc5irj_4/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/XsiX60jLGjxGjbCNewqjc5irj_4/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/XsiX60jLGjxGjbCNewqjc5irj_4/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/XsiX60jLGjxGjbCNewqjc5irj_4/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=MUYLl9qdPIA:DuFs2McA1sc:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=MUYLl9qdPIA:DuFs2McA1sc:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=MUYLl9qdPIA:DuFs2McA1sc:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/MUYLl9qdPIA" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2009/10/bug-of-month.html</feedburner:origLink></item><item><title>How and Why to Clear Your Cache?</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/95o5VgtmUlk/how-and-why-to-clear-your-cache.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Wed, 28 Oct 2009 02:46:53 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-3947154725631493896</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-28T15:16:53.686+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>Often referred to as the cache, the Temporary Internet Files folder contains a kind of travel record of the items you have seen, heard, or downloaded from the Web, including images, sounds, Web pages, even cookies. Typically these items are stored in the Temporary Internet Files folder.

Storing these files in your cache can make browsing the Web faster because it usually takes your computer less...
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/D-dcOKKG_SIFmqp0IJhWLL2MhnM/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/D-dcOKKG_SIFmqp0IJhWLL2MhnM/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/D-dcOKKG_SIFmqp0IJhWLL2MhnM/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/D-dcOKKG_SIFmqp0IJhWLL2MhnM/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=95o5VgtmUlk:zB0wdlp5Si4:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=95o5VgtmUlk:zB0wdlp5Si4:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=95o5VgtmUlk:zB0wdlp5Si4:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/95o5VgtmUlk" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2009/10/how-and-why-to-clear-your-cache.html</feedburner:origLink></item><item><title>objective questions with answer</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/o6uh-RhMO54/objective-questions-with-answer.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Tue, 27 Oct 2009 21:50:56 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-2616860230840812369</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-28T10:20:56.380+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>(1) Which of the following is not one of the techniques to find defects
a)	Operational Techniques
b)	Functional Techniques
c)	Dynamic Techniques
d)	Static Techniques

Ans: a

 (2) Quality Assurance methods are usually considered
a)	Detective
b)	Corrective
c)	Preventive
d)	Proactive

Ans: c
 
(3) Who has the primary responsibility of setting the quality culture in the organization?
a)	Senior...
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/E9Ykht2WQOC_8EWYeUf9YmOttHg/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/E9Ykht2WQOC_8EWYeUf9YmOttHg/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/E9Ykht2WQOC_8EWYeUf9YmOttHg/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/E9Ykht2WQOC_8EWYeUf9YmOttHg/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=o6uh-RhMO54:7SRHfwyOiQg:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=o6uh-RhMO54:7SRHfwyOiQg:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=o6uh-RhMO54:7SRHfwyOiQg:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/o6uh-RhMO54" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2009/10/objective-questions-with-answer.html</feedburner:origLink></item><item><title>What is a GUI Prototype?</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/q2j2J6noDBU/what-is-gui-prototype.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Tue, 27 Oct 2009 00:29:29 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-2517120238031596564</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-27T12:59:29.735+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>   A GUI (Graphical User Interface) prototype is nothing but an initial design built during the Design Phase. It may be a small program consisting of just the main screens (functions are not implemented only how it would appear is done, &amp;quot;Back&amp;quot;, &amp;quot;Next&amp;quot; , &amp;quot;Submit&amp;quot; etc buttons may work for navigation purpose only). After the client approval of the screens (the GUI) they...
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/aRmGN75xgem3zXAr10PvaudHyig/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/aRmGN75xgem3zXAr10PvaudHyig/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/aRmGN75xgem3zXAr10PvaudHyig/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/aRmGN75xgem3zXAr10PvaudHyig/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=q2j2J6noDBU:quzWWup7cy0:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=q2j2J6noDBU:quzWWup7cy0:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=q2j2J6noDBU:quzWWup7cy0:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/q2j2J6noDBU" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2009/10/what-is-gui-prototype.html</feedburner:origLink></item><item><title>Is accessibility testing different from GUI testing ?</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/RPLicWFzII8/is-accessibility-testing-different-from.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Fri, 16 Oct 2009 04:56:02 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-6014778152158020778</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-16T17:26:02.884+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>Yes,

Accessibility testing is different from GUI testing.

GUI testing: Test for Graphical user interface. How site looks? Test for site design in all browsers, design should not corrupts.

Accessibility testing: Test for how site is usable for partial or complete disabled persons. For example: if a user has eye problem, weak sight. Then is there any hearing feature for  words displayed on...
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/BXc_5E4Y51Z9FBNZuYBVhZ4PIsc/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/BXc_5E4Y51Z9FBNZuYBVhZ4PIsc/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/BXc_5E4Y51Z9FBNZuYBVhZ4PIsc/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/BXc_5E4Y51Z9FBNZuYBVhZ4PIsc/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=RPLicWFzII8:80mbtlzz3nM:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=RPLicWFzII8:80mbtlzz3nM:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?a=RPLicWFzII8:80mbtlzz3nM:qj6IDK7rITs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=qj6IDK7rITs" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/RPLicWFzII8" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2009/10/is-accessibility-testing-different-from.html</feedburner:origLink></item><media:rating>nonadult</media:rating></channel></rss>

