The mailing list has been closed since July 2022, but continues to serve as an archive of information about QF-Test.
But if you want to stay informed about news about QF-Test, you can simply
Subscribe to Newsletter
To get up-to-date information about each release - including minor releases - you can
subscribe to the RSS feed or follow us on social media.
Alternatively, QF-Test also provides release information itself.
Another source of information is our blog, where there are current articles on general topics, on the company QFS and also various "how-tos"
subscribe to blog
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [QF-Test] Minor usability suggestions
Hello Jile, I cannot reproduce your repaint issue. Typically such issues are caused by a problem somewhere between Windows and Java. Please check whether your graphics drivers are up-to-date - many such issues were resolved by a driver update. If this problem still persists after updating the drivers, please get back directly to our support. Regarding your suggestion "to allow SUT script to run even if the client is not connected": You cannot execute something in a process that doesn't exists. But it's not needed, since that is what Jython or Groovy 'Server Script' nodes are for. No need for a batch client. In fact, you should never use an 'SUT script' node if the same can be achieved in a 'Server script', i.e. whenever you don't need to interact directly with the SUT. You can convert an 'SUT Script' node to a 'Server script' via a right-click -> Convert node into -> Server Script. Last but not least the story about empty script nodes. Possible, of course, but what for? The most likely reason for having an empty script is an error. If a user has forgotten to input the script, he will be glad that he gets informed. Whenever I just want to add a script and implement its content later I simply enter a sharp (#) sign (or // for Groovy), then press [Ctrl-Enter]. Greetings, Yann Am 17.10.2014 16:27, schrieb Jile Gao:
Hello, Just some minor bugs\usability suggestions. I am in Windows 7. When I try to resize QF-Test to be taller, I drag the top edge of the window to the top of the screen. Windows then automatically pulls the bottom edge to the bottom of the screen. This makes the window become the entire height of the screen. However QF-Test does not fill the bottom part. It is black down there. This is a minor bug. The workaround is to then resize again from the left or right edge. We use Jython SUT script a lot. If the Jython script does not refer to anything in the client, theoretically the client does not need to be connected if we want to run something before launching the SUT in order to prepare. This is impossible in QF-Test. The workaround is to create a batch script which runs the Jython script separately, then run the rest of the test using QF-Test, but this is cumbersome. The suggestion is to allow SUT script to run even if the client is not connected. An empty Jython SUT script is a valid script, but QF-Test does not allow an empty script. The workaround is to put something there that does nothing e.g. an import statement, a null statement, etc. The suggestion is to allow empty SUT scripts. _______________________________________________ qftest-list mailing list qftest-list@?.de http://www.qfs.de/mailman/listinfo/qftest-list
-- _______________________________________________________________ Get the most out of QF-Test - Support directly from the authors * Training & consulting: www.qfs.de/en/qftest/training.html * Phone & email support: www.qfs.de/en/qftest/support.html _______________________________________________________________ Yann Felix Spöri Support E: support@?.de T: +49 (0)8171 38648-20 F: +49 (0)8171 38648-16 Quality First Software GmbH | www.qfs.de Tulpenstr. 41 | 82538 Geretsried | Germany GF Gregor Schmid, Karlheinz Kellerer HRB München 140833