2.1.1 is a more recent build; might be worth trying that, or indeed
the current nightly build.
Are there any warnings/errors in jmeter.log?
Might be worth wrapping the code in __log(), i.e.
${__log('${query}' != '---')}
This should log the string to jmeter.log, and then return it for
JavaScript to execute.
S.
On 18/10/05, Jelmer de Haas <[EMAIL PROTECTED]> wrote:
> I use the following in the If controller
>
> '${query}' != '---'
>
> The ${query} is coming from a column in a .cvs file.
>
> If I use
>
> '${query}' == '---'
>
> the expected (but incorrect) actions are executed. To my knowledge in
> javascript the != should be the correct statement for IS NOT.
>
> I use a 2.1-20050914 build. Should I upgrade perhaps?
>
> Jelmer
>
> -----Original Message-----
> From: sebb [mailto:[EMAIL PROTECTED]
> Sent: dinsdag 18 oktober 2005 12:22
> To: JMeter Users List
> Subject: Re: IF controller NOT?
>
>
> If controller requires valid JavaScript.
> Remember to quote strings.
>
> S.
> On 18/10/05, Jelmer de Haas <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I have a small problem with my IF controller. I want to use an IS NOT
> > condition, but cannot find anything specific in the manual. Tried <>,
>
> > !=, and NOT but they don't seem to work.
> >
> > What should I use here?
> >
> > Thanks,
> > Jelmer de Haas
> >
> >
> >
>
> ---------------------------------------------------------------------
> 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]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
