<?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 - functional test patterns</title>
 <link>http://www.testingreflections.com/taxonomy/view/or/47</link>
 <description></description>
 <language>en</language>
<item>
 <title>Multi-User Functional Testing</title>
 <link>http://www.testingreflections.com/node/view/6665</link>
 <description>In &lt;a href="http://www.stpmag.com/retrieve/stp-0802.htm"&gt;the February issue of Software Test &amp; Performance&lt;/a&gt; read Karen Johnson's article about multi-user testing (pp. 20-23). Karen writes about a very rare subject – functional multi-user testing. Should admit that I started to read with a thought "one more article about performance testing" – but soon realized that it is about quite different subject. And yes, indeed, without functional multi-user testing, most of errors mentioned in article will slip through (won't re-tell the article – it is available on-line, you can read it yourself). Some may be found during performance testing (probably the most severe like deadlocks – if they are in the typical scenarios you included in performance testing) – and you will need to trace them down to the source, and probably it will be much later down the cycle.</description>
<pubDate>Sun, 02 Mar 2008 15:11:17 -0600</pubDate></item>
</channel>
</rss>
