<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Managing Quality (part 4) - Stress Testing</title><link>http://blogs.msdn.com/b/bharry/archive/2007/02/11/managing-quality-part-4-stress-testing.aspx</link><description>The goal of our stress testing is to run an application under load for an extended period of time and capture all "failures". The purpose is to uncover race conditions, long term resource leaks, and bugs that only occur as the result of unexpected sequences</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Managing Quality (part 4) - Stress Testing</title><link>http://blogs.msdn.com/b/bharry/archive/2007/02/11/managing-quality-part-4-stress-testing.aspx#3974722</link><pubDate>Fri, 20 Jul 2007 15:53:18 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3974722</guid><dc:creator>Brian Harry MS</dc:creator><description>&lt;p&gt;We use the Visual Studio Team Edition for Testers product. &amp;nbsp;We write &amp;quot;unit tests&amp;quot; that exercise the various components/scenarios and the load testing tool then randomly runs those tests, simulating hundreds or thousands of users.&lt;/p&gt;
&lt;p&gt;Brian&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=3974722" width="1" height="1"&gt;</description></item><item><title>re: Managing Quality (part 4) - Stress Testing</title><link>http://blogs.msdn.com/b/bharry/archive/2007/02/11/managing-quality-part-4-stress-testing.aspx#3970623</link><pubDate>Fri, 20 Jul 2007 10:11:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3970623</guid><dc:creator>Manjusha</dc:creator><description>&lt;p&gt;What kind of tool we can use to stress test an application (Database dependent) and used in different branches simulteneously........!&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=3970623" width="1" height="1"&gt;</description></item><item><title>The many faces of quality</title><link>http://blogs.msdn.com/b/bharry/archive/2007/02/11/managing-quality-part-4-stress-testing.aspx#2220578</link><pubDate>Sat, 21 Apr 2007 16:59:43 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2220578</guid><dc:creator>Jeff Beehler's Blog</dc:creator><description>&lt;p&gt;Brian's been compiling a great series of posts regarding managing quality which I would highly recommend&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=2220578" width="1" height="1"&gt;</description></item><item><title>Managing Orcas Beta exit criteria by dogfooding TFS</title><link>http://blogs.msdn.com/b/bharry/archive/2007/02/11/managing-quality-part-4-stress-testing.aspx#1811777</link><pubDate>Mon, 05 Mar 2007 22:38:26 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1811777</guid><dc:creator>Jeff Beehler's Blog</dc:creator><description>&lt;p&gt;I've written a few times about our usage of TFS while we develop newer versions of Visual Studio and&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=1811777" width="1" height="1"&gt;</description></item><item><title>Managing Orcas Beta &amp;quot;exit criteria&amp;quot; by dogfooding TFS</title><link>http://blogs.msdn.com/b/bharry/archive/2007/02/11/managing-quality-part-4-stress-testing.aspx#1811567</link><pubDate>Mon, 05 Mar 2007 21:54:41 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1811567</guid><dc:creator>Jeff Beehler's Blog</dc:creator><description>&lt;p&gt;I've written a few times about our usage of TFS while we develop newer versions of Visual Studio and&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=1811567" width="1" height="1"&gt;</description></item><item><title>re: Managing Quality (part 4) - Stress Testing</title><link>http://blogs.msdn.com/b/bharry/archive/2007/02/11/managing-quality-part-4-stress-testing.aspx#1718507</link><pubDate>Mon, 19 Feb 2007 23:42:45 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1718507</guid><dc:creator>mlevison</dc:creator><description>&lt;p&gt;Lacking trackbacks I'm abusing the comment mechanism. This post was featured in the most recent Carnival of the Agilists: &lt;a rel="nofollow" target="_new" href="http://www.notesfromatooluser.com/2007/02/carnival_of_the.html"&gt;http://www.notesfromatooluser.com/2007/02/carnival_of_the.html&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=1718507" width="1" height="1"&gt;</description></item><item><title>VSTS Links - 02/14/2007</title><link>http://blogs.msdn.com/b/bharry/archive/2007/02/11/managing-quality-part-4-stress-testing.aspx#1676600</link><pubDate>Wed, 14 Feb 2007 17:48:55 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1676600</guid><dc:creator>Team System News</dc:creator><description>&lt;p&gt;Adam Singer on Grep'ing Groups. Brian Harry on Managing Quality (part 4) - Stress Testing. AngelaB...&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=1676600" width="1" height="1"&gt;</description></item><item><title>re: Managing Quality (part 4) - Stress Testing</title><link>http://blogs.msdn.com/b/bharry/archive/2007/02/11/managing-quality-part-4-stress-testing.aspx#1661255</link><pubDate>Mon, 12 Feb 2007 17:02:31 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1661255</guid><dc:creator>Brian Harry MS</dc:creator><description>&lt;p&gt;It depends somewhat on the nature of the &amp;quot;code&amp;quot; here. &amp;nbsp;To the degree that you are relying on SQL Server to do the work, you get the advantage of the rigorous stress testing they have done and don't need to worry quite as much about it yourself.&lt;/p&gt;
&lt;p&gt;That said, I'd look at creating a program that could randomly and incrementally populate the source system with data and run my ETL over and over for many hours. &amp;nbsp;Among other things, this will help you determine if you have any resource leaks in the ETL process.&lt;/p&gt;
&lt;p&gt;Brian&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=1661255" width="1" height="1"&gt;</description></item><item><title>re: Managing Quality (part 4) - Stress Testing</title><link>http://blogs.msdn.com/b/bharry/archive/2007/02/11/managing-quality-part-4-stress-testing.aspx#1654294</link><pubDate>Mon, 12 Feb 2007 00:14:56 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1654294</guid><dc:creator>yoyo</dc:creator><description>&lt;p&gt;If it's a database system that extracts data from other sources, regarding ETL part, what will you define for stress test and how will you implement the stress test? Thanks.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=1654294" width="1" height="1"&gt;</description></item></channel></rss>