<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rss [<!ENTITY % HTMLlat1 PUBLIC "-//W3C//ENTITIES Latin 1 for XHTML//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent">]>
<rss version="0.92" xml:base="http://www.testingreflections.com">
<channel>
 <title>testingReflections.com - taxonomy</title>
 <link>http://www.testingreflections.com/taxonomy/view/or/1</link>
 <description>Opinions on the categories available for your blogs - disagree with the terminology... hierarchy... whatever</description>
 <language>en</language>
<item>
 <title>Queuing discipline (FIFO + Round Robin)</title>
 <link>http://www.testingreflections.com/node/view/4841</link>
 <description>[textile]&lt;br /&gt;
After long stint at the client location i came back to india last week.  Since i had been away for long period i wanted to visit all my near and dear. I drove to my parents place (vizag in india).i wanted my entire family to go on a small vacation my father as  usual wanted to travel by train rather than air so we both visted the nearest railway reservation counters in the city.</description>
<pubDate>Thu, 18 Jan 2007 11:46:11 -0600</pubDate></item>
<item>
 <title>Weakest link (Reverse salients)</title>
 <link>http://www.testingreflections.com/node/view/4769</link>
 <description>&lt;p&gt;
On my way back home after a recent client visit i happen to pick a strategy + business latest edition magazine by Booz | Allen | Hamilton, one of the article titled "The weakest link" by Nicholas G. Carr summed it up as below&lt;/p&gt;
"A products vulnerabilities can point the way to lucrative new business opportunities".  Interesting and valid view point, this is how new products version/ideas are concieved for e.g. win3.1-&gt;win95-&gt;win98-&gt;winxp-&gt;vista.</description>
<pubDate>Wed, 03 Jan 2007 00:51:19 -0600</pubDate></item>
<item>
 <title>Sizing Disks:recommend appropriate hardware</title>
 <link>http://www.testingreflections.com/node/view/4757</link>
 <description>&lt;p&gt;
A typical Load test (utilizing a typical workload) on your test environment (representing a production model) results in raw performance data, this data could be utilized to uncover sizing information.&lt;/p&gt;</description>
<pubDate>Thu, 28 Dec 2006 03:53:47 -0600</pubDate></item>
<item>
 <title>Universal scalability law</title>
 <link>http://www.testingreflections.com/node/view/4729</link>
 <description>[textile]After reading the book practical performance analyst and articles on universal law of scalability i was fascinated by the theory. I quickly wanted to apply these laws on my old performance raw data, to predict the performance of the application using the models.  The first experience was breath taking to see the accuracy with which the model predicted.</description>
<pubDate>Thu, 28 Dec 2006 09:46:51 -0600</pubDate></item>
<item>
 <title>Disabling CPU's (RH Linux,Solaris,Windows)</title>
 <link>http://www.testingreflections.com/node/view/4306</link>
 <description>There is always need to play with the number of CPU's when you need to conduct a scale-in test.</description>
<pubDate>Thu, 28 Dec 2006 14:05:19 -0600</pubDate></item>
<item>
 <title>Proactive performance management:Some ideas</title>
 <link>http://www.testingreflections.com/node/view/3892</link>
 <description>2.5 years ago when i worked as a lead in a performance testing project we learnt few tricks which helped us to do proactive performance management early in the life cycle.</description>
<pubDate>Thu, 28 Dec 2006 14:06:51 -0600</pubDate></item>
<item>
 <title>Setting up WAN environment: Open Source</title>
 <link>http://www.testingreflections.com/node/view/3868</link>
 <description>&lt;b&gt;Introduction&lt;/b&gt;
&lt;p&gt;In the context of designing application performance from ground up every aspect of end user usage needs to be considered before the application is rolled out to production. One topic of interest is the inter connectivity of the computing systems and end user connectivity to the computing systems in the production.</description>
<pubDate>Thu, 28 Dec 2006 14:07:34 -0600</pubDate></item>
<item>
 <title>Transition of Bugs</title>
 <link>http://www.testingreflections.com/node/view/3127</link>
 <description>I do testing in application which is developed under eXtreme Programming model. Due to the short span of the development process, we always work with bitter pressure. Whenever I encounter a bug, I immediately logged the issue in the tracking tool and if necessary I would made a face to face discussion with the developers.&lt;br /&gt;
 &lt;br /&gt;
I was recently testing an application which had an excellent search function. Most of the pages had a data grid with 4 to 6 columns. The point here I wish to mention is, the bugs identified is taking different weightage at different levels of development process. Within a period of week, the high priority bug becomes obsolete.</description>
<pubDate>Fri, 20 Jan 2006 11:38:43 -0600</pubDate></item>
<item>
 <title>The problem of communication</title>
 <link>http://www.testingreflections.com/node/view/2940</link>
 <description>&lt;strong&gt;1. Introduction&lt;/strong&gt;&lt;br /&gt;
&lt;br /&gt;
A lot of waste and rework is done because of bad communication. In fact, communication is the main factor in a project success or failure. And that does not refer only to software. Alistair Cockburn, wrote an entire book about the importance of communication and builds a methodology around improving communication: the crystal family&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;2. The big misunderstanding: improving means increasing quantity&lt;/strong&gt;</description>
<pubDate>Mon, 07 Nov 2005 08:52:18 -0600</pubDate></item>
<item>
 <title>A young web test tools:Selenium</title>
 <link>http://www.testingreflections.com/node/view/2905</link>
 <description>This is my first blog!congratulation to myself!&lt;br /&gt;
I have worked on &lt;a href="http://selenium.thoughtworks.com"&gt;Selenium&lt;/a&gt; about one week.I think &lt;a href="http://selenium.thoughtworks.com"&gt;Selenium&lt;/a&gt; is a great tool.&lt;br /&gt;
The one just only know about html and javascript can ride with &lt;a href="http://selenium.thoughtworks.com"&gt;Selenium&lt;/a&gt;.&lt;br /&gt;
JavaScript makes &lt;a href="http://selenium.thoughtworks.com"&gt;Selenium&lt;/a&gt; easy and powerful but also brings some limitations.</description>
<pubDate>Wed, 26 Oct 2005 07:30:55 -0500</pubDate></item>
<item>
 <title>How did we get Here?</title>
 <link>http://www.testingreflections.com/node/view/2126</link>
 <description>How did this happen (our director fired)?  Here is my analysis - he was the victim of a huge failed project.  Did he have any intimate involvement with the project?  No.  Was he at fault in any way? No.  He was gunned down by the corporate equivalent of friendly fire.  In actuality his firing was more akin to collateral damage.  Let this be a lesson to all of us.  No matter how good of a job you do.  No matter how much your boss likes you.  No matter how long you have been at your company.  Events completely unrelated to you and your work can take you down.</description>
<pubDate>Mon, 09 May 2005 07:51:55 -0500</pubDate></item>
<item>
 <title>End of an Era</title>
 <link>http://www.testingreflections.com/node/view/2072</link>
 <description>Two weeks ago, my team was called into a meeting where we were told that our director (of Software Quality Assurance) was being redeployed - which is the new term for laid off - in our company.  He ran the SQA group for over 10 years.  Throughout his reign he introduced a process that is defined yet flexible, continually honed and re-evaluated.  We have had audits both independent and internal, hired consultants to sharpen our skills and certify our work.</description>
<pubDate>Wed, 27 Apr 2005 09:50:48 -0500</pubDate></item>
<item>
 <title>more vocabularies to be added for categorising of posts</title>
 <link>http://www.testingreflections.com/node/view/8</link>
 <description>[textile]The first item of discussion for us to chew over is the vocabularies to use on this site. I am going to attempt to build a taxonomy based on 'standard' software testing terms... Since, internationally, there are so many, I will initially base it on (deep breath!) the British Computer Society affiliated Specialist Interest Group In Software Testing's (inhale!! breath) Standards Working Party's "living glossary":http://www.testingstandards.co.uk/living_glossary.htm</description>
<pubDate>Thu, 01 Jul 2004 21:07:59 -0500</pubDate></item>
</channel>
</rss>
