Mailing list - Entries of 2006


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [qftestJUI] badVariableSyntaxException


  • Subject: Re: [qftestJUI] badVariableSyntaxException
  • From: Gregor Schmid <Gregor.Schmid@?.de>
  • Date: 10 Jan 2006 19:45:11 +0100

Hello Huawei,

$(...) in parameters is expanded normally. If the exception is
BadVariableSytaxException, something is probably wrong with the line
you're using, a missing ')' or s.th. like that.

If you can't find it, please send me your suite and I'll take a look.

By the way, is MY_HOME defined as a qftestJUI variable or is it an
environment variable defined at operating system level?

Best regards,
    Greg

Huawei Luo <hluo@?.com> writes:

> Hi, anybody could help with this? I have a Java SUT client node, the
> parameter Executable is a classpath, so I have two lines there like:
> -classpath
> jar1;jar2
> 
> for the list of jar files, I have a variable there, say, the variable
> is : MY_HOME, then that line becomes:
> $(MY_HOME)/jar1;$(MY_HOME)/jar2
> 
> but qftestJUI keeps complaining with "badVariableSyntaxException", it
> stops complaining when I use rc.lookup("MY_HOME"), but I found this is
> not expanded  to the value of MY_HOME, while the variable is expanded
> in all other nodes. Guess variable is allowed here??? Any help with
> this? Because I run my tests in a automated framework and all the test
> cases might be moved to different places, so I have to use variables
> here.
> 
> Thanks very much
> 
> Huawei

-- 
Gregor Schmid                                Gregor.Schmid@?.de
Quality First Software GmbH                     http://www.qfs.de
Tulpenstr. 41                                Tel: +49 8171 919870
DE-82538 Geretsried                          Fax: +49 8171 919876


Videos Downloads Documentation Buy Free Trial