Mailingliste - Einträge 2006

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

Re: [qftestJUI] Problem with "Stop client" node

  • Subject: Re: [qftestJUI] Problem with "Stop client" node
  • From: Gregor Schmid <Gregor.Schmid@?.de>
  • Date: 20 Jun 2006 10:48:29 +0200

Hello Jiri,

strange problem, but let's see...

- You say that after the "Stop client" node the process is still
  alive, but the menu "Stop all clients" terminates it. What if you
  reverse the order? Set a breakpoint on the "Stop client" node, then
  use "Stop all clients" first. What's the status? If the process also
  is alive, does the "Stop client" node kill it now? In that case,
  what about two times "Stop all clients" or executing "Stop client"
  two times?

All of the above is based on the assumption that there may actually be
two processes involved.

One other thing to try is running qftestJUI with the -nodirectlaunch

And there is also the question of whether you're using the old
connection mechanism or the new one based on JDK instrumentation. If
your client doesn't have a GUI, do you need a connection at all or do
you just want to have the process running? Try instrumenting the JDK
and starting qftestJUI with -newconnect to force using the new

If you can't get it to work, please run qftestJUI from the command
line as

qftestJUI -dbg [possibly other options] > qf.log

Then run your test, most notably the start and stop client nodes and
send me the *.qrz run-log as well as the qf.log file with the
redirected output.

Best regards,

Jiri Kajaba <jkajaba@?.com> writes:

> Hello,
> when I worked with qftest version 1.06 everything was fine and I was
> happy :-). Now I use qftest version 1.08 and "Stop client" node
> doesn't work for me.
> My use case:
> 1)
> I have to start SUT in this weird way
> ----- sut starting script -----
> rem setting properties for normal execution
> ...
> rem setting additional properties for testing
> set QFTEST_HOME=C:\Program Files\qfs\qftest
> set QFTEST_JUI_HOME=%QFTEST_HOME%\qftestJUI-1.08.5
> set CLASSPATH=%CLASSPATH%;%QFTEST_JUI_HOME%\qflib\qftest_12.jar
> set CLASSPATH=%CLASSPATH%;%QFTEST_JUI_HOME%\qflib\qflib_12.jar
> set CLASSPATH=%CLASSPATH%;%QFTEST_JUI_HOME%\lib\pngencoder.jar
> set CLASSPATH=%CLASSPATH%;%QFTEST_JUI_HOME%\lib\jniwrapper.jar
> set CLASSPATH=%CLASSPATH%;%QFTEST_JUI_HOME%\lib\bsfengines.jar
> set QFTEST_PARAM_1="-Dqftest.home=%QFTEST_HOME%"
> "-DqftestJUI.home=%QFTEST_JUI_HOME%"
> set QFTEST_START_CLASS=de.qfs.apps.qftest.start.StartClient
> set QFTEST_PARAM_2=-serverhost %QFTEST_SERVER% -clientname %QFTEST_CLIENT%
> rem run sut
> ----- ----- -----
> 2)
> SUT was started and connected ("Wait for client to connect" node works fine)
> -> record components button is enabled (but it is not GUI application)
> 3)
> now I need to terminate client, but "Stop client" node is unable to stop SUT
> 4)
> if I use qftest's menu Clients -> Stop all, im able to stop SUT
> 5)
> qftest menu after SUT start
> ********************
> Clients -> 1. client_name ->
>   Show terminal ...
>   Show Jython terminal...
>   Stop
> qftest menu after "Stop client" call
> *************************
> Clients -> 1. client_name ->
>   Stop
> qftest menu after "Clients -> Stop all" execution
> ************************************
> Clients -> no active client
> Do you have any idea how to solve this problem. Or do you need more
> information? In the worst case, I can switch back to old version and
> never use better :-)
> Thanks.
> Jiri Kajaba

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