Mailing list - Entries of 2005

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

Re: [qftestJUI] waitFor String in Terminal

  • Subject: Re: [qftestJUI] waitFor String in Terminal
  • From: Bastian Bowe <Bastian.Bowe@?.de>
  • Date: Wed, 21 Sep 2005 10:05:38 +0200

Thanks Gregor,

I had a bug in my script. My script was

out = rc.lookup("qftestJUI","client.output.$(client)")
if out.find("$(outString)") > 0:
  raise UserException("$(outString) was FOUND in $(client)")

the problem is the check on out.find(). I have to compare ">= 0" as our
expected value is returned without ant output in advance...



Gesendet von: qftestjui-list-bounces@?.de
20.09.2005 20:01

Bastian Bowe <Bastian.Bowe@?.de>
Re: [qftestJUI] waitFor String in Terminal

Hi Bastian,

if you see the output in the terminal, you should also be able to
access it with ${qftestJUI:client.output.<nameOfClient>}. What does
the run-log say? It should help you find out whether the output is
actually missing or whether there's a bug in your script.

Best regards,

Bastian Bowe <Bastian.Bowe@?.de> writes:

> Hi,
> we're using LaunchAnywhere from Zero G for our product distribution
> version. How to wait for a string on the console in that case? I've read

> and i get the
> solutions working for output of a Java class, ant builts started from
> batchfiles etc.
> LaunchAnywhere creates a OurProduct.exe. The .exe uses a OurProduct.lax
> file to setup classpath and starts the (in qftest instrumented) JRE.
> Output to console is displayed on the qftest terminal area. Finding the
> outputstring fails.
> How to find output strings in that case?
> Kind regards
> Bastian
Gregor Schmid                                Gregor.Schmid@?.de
Quality First Software GmbH           
Tulpenstr. 41                                Tel: +49 8171 919870
DE-82538 Geretsried                          Fax: +49 8171 919876
qftestJUI-list mailing list