<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Worst Practices in Performance Testing</title>
	<atom:link href="http://www.jds.net.au/tech-tips/performance-testing-worst-practices/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jds.net.au/tech-tips/performance-testing-worst-practices/</link>
	<description>Expert consulting services with HP Software</description>
	<lastBuildDate>Tue, 08 Jun 2010 15:08:25 +1000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Stan Desyatnikov</title>
		<link>http://www.jds.net.au/tech-tips/performance-testing-worst-practices/#comment-8782</link>
		<dc:creator>Stan Desyatnikov</dc:creator>
		<pubDate>Wed, 25 Nov 2009 13:28:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.jds.net.au/?p=2343#comment-8782</guid>
		<description>Another example for &quot;Stick to the requirements, even when they don’t make sense&quot;

When there is only one response time threshold for all applications/transactions, e.g. 3 or 5 seconds.

Sometimes it is useless for the transactions that handle big volumes of data. (e.g. search, export, upload, download transactions).

I think, for such cases there should be defined appropriate response time thresholds.</description>
		<content:encoded><![CDATA[<p>Another example for &#8220;Stick to the requirements, even when they don’t make sense&#8221;</p>
<p>When there is only one response time threshold for all applications/transactions, e.g. 3 or 5 seconds.</p>
<p>Sometimes it is useless for the transactions that handle big volumes of data. (e.g. search, export, upload, download transactions).</p>
<p>I think, for such cases there should be defined appropriate response time thresholds.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ward</title>
		<link>http://www.jds.net.au/tech-tips/performance-testing-worst-practices/#comment-8747</link>
		<dc:creator>Ward</dc:creator>
		<pubDate>Mon, 23 Nov 2009 06:39:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.jds.net.au/?p=2343#comment-8747</guid>
		<description>SMEs are also the folks that commonly know how the business will perform various different transactions. So they identify the transaction steps to the Performance Tester.  Otherwise in large systems testers may invoke a business process that is not used by the business.</description>
		<content:encoded><![CDATA[<p>SMEs are also the folks that commonly know how the business will perform various different transactions. So they identify the transaction steps to the Performance Tester.  Otherwise in large systems testers may invoke a business process that is not used by the business.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Wilton</title>
		<link>http://www.jds.net.au/tech-tips/performance-testing-worst-practices/#comment-8746</link>
		<dc:creator>Nick Wilton</dc:creator>
		<pubDate>Mon, 23 Nov 2009 05:32:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.jds.net.au/?p=2343#comment-8746</guid>
		<description>Often a symptom of the first three items above; is that performance testing is often left to the very last week or two before the go-live date.
It is a very good idea to performance test an application as early as possible, particularly if the application has been highly-customized. Some integration tools even allow you do run a performance test during code build cycles.
Defects raised during performance testing tend to be architectural in nature which can result in fundamental code changes, and therefore much code or configuration rework. Effective projects tend to include a full performance review cycle within their solution design phase which can very beneficial in mitigating the risk of significant performance defects being raised.</description>
		<content:encoded><![CDATA[<p>Often a symptom of the first three items above; is that performance testing is often left to the very last week or two before the go-live date.<br />
It is a very good idea to performance test an application as early as possible, particularly if the application has been highly-customized. Some integration tools even allow you do run a performance test during code build cycles.<br />
Defects raised during performance testing tend to be architectural in nature which can result in fundamental code changes, and therefore much code or configuration rework. Effective projects tend to include a full performance review cycle within their solution design phase which can very beneficial in mitigating the risk of significant performance defects being raised.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anon</title>
		<link>http://www.jds.net.au/tech-tips/performance-testing-worst-practices/#comment-8737</link>
		<dc:creator>Anon</dc:creator>
		<pubDate>Mon, 23 Nov 2009 00:01:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.jds.net.au/?p=2343#comment-8737</guid>
		<description>Test managers always want to re-write my reports. The last one wanted me to remove every occurance of the word &quot;defect&quot; from the report, and replace it with &quot;issue&quot;. :-)

Also, this Tech Tip reminded me of a quote from Douglas Adams...
&lt;em&gt;Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so.&lt;/em&gt;
</description>
		<content:encoded><![CDATA[<p>Test managers always want to re-write my reports. The last one wanted me to remove every occurance of the word &#8220;defect&#8221; from the report, and replace it with &#8220;issue&#8221;. :-)</p>
<p>Also, this Tech Tip reminded me of a quote from Douglas Adams&#8230;<br />
<em>Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so.</em></p>
]]></content:encoded>
	</item>
</channel>
</rss>
