[Webtest] Turning WebTest tests into concurrent load tests.

Mon, 7 Apr 2008 11:07:35 +0200 (CEST)

This is a multi-part message in MIME format.

------=_NextPart_000_000F_01C8989F.95AACD40
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

I agree with both Marc and Siggi ;-) 

It depends on what you are trying to achieve with your load test.

When the goal is to load-test the *technical infrastructure*
(i.e. regardless of the deployed application) the Siggi's way
is the way to go.

When the goal is to load-test the *application* then I would follow
Marc's path. Let's face it: there is not much value in knowing 
that your appserver can handle n requests per second if half the
responses only report an exception because of concurrency issues
or resource locks in your app.

cheers
Dierk

------=_NextPart_000_000F_01C8989F.95AACD40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7036.0">
<TITLE>RE: [Webtest] Turning WebTest tests into concurrent load =
tests.</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>

I agree with both Marc and Siggi ;-) 
 
It depends on what you are trying to achieve with your load test. 
 
When the goal is to load-test the *technical infrastructure* 
(i.e. regardless of the deployed application) the Siggi's way 
is the way to go. 
 
When the goal is to load-test the *application* then I would follow 
Marc's path. Let's face it: there is not much value in knowing 
that your appserver can handle n requests per second if half the 
responses only report an exception because of concurrency issues 
or resource locks in your app. 
 
cheers 
Dierk

</BODY>
</HTML>
------=_NextPart_000_000F_01C8989F.95AACD40--