<?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:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0"><channel><title>Software Testing</title><link>http://softwaretestingexpertise.blogspot.com/</link><description>Testing Tutorial,Interview Questions, Video, Test cases ...</description><language>en</language><managingEditor>noreply@blogger.com (Brijesh)</managingEditor><lastBuildDate>Tue, 10 Nov 2009 00:50:41 PST</lastBuildDate><generator>Blogger http://www.blogger.com</generator><openSearch:totalResults xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/">155</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><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/SoftwareTestingExpertise" type="application/rss+xml" /><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><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><item><title>2- Real Testing - Real Experience</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/9zHiwXcjQzY/2-real-testing-real-experience.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Wed, 04 Nov 2009 22:31:53 PST</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-5744411229047495637</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2009-11-05T12:01:53.516+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, please comment.
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/Hd4tpm4s0sC9QDDgedhh0hjjcQI/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Hd4tpm4s0sC9QDDgedhh0hjjcQI/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/Hd4tpm4s0sC9QDDgedhh0hjjcQI/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Hd4tpm4s0sC9QDDgedhh0hjjcQI/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;/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 "print" button/link to print terms and conditions agreement. Always test it with printer. As a
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/nqu-SLIAY68GfGUGOZKrUooCpEo/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/nqu-SLIAY68GfGUGOZKrUooCpEo/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/nqu-SLIAY68GfGUGOZKrUooCpEo/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/nqu-SLIAY68GfGUGOZKrUooCpEo/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;/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>   '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:- http://www.wired.com/threatlevel/2009/
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/CJR9duNtHtRIeGkXnskc5xLP-zY/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/CJR9duNtHtRIeGkXnskc5xLP-zY/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/CJR9duNtHtRIeGkXnskc5xLP-zY/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/CJR9duNtHtRIeGkXnskc5xLP-zY/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;/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/peOH8juAb-ieq8mV7f-MK_YbP7U/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/peOH8juAb-ieq8mV7f-MK_YbP7U/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/peOH8juAb-ieq8mV7f-MK_YbP7U/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/peOH8juAb-ieq8mV7f-MK_YbP7U/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;/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 defectsa)	Operational Techniquesb)	Functional Techniquesc)	Dynamic Techniquesd)	Static TechniquesAns: a (2) Quality Assurance methods are usually considereda)	Detectiveb)	Correctivec)	Preventived)	ProactiveAns: c (3) Who has the primary responsibility of setting the quality culture in the organization?a)	Senior Managementb)	The
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/_Ise8pN7OtsqXFLUwKPC_-hC7Xo/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/_Ise8pN7OtsqXFLUwKPC_-hC7Xo/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/_Ise8pN7OtsqXFLUwKPC_-hC7Xo/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/_Ise8pN7OtsqXFLUwKPC_-hC7Xo/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;/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, "Back", "Next" , "Submit" etc buttons may work for navigation purpose only). After the client approval of the screens (the GUI) they are finalized. Then starts
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/KwqUVJmPWaHjFQlZFAkzsdPIWLw/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/KwqUVJmPWaHjFQlZFAkzsdPIWLw/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/KwqUVJmPWaHjFQlZFAkzsdPIWLw/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/KwqUVJmPWaHjFQlZFAkzsdPIWLw/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;/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 site. I
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/QpFlsqOyffSrunBpEOrnehZ54is/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/QpFlsqOyffSrunBpEOrnehZ54is/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/QpFlsqOyffSrunBpEOrnehZ54is/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/QpFlsqOyffSrunBpEOrnehZ54is/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;/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><item><title>Difference between test case and test scenario</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/GZCTu4S9fz4/difference-between-test-case-and-test.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Tue, 13 Oct 2009 22:02:44 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-8472491992217121222</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-14T10:32:44.763+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><description>Test case is a condition which is executed for expected output with predefined set of steps with known inputs. Generally a test case have1) Precondition2) Steps to execute3) Input data4) Expected output 5) Status (Pass/Fail)Test Scenario is set of test cases. What it means, If you have to withdraw money from an ATM machine, then it is a scenario. But to withdraw money, you need to execute many
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/mwkFZM8d4JBfLy_jTR9U3_NXZ18/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/mwkFZM8d4JBfLy_jTR9U3_NXZ18/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/mwkFZM8d4JBfLy_jTR9U3_NXZ18/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/mwkFZM8d4JBfLy_jTR9U3_NXZ18/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=GZCTu4S9fz4:xGFOeD-Dozo:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/GZCTu4S9fz4" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2009/10/difference-between-test-case-and-test.html</feedburner:origLink></item><item><title>How to log a defect?</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/4mINZozIo68/how-to-log-defect.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Mon, 12 Oct 2009 23:05:09 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-8744454468549780123</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-13T11:35:09.372+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total><description>How to log a defect?I have used 4 defect/bug tracking tools which are:1) Microsoft VSTS2) Bugzilla3) Mantis4) RedmineAS per my experience, what I found common and most valuable thing in bug reporting are:  1) Defect title2) Defect Summary3) Defect description ( Steps to reproduce)4) Severity5) Screenshot if any.
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/pedaimuHLkXjyKKGQQnVfDVO0n8/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/pedaimuHLkXjyKKGQQnVfDVO0n8/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/pedaimuHLkXjyKKGQQnVfDVO0n8/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/pedaimuHLkXjyKKGQQnVfDVO0n8/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=4mINZozIo68:hWSDmyR7_WE:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/4mINZozIo68" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2009/10/how-to-log-defect.html</feedburner:origLink></item><item><title>Test cases for Lift</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/nUfv4RVxDMk/test-cases-for-lift.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Mon, 12 Oct 2009 05:18:21 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-4371118191488764491</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-12T17:48:21.198+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>Hi,Lift are always as per requiremnts. So, It will not better to start with test cases without requirements.Here I am taking the simplest example of metro rail lift used to get from Ticket floor (TF) to Platform floor (PF). Requirement is passanger should able to use lift to go and come back from Ticket floor to platform floor. Precondition is passanger is on TF. 1) When light is on for the lift
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/rPX9ftSVLnG10A1u8qOPK76nvew/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/rPX9ftSVLnG10A1u8qOPK76nvew/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/rPX9ftSVLnG10A1u8qOPK76nvew/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/rPX9ftSVLnG10A1u8qOPK76nvew/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=nUfv4RVxDMk:O50pEB9n0W0:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/nUfv4RVxDMk" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2009/10/test-cases-for-lift.html</feedburner:origLink></item><item><title>How to interact with the developer about the bug?</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/1srdzKAO8Hs/how-to-interact-with-developer-about.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Sun, 11 Oct 2009 22:45:44 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-7214342279640007267</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-12T11:15:44.777+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>How to interact with a developer about the bug is really a gud question that can be asked to any candidate in an interview. Why because, we all as tester reports bug to developers but how many of them get fixed by developers depends on our bug reporting. this is like a stranger ask you about a way and how better we can explain it to that stranger, so that he/she needs not to ask about it to
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/3Z4FzuX6pyirJ-xi_ZYy-bD9Upc/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/3Z4FzuX6pyirJ-xi_ZYy-bD9Upc/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/3Z4FzuX6pyirJ-xi_ZYy-bD9Upc/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/3Z4FzuX6pyirJ-xi_ZYy-bD9Upc/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=1srdzKAO8Hs:9RLXnzMXEVc:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/1srdzKAO8Hs" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2009/10/how-to-interact-with-developer-about.html</feedburner:origLink></item><item><title>Relation b/w Acceptance testing and Beta testing</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/iNC7kOwfOnU/relation-bw-acceptance-testing-and-beta.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Mon, 28 Sep 2009 22:34:12 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-1813365449163876934</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-29T11:04:12.729+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>Can we relate Acceptance testing and Beta testing?Answer may be yes, why ?  Because when we completed the acceptance testing, we release the product for beta testing. Acceptance testing could also be called beta testing (selected users), here they are client and management. Later released for real customers/users.  Am I right? Please comments.
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/A8stUPYdfNMpuYV62xcQES2mvJ0/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/A8stUPYdfNMpuYV62xcQES2mvJ0/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/A8stUPYdfNMpuYV62xcQES2mvJ0/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/A8stUPYdfNMpuYV62xcQES2mvJ0/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=iNC7kOwfOnU:gBp5C00a6Uk:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/iNC7kOwfOnU" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2009/09/relation-bw-acceptance-testing-and-beta.html</feedburner:origLink></item><item><title>Executing the same test case by giving the number of inputs</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/TCeboz_EyWc/executing-same-test-case-by-giving.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Sat, 26 Sep 2009 07:40:03 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-4759659410938563147</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-26T20:10:03.764+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><description>    Executing the same test case by giving the number of inputs is known as what?On some sites I found that, it is known as Retesting.  But do you also think so?I think when we do retesting we reexecute the test case and If we are reexecuting the test case we rarely change the test input. Then how we can say it retesting? Retesting is done after bug fix. We can't call it Regression testing also,
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/oBaDB_MplfugPd3hYOoTfYiXHRo/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/oBaDB_MplfugPd3hYOoTfYiXHRo/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/oBaDB_MplfugPd3hYOoTfYiXHRo/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/oBaDB_MplfugPd3hYOoTfYiXHRo/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=TCeboz_EyWc:QN11g-ROH14:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/TCeboz_EyWc" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2009/09/executing-same-test-case-by-giving.html</feedburner:origLink></item><item><title>Test cases for Bulb</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/h53YEMXrch0/test-cases-for-bulb.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Fri, 18 Sep 2009 18:39:03 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-6696821013924646942</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-19T07:09:03.519+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>Hi,Here are the test cases for Bulb:-1) Check for company logo.2) Check for wattage marked.3) Test with wattage plus/minus one, as per capacity of bulb.4) Test for shape of the bulb.5) Test for performance of the bulb by leaving it ON for more than 50 hours. 6) Test bulb life.7) Test performance of bulb power up/down.8) Test for bulb holder compatibility.9) Test for bulb filament.10) Test for
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/X4K7iqlyWNZ32Zfcfpvan7zlYy0/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/X4K7iqlyWNZ32Zfcfpvan7zlYy0/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/X4K7iqlyWNZ32Zfcfpvan7zlYy0/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/X4K7iqlyWNZ32Zfcfpvan7zlYy0/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=h53YEMXrch0:kHMYld1DkOg:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/h53YEMXrch0" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2009/09/test-cases-for-bulb.html</feedburner:origLink></item><item><title>When writing test cases</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/K66_G_F0AkA/when-writing-test-cases.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Wed, 09 Sep 2009 02:41:41 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-4464887163735382223</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-09T15:11:41.333+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>Please consider following guidelines when writing test cases for any feature/module:1) Give preference to functional test cases.2) Write validation test cases also.3) Write positive and negative, both type of test cases.  4) Use test case writing techniques (Boundary value analysis, Equivalence class partitioning and Error guessing).5) Confirm database testing.6) Confirm UI/Browser compatibility
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/Y7O4eoqFRyd98qf8rjJJavmXE00/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Y7O4eoqFRyd98qf8rjJJavmXE00/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/Y7O4eoqFRyd98qf8rjJJavmXE00/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Y7O4eoqFRyd98qf8rjJJavmXE00/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=K66_G_F0AkA:Hkshgwj5fhQ:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/K66_G_F0AkA" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2009/09/when-writing-test-cases.html</feedburner:origLink></item><item><title>Not just tester, Be a hacker also</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/Kz1lDAtH6SY/not-just-tester-be-hacker-also.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Tue, 07 Jul 2009 23:17:29 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-4147909279077902974</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-08T11:47:29.871+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>In today complex web envoronment. If you are testing a website or a web product. Don't be a tester only but be a hacker also. Testing alone is not sufficient to say that we are secure. It may be the case that our site is working fine as customer expected. But it should also work as we expected, as client expected. What about a gun if anyone can shot it, but it's yours? If it is yours, only you
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/9TQtrQWHlYf3cyb0AIf3iqXBJNU/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/9TQtrQWHlYf3cyb0AIf3iqXBJNU/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/9TQtrQWHlYf3cyb0AIf3iqXBJNU/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/9TQtrQWHlYf3cyb0AIf3iqXBJNU/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=Kz1lDAtH6SY:21xY9xgVCiE:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/Kz1lDAtH6SY" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2009/07/not-just-tester-be-hacker-also.html</feedburner:origLink></item><item><title>Is really automation makes testing error free?</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/Ml7NyPnS1Dw/is-really-automation-makes-testing.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Sat, 29 Aug 2009 11:13:47 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-6980177842195819700</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2009-08-29T23:43:47.351+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><description>There is a general question in interviews " Automation makes testing error free, what you say?".Most of us answer this question in "Yes", but reality is different. I know one proverb "A fool with a tool is still a fool".In the same way, automation does not do anything itself. We are the testers who use the automated tools as per our requirements. Please keep things in mind.1) Not every test case
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/c0vby6Shg9UqCtGByMpQ8wuo5kk/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/c0vby6Shg9UqCtGByMpQ8wuo5kk/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/c0vby6Shg9UqCtGByMpQ8wuo5kk/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/c0vby6Shg9UqCtGByMpQ8wuo5kk/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=Ml7NyPnS1Dw:VkzZgQrnPhY:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/Ml7NyPnS1Dw" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2009/07/is-really-automation-makes-testing.html</feedburner:origLink></item><item><title>Usability Testing</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/5fzryzM-Rvw/usability-testing.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Sat, 29 Aug 2009 11:14:31 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-8767337537693009492</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2009-08-29T23:44:31.291+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><description>Usability testing is conducted to check with the user-friendlyness of the application.When does usability testing, test for1. Font size and face of the text in the application2. Grouping of objects3. Caps for initial letters4. Borders5. Resolution of screens6. Help Text7. Processing time etc.
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/LwtjaDcmDd8-ZCWpxnDT1ywXXCc/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/LwtjaDcmDd8-ZCWpxnDT1ywXXCc/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/LwtjaDcmDd8-ZCWpxnDT1ywXXCc/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/LwtjaDcmDd8-ZCWpxnDT1ywXXCc/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=5fzryzM-Rvw:oJTGiVyHkc4:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/5fzryzM-Rvw" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2009/06/usability-testing.html</feedburner:origLink></item><item><title>Use PNG file for screenshot</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/bA9GwO_WkXU/use-png-file-for-screenshot.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Sat, 29 Aug 2009 11:15:28 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-3010882023357055027</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2009-08-29T23:45:28.045+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><description>Hi,When we do testing and found any bug, sometimes we need to take the screen shot of the issue and it is advisable also, to better represent the issue to the developers. But many of us use BMP file to screenshot which makes a bug report heavy in size. Today almost all bug trackers are online and so, it needs to upload and download of screenshots when bug is under process. Please use PNG file for
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/zlcEapMtarflGoI0BSszszihwU0/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/zlcEapMtarflGoI0BSszszihwU0/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/zlcEapMtarflGoI0BSszszihwU0/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/zlcEapMtarflGoI0BSszszihwU0/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=bA9GwO_WkXU:sCagdzNLz4c:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/bA9GwO_WkXU" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2009/06/use-png-file-for-screenshot.html</feedburner:origLink></item><item><title>IBM interview -- Client asked you to complete the testing with in a  week</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/-r_naMq3yLY/ibm-interview-client-asked-you-to.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Sat, 05 Sep 2009 05:45:17 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-2400844346346209869</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-05T18:15:17.295+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">3</thr:total><description>Hi Friends,This is the question asked by IBM interviewers to one of the candidate."Client asked you to complete the testing with in a week, what you do ? how will you approach?"Let's make a clear discussion on it.Tell me what you think is the best answer for this question?1) I will do Adhoc Testing2) It Can't be tested3) Depending on project, I will test functionality first. 4) Depends on client
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/3bswuiW4OICHei9ZwgcZ4NAtaKA/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/3bswuiW4OICHei9ZwgcZ4NAtaKA/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/3bswuiW4OICHei9ZwgcZ4NAtaKA/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/3bswuiW4OICHei9ZwgcZ4NAtaKA/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=-r_naMq3yLY:6-pdso9UY-k:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/-r_naMq3yLY" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2009/06/ibm-interview-client-asked-you-to.html</feedburner:origLink></item><item><title>Right / Wrong way of bug fix/test</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/xB1mbh8eXoM/right-wrong-way-of-bug-fixtest.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Sat, 05 Sep 2009 05:45:39 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-3546989089095686761</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-05T18:15:39.050+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>Hi,     Tester has reported an issue and it has been fixed by respective developer. We retest the issue for bug fix. But how many of us see that, the way of fixing the bug is Right/Wrong?     Almost 99/100 testers ignore it. Take an example. There is an order form where user can apply discount code. If user has not applied it on initial order payment page, it can be applied on final payment page,
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/Oq9WnHEvFHPvEVHciAWBjnYCfbM/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Oq9WnHEvFHPvEVHciAWBjnYCfbM/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/Oq9WnHEvFHPvEVHciAWBjnYCfbM/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Oq9WnHEvFHPvEVHciAWBjnYCfbM/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=xB1mbh8eXoM:5nxcP43xyyM:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/xB1mbh8eXoM" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2009/06/right-wrong-way-of-bug-fixtest.html</feedburner:origLink></item><item><title>Bug Workflow</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/JMUab20hiGw/bug-workflow.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Mon, 08 Jun 2009 05:33:46 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-5106972477321837165</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-08T18:03:46.388+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>Bug Workflow• You find a bug, investigate it, and report it.• A programmer looks into it and fixes it, decides that a fix will take so long it needs management approval, recommends thatit be deferred (fix it later), or determines (argues) it is not a bug.  • The project manager prioritizes the unfixed bugs and may reassign them.• The project team (with representatives of the key stakeholder
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/EpQoo0DgHH5xhoILq0ubrCOSO1o/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/EpQoo0DgHH5xhoILq0ubrCOSO1o/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/EpQoo0DgHH5xhoILq0ubrCOSO1o/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/EpQoo0DgHH5xhoILq0ubrCOSO1o/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=JMUab20hiGw:TubzfGHzoQU:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/JMUab20hiGw" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2009/06/bug-workflow.html</feedburner:origLink></item><item><title>Preparation of the test cases without the documents</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/XzQrgiIMnR4/preparation-of-test-cases-without.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Sat, 05 Sep 2009 05:48:12 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-4604756507977837624</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-05T18:18:12.577+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><description>Hi,It's the general problem a small and middle companies face for their projects. Why they face such situations because their aim is to get projects. They generally follow no process for software development or one more reason is the client has freelancing the project when it was in starting phases, but as his business grow he want to add more and more features and so, outsourced the project to a
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/ixJKhc4eu_Z9iYnfU6BLX3mzH3Q/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ixJKhc4eu_Z9iYnfU6BLX3mzH3Q/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/ixJKhc4eu_Z9iYnfU6BLX3mzH3Q/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ixJKhc4eu_Z9iYnfU6BLX3mzH3Q/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=XzQrgiIMnR4:aYcPUS2L1Z4:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/XzQrgiIMnR4" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2009/05/preparation-of-test-cases-without.html</feedburner:origLink></item><item><title>Re: HI</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/8CdaYcanK_8/re-hi.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Sat, 29 Aug 2009 12:02:03 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-16442306697187247</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2009-08-30T00:32:03.494+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><description>Hi,   Integration testing is to test communication between two or more modules. For a website it can be data flow between two pages etc. In real time you always do the integration testing, but you don't know, how really you are doing it. If any time you you have tested the login form, you have seen that when you enter wrong username and password, you got error message, and if information is
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/hcdA5zFYrLS1ltb9pPhjs-mOTJA/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/hcdA5zFYrLS1ltb9pPhjs-mOTJA/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/hcdA5zFYrLS1ltb9pPhjs-mOTJA/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/hcdA5zFYrLS1ltb9pPhjs-mOTJA/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=8CdaYcanK_8:drIKUtwVTXU:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/8CdaYcanK_8" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2009/05/re-hi.html</feedburner:origLink></item><item><title>What is most important for a tester?</title><link>http://feedproxy.google.com/~r/SoftwareTestingExpertise/~3/ImjRbvXAVes/what-is-most-important-for-tester.html</link><author>noreply@blogger.com (Brijesh)</author><pubDate>Sat, 29 Aug 2009 12:19:37 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8016444265851003821.post-2680461419657659301</guid><app:edited xmlns:app="http://www.w3.org/2007/app">2009-08-30T00:49:37.442+05:30</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><description>Hi,As a tester everyone does the testing, still we see someone to grow fast in comparison of other testers. Do you know the reason? As per my experience, I learned some points which I want to share with you. I have title it "What is most important for a tester?" in respect to be better to other tester.1) Team lead qualities:- A and B are two testers working for a company now company is planning
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/l3WYMeG9az3676xsdn_AQiAJqcw/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/l3WYMeG9az3676xsdn_AQiAJqcw/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/l3WYMeG9az3676xsdn_AQiAJqcw/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/l3WYMeG9az3676xsdn_AQiAJqcw/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=ImjRbvXAVes:8YwBwo_Buic:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/SoftwareTestingExpertise?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/SoftwareTestingExpertise/~4/ImjRbvXAVes" height="1" width="1"/&gt;</description><feedburner:origLink>http://softwaretestingexpertise.blogspot.com/2009/05/what-is-most-important-for-tester.html</feedburner:origLink></item></channel></rss>
