lv123
20-10-2009, 08:28
Hi, I was wondering if its possible to have nested or dependent item checks similar to what we can do in "web scenarios".
e.g
Step1: Check if LDAP daemon is running
Step2: If yes, check if we can Bind to LDAP
Step3: If yes, check if we can search LDAP... etc
So if the check in Step1 returns false, we don't bother doing the next two checks.
Also, in web scenarios (or any item check for that matter) is it possible to use the results of an existing check in another scenario to prevent doubling up on http requests or checks?
e.g
Scenario1-
Step1: Check web application1 front page
Step2: Check backend page
Scenario2-
Step1: Check web application2 front page
Step2: Check backend page
Both web applications use the same backend page but Step2 really only needs to be done once. Yes, we could put this all into one scenario but since they are two separate web applications its nice to logically separate them incase we want separate stats/triggers/actions performed on each scenario.
e.g
Step1: Check if LDAP daemon is running
Step2: If yes, check if we can Bind to LDAP
Step3: If yes, check if we can search LDAP... etc
So if the check in Step1 returns false, we don't bother doing the next two checks.
Also, in web scenarios (or any item check for that matter) is it possible to use the results of an existing check in another scenario to prevent doubling up on http requests or checks?
e.g
Scenario1-
Step1: Check web application1 front page
Step2: Check backend page
Scenario2-
Step1: Check web application2 front page
Step2: Check backend page
Both web applications use the same backend page but Step2 really only needs to be done once. Yes, we could put this all into one scenario but since they are two separate web applications its nice to logically separate them incase we want separate stats/triggers/actions performed on each scenario.