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?
All help greatly appreciated,
Shelli
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
