<?xml version='1.0' encoding='UTF-8'?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/" xmlns:blogger="http://schemas.google.com/blogger/2008" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" version="2.0"><channel><atom:id>tag:blogger.com,1999:blog-3611283929809742247</atom:id><lastBuildDate>Fri, 30 Aug 2024 01:46:18 +0000</lastBuildDate><category>Improve bug reporting</category><category>Installation testing</category><category>Regression testing</category><category>Root Cause Analysis</category><category>customer satisfaction</category><category>software testing</category><title>Testing Geeks</title><description>Place for QA Geeks</description><link>http://testinggeeks.blogspot.com/</link><managingEditor>noreply@blogger.com (Bindu Laxminarayan)</managingEditor><generator>Blogger</generator><openSearch:totalResults>7</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3611283929809742247.post-1328810034286825065</guid><pubDate>Thu, 23 Apr 2009 21:27:00 +0000</pubDate><atom:updated>2009-04-29T03:12:10.284+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Improve bug reporting</category><title>Improve Bug Reporting</title><atom:summary type="text">Most of the times testers get irritated when developers reject there defects or when they reassign them to the testers for more information. Why do this happen? What is wrong with the posted defects? These are the questions which usually arises in a testers mind. Especially with the newcomers. Moreover, a lot of time is wasted for both testers and developers if the defects are not communicated </atom:summary><link>http://testinggeeks.blogspot.com/2009/04/improve-bug-reporting.html</link><author>noreply@blogger.com (Bindu Laxminarayan)</author><thr:total>1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3611283929809742247.post-7859104400896420516</guid><pubDate>Wed, 25 Jun 2008 02:19:00 +0000</pubDate><atom:updated>2008-06-25T08:04:18.322+05:30</atom:updated><title>Test Automation Scripting Techniques</title><atom:summary type="text">IntroductionIn the below section I will be discussing scripting techniques used in various test automation projects. Advantages and disadvantages of implementing the techniques.The various test automation scripting techniques are as follows1. Linear2. Structured3. Shared4. Data driven5. Keyword drivenLinear scriptingLinear scripting approach is a simple record and playback used by a testEngineer </atom:summary><link>http://testinggeeks.blogspot.com/2008/06/test-automation-scripting-techniques.html</link><author>noreply@blogger.com (Unknown)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3611283929809742247.post-8847664031350792862</guid><pubDate>Tue, 13 May 2008 03:17:00 +0000</pubDate><atom:updated>2008-05-15T20:03:01.668+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">customer satisfaction</category><title>How to Meet the Customer Expectations</title><atom:summary type="text">What is meant by success of every project? Delivering the end product to the client. All projects work hard and deliver the end product, then why do only some projects are always appreciated and some are not? The project is appreciated by the client only when the team meets the expectations of the client. This article will help the teams to deliver the end product along with some useful </atom:summary><link>http://testinggeeks.blogspot.com/2008/05/how-to-meet-customer-expectations.html</link><author>noreply@blogger.com (Bindu Laxminarayan)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3611283929809742247.post-6769418679071336343</guid><pubDate>Wed, 07 May 2008 11:16:00 +0000</pubDate><atom:updated>2008-05-07T18:46:39.588+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Regression testing</category><title>Optimizing the time allocated for Regression Testing</title><atom:summary type="text">Regression testing can be defined as process of testing changes to a programs to make sure that the older programming still works with the new changes.Regression testing involves reuse of tests to manage risks of change. Usually the regression test is performed by repeating the exact same test as before. But in the case where the test bank is huge and the time allocated is not sufficient </atom:summary><link>http://testinggeeks.blogspot.com/2008/05/optimizing-time-allocated-for.html</link><author>noreply@blogger.com (Bindu Laxminarayan)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3611283929809742247.post-3111097134283383664</guid><pubDate>Thu, 01 May 2008 13:27:00 +0000</pubDate><atom:updated>2008-05-02T14:01:13.082+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Root Cause Analysis</category><title>Root Cause Analysis for errors Encountered</title><atom:summary type="text">OVERVIEW:We know that Debugging is the activity performed by the developers for fixing a defect. But how good it would if a tester can identify the cause before this process is performed. Identifying the statement that is causing error without having the code is not possible. But identifying the module or the area of the software that is causing the problem is very interesting. This activity is </atom:summary><link>http://testinggeeks.blogspot.com/2008/05/root-cause-analysis-for-errors.html</link><author>noreply@blogger.com (Bindu Laxminarayan)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3611283929809742247.post-4300087733907248061</guid><pubDate>Tue, 29 Apr 2008 19:04:00 +0000</pubDate><atom:updated>2008-04-30T00:58:01.195+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Installation testing</category><title>Installation Testing</title><atom:summary type="text">Installation testing is a part of testing that is performed on every product. Though it is the basic testing that needs to be performed on every software most of the testers take this testing very casually. Some testers always look at the front end (ie the messages displayed during the installation) rather than the back end( ie files that are getting installed).It is responsiblity of the tester </atom:summary><link>http://testinggeeks.blogspot.com/2008/04/installation-testing.html</link><author>noreply@blogger.com (Bindu Laxminarayan)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3611283929809742247.post-7780697905195197522</guid><pubDate>Tue, 29 Apr 2008 18:39:00 +0000</pubDate><atom:updated>2008-04-30T00:34:35.188+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">software testing</category><title>For Newbies of Testing</title><atom:summary type="text">Though Software testing is becoming very popular, I found that the effective way of testing different kinds of products is not shared. Having good experience in software testing especially for products like security suites I have decided to share my experience through this blog.To start off with let me introduce to some facts for all the testers who are new to this field:1. It is impossible for </atom:summary><link>http://testinggeeks.blogspot.com/2008/04/for-newbies-of-testing.html</link><author>noreply@blogger.com (Bindu Laxminarayan)</author><thr:total>0</thr:total></item></channel></rss>