AWESOME! I had no idea that I could do the variable testing in a <nop>. This approach is working for me, however, I guess in the version that I have I must use integer labels instead of text ones, unless the example you provided was just to show me how to get an implementation of if-then-else with next & test.
Thanks very much Charles! Dave Adams. This email message and any attachments may be confidential and/or privileged to Nortel. If the reader of this message is not the intended recipient, you are hereby notified that any use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to this message or by calling the sender and then destroying all copies of the message and any attachments. -----Original Message----- From: Charles P Wright [mailto:[EMAIL PROTECTED] Sent: Monday, November 03, 2008 2:41 PM To: Adams, David (CAR:3P33) Cc: [email protected] Subject: Re: [Sipp-users] SIPP Conditional Branching with If-Then-Else Variable Testing if you set the variable you can do something like: <nop next="ifclause" test="variable" /> <!-- else cluase stuff goes here --> <nop next="endif" /> <!-- if clause stuff goes here --> <label id="endif" /> Charles "David Adams" <[EMAIL PROTECTED]> wrote on 11/03/2008 12:41:41 PM: > Hi, > I'm trying to build error-handling into a scenario with conditional- > branching and variable testing. With the latest stable version of > SIPP, I know I have the ability to use regexp to populate variables, > and then in some actions such as <send> / <receive> I can test a > variable and jump to a label after the <send> or <receive> action has > been executed. > What I'd like to be able to do is setup a variable, then based on > whether the variable is set or not, then go to a different place in my > scenario file. > So far I have not been able to figure how to do this, if it's even > possible. SIPP seems to support the "Else" part of the If-Then-Else > with the variable testing and next arguments as part of <send> and > <receive> operations. > 1. Is there a way to do this in SIPP3.x? If not, > 2. Could you direct me to the most logical place in the code that I > would need to modify to build this feature? > Thanks, > Dave Adams. > ------------------------------------------------------------------------ - > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Sipp-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/sipp-users ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
