<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss'><id>tag:blogger.com,1999:blog-8016444265851003821</id><updated>2009-11-27T11:40:58.324+05:30</updated><title type='text'>Software Testing</title><subtitle type='html'>Testing Tutorial,Interview Questions, Video, Test cases ...</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://softwaretestingexpertise.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default?orderby=updated'/><link rel='alternate' type='text/html' href='http://softwaretestingexpertise.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><link rel='next' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default?start-index=26&amp;max-results=25&amp;orderby=updated'/><author><name>Brijesh</name><email>noreply@blogger.com</email></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>155</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-8016444265851003821.post-5744411229047495637</id><published>2009-11-05T12:01:00.001+05:30</published><updated>2009-11-05T12:01:53.516+05:30</updated><title type='text'>2- Real Testing - Real Experience</title><summary type='text'>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.    </summary><link rel='replies' type='application/atom+xml' href='http://softwaretestingexpertise.blogspot.com/feeds/5744411229047495637/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=8016444265851003821&amp;postID=5744411229047495637' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/5744411229047495637'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/5744411229047495637'/><link rel='alternate' type='text/html' href='http://softwaretestingexpertise.blogspot.com/2009/11/2-real-testing-real-experience.html' title='2- Real Testing - Real Experience'/><author><name>Brijesh</name><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='17996872925884695187'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8016444265851003821.post-2885701886676054538</id><published>2009-11-04T14:39:00.001+05:30</published><updated>2009-11-04T14:39:52.981+05:30</updated><title type='text'>Real Testing - Real Experience</title><summary type='text'>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 </summary><link rel='replies' type='application/atom+xml' href='http://softwaretestingexpertise.blogspot.com/feeds/2885701886676054538/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=8016444265851003821&amp;postID=2885701886676054538' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/2885701886676054538'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/2885701886676054538'/><link rel='alternate' type='text/html' href='http://softwaretestingexpertise.blogspot.com/2009/11/real-testing-real-experience.html' title='Real Testing - Real Experience'/><author><name>Brijesh</name><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='17996872925884695187'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8016444265851003821.post-1134108136116867631</id><published>2009-10-30T10:29:00.002+05:30</published><updated>2009-10-30T10:35:38.858+05:30</updated><title type='text'>Bug of the Month</title><summary type='text'>
   '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/</summary><link rel='replies' type='application/atom+xml' href='http://softwaretestingexpertise.blogspot.com/feeds/1134108136116867631/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=8016444265851003821&amp;postID=1134108136116867631' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/1134108136116867631'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/1134108136116867631'/><link rel='alternate' type='text/html' href='http://softwaretestingexpertise.blogspot.com/2009/10/bug-of-month.html' title='Bug of the Month'/><author><name>Brijesh</name><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='17996872925884695187'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8016444265851003821.post-3947154725631493896</id><published>2009-10-28T15:16:00.001+05:30</published><updated>2009-10-28T15:16:53.686+05:30</updated><title type='text'>How and Why to Clear Your Cache?</title><summary type='text'>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 </summary><link rel='replies' type='application/atom+xml' href='http://softwaretestingexpertise.blogspot.com/feeds/3947154725631493896/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=8016444265851003821&amp;postID=3947154725631493896' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/3947154725631493896'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/3947154725631493896'/><link rel='alternate' type='text/html' href='http://softwaretestingexpertise.blogspot.com/2009/10/how-and-why-to-clear-your-cache.html' title='How and Why to Clear Your Cache?'/><author><name>Brijesh</name><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='17996872925884695187'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8016444265851003821.post-2616860230840812369</id><published>2009-10-28T10:20:00.001+05:30</published><updated>2009-10-28T10:20:56.380+05:30</updated><title type='text'>objective questions with answer</title><summary type='text'>(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 </summary><link rel='replies' type='application/atom+xml' href='http://softwaretestingexpertise.blogspot.com/feeds/2616860230840812369/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=8016444265851003821&amp;postID=2616860230840812369' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/2616860230840812369'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/2616860230840812369'/><link rel='alternate' type='text/html' href='http://softwaretestingexpertise.blogspot.com/2009/10/objective-questions-with-answer.html' title='objective questions with answer'/><author><name>Brijesh</name><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='17996872925884695187'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8016444265851003821.post-2517120238031596564</id><published>2009-10-27T12:59:00.001+05:30</published><updated>2009-10-27T12:59:29.735+05:30</updated><title type='text'>What is a GUI Prototype?</title><summary type='text'>   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 </summary><link rel='replies' type='application/atom+xml' href='http://softwaretestingexpertise.blogspot.com/feeds/2517120238031596564/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=8016444265851003821&amp;postID=2517120238031596564' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/2517120238031596564'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/2517120238031596564'/><link rel='alternate' type='text/html' href='http://softwaretestingexpertise.blogspot.com/2009/10/what-is-gui-prototype.html' title='What is a GUI Prototype?'/><author><name>Brijesh</name><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='17996872925884695187'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8016444265851003821.post-6014778152158020778</id><published>2009-10-16T17:26:00.001+05:30</published><updated>2009-10-16T17:26:02.884+05:30</updated><title type='text'>Is accessibility testing different from GUI testing ?</title><summary type='text'>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 </summary><link rel='replies' type='application/atom+xml' href='http://softwaretestingexpertise.blogspot.com/feeds/6014778152158020778/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=8016444265851003821&amp;postID=6014778152158020778' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/6014778152158020778'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/6014778152158020778'/><link rel='alternate' type='text/html' href='http://softwaretestingexpertise.blogspot.com/2009/10/is-accessibility-testing-different-from.html' title='Is accessibility testing different from GUI testing ?'/><author><name>Brijesh</name><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='17996872925884695187'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8016444265851003821.post-8472491992217121222</id><published>2009-10-14T10:32:00.001+05:30</published><updated>2009-10-14T10:32:44.763+05:30</updated><title type='text'>Difference between test case and test scenario</title><summary type='text'>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 </summary><link rel='replies' type='application/atom+xml' href='http://softwaretestingexpertise.blogspot.com/feeds/8472491992217121222/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=8016444265851003821&amp;postID=8472491992217121222' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/8472491992217121222'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/8472491992217121222'/><link rel='alternate' type='text/html' href='http://softwaretestingexpertise.blogspot.com/2009/10/difference-between-test-case-and-test.html' title='Difference between test case and test scenario'/><author><name>Brijesh</name><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='17996872925884695187'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8016444265851003821.post-8744454468549780123</id><published>2009-10-13T11:35:00.001+05:30</published><updated>2009-10-13T11:35:09.372+05:30</updated><title type='text'>How to log a defect?</title><summary type='text'>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. </summary><link rel='replies' type='application/atom+xml' href='http://softwaretestingexpertise.blogspot.com/feeds/8744454468549780123/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=8016444265851003821&amp;postID=8744454468549780123' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/8744454468549780123'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/8744454468549780123'/><link rel='alternate' type='text/html' href='http://softwaretestingexpertise.blogspot.com/2009/10/how-to-log-defect.html' title='How to log a defect?'/><author><name>Brijesh</name><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='17996872925884695187'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8016444265851003821.post-4371118191488764491</id><published>2009-10-12T17:48:00.001+05:30</published><updated>2009-10-12T17:48:21.198+05:30</updated><title type='text'>Test cases for Lift</title><summary type='text'>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 </summary><link rel='replies' type='application/atom+xml' href='http://softwaretestingexpertise.blogspot.com/feeds/4371118191488764491/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=8016444265851003821&amp;postID=4371118191488764491' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/4371118191488764491'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/4371118191488764491'/><link rel='alternate' type='text/html' href='http://softwaretestingexpertise.blogspot.com/2009/10/test-cases-for-lift.html' title='Test cases for Lift'/><author><name>Brijesh</name><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='17996872925884695187'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8016444265851003821.post-7214342279640007267</id><published>2009-10-12T11:15:00.001+05:30</published><updated>2009-10-12T11:15:44.777+05:30</updated><title type='text'>How to interact with the developer about the bug?</title><summary type='text'>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 </summary><link rel='replies' type='application/atom+xml' href='http://softwaretestingexpertise.blogspot.com/feeds/7214342279640007267/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=8016444265851003821&amp;postID=7214342279640007267' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/7214342279640007267'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/7214342279640007267'/><link rel='alternate' type='text/html' href='http://softwaretestingexpertise.blogspot.com/2009/10/how-to-interact-with-developer-about.html' title='How to interact with the developer about the bug?'/><author><name>Brijesh</name><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='17996872925884695187'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8016444265851003821.post-1813365449163876934</id><published>2009-09-29T11:04:00.001+05:30</published><updated>2009-09-29T11:04:12.729+05:30</updated><title type='text'>Relation b/w Acceptance testing and Beta testing</title><summary type='text'>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. </summary><link rel='replies' type='application/atom+xml' href='http://softwaretestingexpertise.blogspot.com/feeds/1813365449163876934/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=8016444265851003821&amp;postID=1813365449163876934' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/1813365449163876934'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/1813365449163876934'/><link rel='alternate' type='text/html' href='http://softwaretestingexpertise.blogspot.com/2009/09/relation-bw-acceptance-testing-and-beta.html' title='Relation b/w Acceptance testing and Beta testing'/><author><name>Brijesh</name><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='17996872925884695187'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8016444265851003821.post-4759659410938563147</id><published>2009-09-26T20:10:00.001+05:30</published><updated>2009-09-26T20:10:03.764+05:30</updated><title type='text'>Executing the same test case by giving the number of inputs</title><summary type='text'>    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, </summary><link rel='replies' type='application/atom+xml' href='http://softwaretestingexpertise.blogspot.com/feeds/4759659410938563147/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=8016444265851003821&amp;postID=4759659410938563147' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/4759659410938563147'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/4759659410938563147'/><link rel='alternate' type='text/html' href='http://softwaretestingexpertise.blogspot.com/2009/09/executing-same-test-case-by-giving.html' title='Executing the same test case by giving the number of inputs'/><author><name>Brijesh</name><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='17996872925884695187'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8016444265851003821.post-6696821013924646942</id><published>2009-09-19T07:09:00.001+05:30</published><updated>2009-09-19T07:09:03.519+05:30</updated><title type='text'>Test cases for Bulb</title><summary type='text'>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 </summary><link rel='replies' type='application/atom+xml' href='http://softwaretestingexpertise.blogspot.com/feeds/6696821013924646942/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=8016444265851003821&amp;postID=6696821013924646942' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/6696821013924646942'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/6696821013924646942'/><link rel='alternate' type='text/html' href='http://softwaretestingexpertise.blogspot.com/2009/09/test-cases-for-bulb.html' title='Test cases for Bulb'/><author><name>Brijesh</name><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='17996872925884695187'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8016444265851003821.post-4464887163735382223</id><published>2009-09-09T15:11:00.001+05:30</published><updated>2009-09-09T15:11:41.333+05:30</updated><title type='text'>When writing test cases</title><summary type='text'>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 </summary><link rel='replies' type='application/atom+xml' href='http://softwaretestingexpertise.blogspot.com/feeds/4464887163735382223/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=8016444265851003821&amp;postID=4464887163735382223' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/4464887163735382223'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/4464887163735382223'/><link rel='alternate' type='text/html' href='http://softwaretestingexpertise.blogspot.com/2009/09/when-writing-test-cases.html' title='When writing test cases'/><author><name>Brijesh</name><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='17996872925884695187'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8016444265851003821.post-180134001097696268</id><published>2008-08-08T11:45:00.002+05:30</published><updated>2009-09-06T11:28:58.192+05:30</updated><title type='text'>Why Traceability Matrix?</title><summary type='text'>The client who had ordered for the product specifies his requirements to the development Team and the process of Software Development gets started. In addition to the requirements specified by the client, the development team may also propose various value added suggestions that could be added on to the software. But maintaining a track of all the requirements specified in the requirement </summary><link rel='replies' type='application/atom+xml' href='http://softwaretestingexpertise.blogspot.com/feeds/180134001097696268/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=8016444265851003821&amp;postID=180134001097696268' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/180134001097696268'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/180134001097696268'/><link rel='alternate' type='text/html' href='http://softwaretestingexpertise.blogspot.com/2008/08/why-traceability-matrix.html' title='Why Traceability Matrix?'/><author><name>Brijesh</name><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='17996872925884695187'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8016444265851003821.post-72107875806738953</id><published>2008-12-17T11:29:00.002+05:30</published><updated>2009-09-06T11:26:24.895+05:30</updated><title type='text'>Pesticide Paradox</title><summary type='text'>Software Testing Techniques Second Edition:Introduction    &lt;!--  A:hover  {   color : Red;  }  --&gt; You're a poor farmer growing cotton in Alabama and the boll weevils are  destroying your crop. You mortgage the farm to buy DDT, which you spray on your  field, killing 98% of the pest, saving the crop. The next year, you spray the  DDT early in the season, but the boll weevils still eat your crop </summary><link rel='replies' type='application/atom+xml' href='http://softwaretestingexpertise.blogspot.com/feeds/72107875806738953/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=8016444265851003821&amp;postID=72107875806738953' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/72107875806738953'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/72107875806738953'/><link rel='alternate' type='text/html' href='http://softwaretestingexpertise.blogspot.com/2008/12/pesticide-paradox.html' title='Pesticide Paradox'/><author><name>Brijesh</name><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='17996872925884695187'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8016444265851003821.post-2687955754439530404</id><published>2008-12-19T15:18:00.002+05:30</published><updated>2009-09-06T11:26:06.959+05:30</updated><title type='text'>The Program Environment</title><summary type='text'>Software Testing Techniques Second Edition:Introduction   &lt;!--  A:hover  {   color : Red;  }  --&gt;   Program's environment is the hardware and software required to make it  run. The environment also includes all programs  that interact with—and are used to create—the program under test, such as  operating system, loader, linkage editor, compiler, utility routines.  Because hardware and firmware </summary><link rel='replies' type='application/atom+xml' href='http://softwaretestingexpertise.blogspot.com/feeds/2687955754439530404/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=8016444265851003821&amp;postID=2687955754439530404' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/2687955754439530404'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/2687955754439530404'/><link rel='alternate' type='text/html' href='http://softwaretestingexpertise.blogspot.com/2008/12/program-environment.html' title='The Program Environment'/><author><name>Brijesh</name><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='17996872925884695187'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8016444265851003821.post-6574763151041423121</id><published>2008-12-22T17:48:00.002+05:30</published><updated>2009-09-06T11:25:42.389+05:30</updated><title type='text'>Cyclomatic complexity (McCabe’s Metric)</title><summary type='text'>Software Testing Techniques Second Edition:Metrics and Complexity   &lt;!--  A:hover  {   color : Red;  }  --&gt; McCabe's cyclornatic complexity metric (MCCA76) is defined as:  M = L — N + 2P  where  L = the number of links in the graph N = the number of nodes in the graph P = the number of disconnected parts of the graph (e.g., a calling  program and a subroutine)   &lt;!--  A:hover  {   color : Red;  }</summary><link rel='replies' type='application/atom+xml' href='http://softwaretestingexpertise.blogspot.com/feeds/6574763151041423121/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=8016444265851003821&amp;postID=6574763151041423121' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/6574763151041423121'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/6574763151041423121'/><link rel='alternate' type='text/html' href='http://softwaretestingexpertise.blogspot.com/2008/12/cyclomatic-complexity-mccabes-metric.html' title='Cyclomatic complexity (McCabe’s Metric)'/><author><name>Brijesh</name><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='17996872925884695187'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8016444265851003821.post-326351131709692681</id><published>2008-07-22T13:03:00.002+05:30</published><updated>2009-09-06T11:24:43.068+05:30</updated><title type='text'>Ten things to avoid in a website</title><summary type='text'>Ten things to avoid in a website Frames                 Over-use of "leading-edge" technology                Scrolling text, marquees, and animations                Complex URLs                Orphan pages                Long scrolling pages                No navigation support                Non-standard link colors                Outdated information                Long download times           </summary><link rel='replies' type='application/atom+xml' href='http://softwaretestingexpertise.blogspot.com/feeds/326351131709692681/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=8016444265851003821&amp;postID=326351131709692681' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/326351131709692681'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/326351131709692681'/><link rel='alternate' type='text/html' href='http://softwaretestingexpertise.blogspot.com/2008/07/ten-things-to-avoid-in-website.html' title='Ten things to avoid in a website'/><author><name>Brijesh</name><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='17996872925884695187'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8016444265851003821.post-6824476794070009725</id><published>2008-07-17T16:11:00.002+05:30</published><updated>2009-09-06T11:24:28.023+05:30</updated><title type='text'>If developer do not accepts a bug; then what to do?</title><summary type='text'>Question:- If developer do not accepts the bug; then what to do?Answer:- Hi, many times this situation occurs, when a tester find the bug and report it to developers to fix. But still developers say no to fif the bug. The reason may not be that developers don't want to fix it. Reason may be:-1) A related bug is already posted, so developer knows that fixing that bug will fix it automatically.2) </summary><link rel='replies' type='application/atom+xml' href='http://softwaretestingexpertise.blogspot.com/feeds/6824476794070009725/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=8016444265851003821&amp;postID=6824476794070009725' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/6824476794070009725'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/6824476794070009725'/><link rel='alternate' type='text/html' href='http://softwaretestingexpertise.blogspot.com/2008/07/if-developer-do-not-accepts-bug-then.html' title='If developer do not accepts a bug; then what to do?'/><author><name>Brijesh</name><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='17996872925884695187'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8016444265851003821.post-3907718290881515970</id><published>2008-07-21T15:39:00.002+05:30</published><updated>2009-09-06T11:24:27.804+05:30</updated><title type='text'>Re: Difference between functional and technical tester?</title><summary type='text'>On Mon, Jul 21, 2008 at 2:06 AM, preethi menon  wrote: Hi brijesh,what is the difference between functional tester and technical tester?regardsPreethi Hi,Break the word "technical tester", into "technical" and "tester". What do you thing if we say functional tester, it means it is related to software functionality. No, functional testing is a general term, and as we are talking about software in </summary><link rel='replies' type='application/atom+xml' href='http://softwaretestingexpertise.blogspot.com/feeds/3907718290881515970/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=8016444265851003821&amp;postID=3907718290881515970' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/3907718290881515970'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/3907718290881515970'/><link rel='alternate' type='text/html' href='http://softwaretestingexpertise.blogspot.com/2008/07/re-difference-between-functional-and.html' title='Re: Difference between functional and technical tester?'/><author><name>Brijesh</name><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='17996872925884695187'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8016444265851003821.post-6747877386750877556</id><published>2008-07-22T12:38:00.002+05:30</published><updated>2009-09-06T11:24:22.769+05:30</updated><title type='text'>Why do bugs occur ?</title><summary type='text'>Question:- Why do bugs occur ?Answer:- There are so many reasons for bugs to occur:-1) Miscommunication or no communication2) Unclear requirements3) Time lines4) Human errors5) Technical reasons6) Frequent changes in requirementsand so on...</summary><link rel='replies' type='application/atom+xml' href='http://softwaretestingexpertise.blogspot.com/feeds/6747877386750877556/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=8016444265851003821&amp;postID=6747877386750877556' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/6747877386750877556'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/6747877386750877556'/><link rel='alternate' type='text/html' href='http://softwaretestingexpertise.blogspot.com/2008/07/why-do-bugs-occur.html' title='Why do bugs occur ?'/><author><name>Brijesh</name><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='17996872925884695187'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8016444265851003821.post-3288539027347925260</id><published>2008-08-12T11:44:00.002+05:30</published><updated>2009-09-06T11:24:14.690+05:30</updated><title type='text'>THE EIGHT BASIC PRINCIPLES OF TESTING</title><summary type='text'>Following are eight basic principles of testing: 1. Define the expected output or result. 2. Don't test your own programs. 3. Inspect the results of each test completely. 4. Include test cases for invalid or unexpected conditions. 5. Test the program to see if it does what it is not supposed to do as well as what it is supposed to do. 6. Avoid disposable test cases unless the program itself is </summary><link rel='replies' type='application/atom+xml' href='http://softwaretestingexpertise.blogspot.com/feeds/3288539027347925260/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=8016444265851003821&amp;postID=3288539027347925260' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/3288539027347925260'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/3288539027347925260'/><link rel='alternate' type='text/html' href='http://softwaretestingexpertise.blogspot.com/2008/08/eight-basic-principles-of-testing.html' title='THE EIGHT BASIC PRINCIPLES OF TESTING'/><author><name>Brijesh</name><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='17996872925884695187'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8016444265851003821.post-206672309226960967</id><published>2008-08-12T11:59:00.002+05:30</published><updated>2009-09-06T11:23:57.103+05:30</updated><title type='text'>Exploratory testing v/s Chess Game</title><summary type='text'>Sometimes we have to follow the process of finding the most important bugs in a short period of time, this is called exploratory testing.Exploratory testing is like a chess game with a computer. Tester revise his plans after seeing the move of your opponent. Yet all your plans can be changed after one unpredictable move of your opponent. Can you write a detail plan for a chess game with a </summary><link rel='replies' type='application/atom+xml' href='http://softwaretestingexpertise.blogspot.com/feeds/206672309226960967/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=8016444265851003821&amp;postID=206672309226960967' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/206672309226960967'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8016444265851003821/posts/default/206672309226960967'/><link rel='alternate' type='text/html' href='http://softwaretestingexpertise.blogspot.com/2008/08/exploratory-testing-vs-chess-game.html' title='Exploratory testing v/s Chess Game'/><author><name>Brijesh</name><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='17996872925884695187'/></author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></entry></feed>