I've removed all references to the HTTP stuff in the test plan so that it
looked like this:
Thread Group
|
|__ JDB Connection Configuration
|
|__ View Results Tree
|
|__ Simple Controller
|
|__ JDBC Request (make sure consumer exists in db)
|
|__ If Controller (if consumer exists)
|
|__ JDBC Request (check for valid subscription)
|
|__ If Controller (if subscription exists)
|
|__ JDBC Request (remove subscription)
And that works fine (i.e. all 3 JDBC requests are executed). So, I don't
think it's how the if controller is set up. I've only dabbled in JMeter
before and this is my first plan that uses JDBC requests. I was wondering
if it's the combination of the two types of requests within the same thread
group that was causing the issues. Maybe JMeter isn't meant to have "mixed"
test plans?
Shelli
-----Original Message-----
From: sebb [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 25, 2006 11:42 AM
To: JMeter Users List
Subject: Re: Request Not Executing
On 25/04/06, Shelli D. Orton <[EMAIL PROTECTED]> wrote:
> Hello All,
>
> I am writing a functional web application test which includes both JDBC
and
> HTTP requests. Before I can do the HTTP requests, I need to make sure the
> database is set up correctly. My plan looks something like this:
>
> Thread Group
> |
> |__ JDB Connection Configuration
> |
> |__ HTTP Request Defaults
> |
> |__ HTTP Header Manager
> |
> |__ View Results Tree
> |
> |__ Simple Controller
> |
> |__ JDBC Request (make sure consumer exists in db)
> |
> |__ If Controller (if consumer exists)
> |
> |__ JDBC Request (check for valid subscription)
> |
> |__ If Controller (if subscription exists)
> |
> |__ JDBC Request (remove subscription)
> |
> |__ HTTP Request (display subscription form)
> |
> |__ HTTP Request (submit subscription form)
>
>
> In my View Results Tree I see the first JDBC request (ensure consumer
> exists) and the first HTTP request (display subscription form). I do not
> see the second JDBC request (and subsequently the third JDBC request) and
do
> not know why. The test that the consumer exists must pass because the
HTTP
> requests are nested in that controller (as well as the other JDBC
requests).
> The second HTTP request is not executed because the validation of the
first
> HTTP request fails (consumer already has a subscription).
>
> As I was building up the test plan, I originally had the JDBC and HTTP
> requests in separate thread groups (and set the number of threads for the
> HTTP one to zero so it would not execute). However, now that they are in
> the same thread group, it skips over the second JDBC request. Does anyone
> have any thoughts on why this would be?
>
Most likely the If Controller condition is not doing what you think.
Are there any relevant messages in jmeter.log (or possibly console)?
What happens if you remove the nested If controller?
A good way of testing the logic of a Test Plan is to use the Java Sampler.
If all fails, and you think there is a bug, please see:
http://wiki.apache.org/jakarta-jmeter/FaultReporting
S.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
