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] [QF-Test] Wrong thread events error level to warning
Hi, I’m trying to change wrong thread events error level to warning with Jython Server script from Event Handling options, but not succeeding. This is how I tried (the whole script): val = Options.VAL_PLAY_THREAD_LEVEL_WARNING rc.setOption(Options. OPT_PLAY_WRONG_THREAD_ERROR_LEVEL, val) Should there be something else also because this is not working? I checked the options from your Manual from this section: How to handle events coming from the wrong thread (System) SUT script name: OPT_PLAY_WRONG_THREAD_ERROR_LEVEL Possible Values: VAL_PLAY_THREAD_LEVEL_WARNING, VAL_PLAY_THREAD_LEVEL_ERROR, VAL_PLAY_THREAD_LEVEL_EXCEPTION It is a rather common mistake in Swing based Java applications to access GUI components from the wrong thread. Since Swing is
not thread-safe, such calls may only be made from the AWT event dispatch thread. Otherwise the potential consequences are race conditions, leading to very subtle and hard-to-debug errors, or deadlocks, freezing the application and making it unusable. Background
information about this topic is available from http://download.oracle.com/javase/tutorial/uiswing/concurrency/index.html , specifically the sections on "Initial Threads" and "The Event Dispatch Thread". When QF-Test registers an event on a thread other than the AWT event dispatch thread it issues an error message including a
stack trace which can be useful in fixing the problem. This set of options defines the severity of the message, whether to perform strict checking and a maximum for the number of messages to log. The possible choices for the option "Error level" are "Error" and "Warning". We strongly suggest that you keep the default setting
of "Error" and make sure that such problems are fixed sooner rather than later because they represent a serious risk. Another question is that how can I check the current value of ‘Options. OPT_PLAY_WRONG_THREAD_ERROR_LEVEL’? I have version 3.5.0 from QFtest. Thanks and Br, Katri
|
1. Functional cookies
We use functional cookies to ensure the basic functionality of the website.
2. Performance and statistic cookies
We use Matomo for analyzing and optimizing our website. Cookies permit an anonymous collection of information that help us offering you a clear and user-friendly visit of our web pages.
This cookie contains a unique, pseudonymized visitor ID internal to Matomo for recognizing returning visitors.
This cookie is used to track from which website the anonymized user proceeded to our website.
The Matomo session cookie is used to track the visitor's page requests during the session.
is created and should be then directly deleted (used to check whether the visitor’s browser supports cookies).
short lived cookies used to temporarily store data for the visit.
short lived cookies used to temporarily store data for the visit.
