La liste de diffusion est fermée depuis juillet 2022, mais sert toujours d'archive d'informations sur QF-Test.
Cependant, si vous souhaitez rester informé des nouveautés concernant QF-Test, vous pouvez simplement vous abonner à la newsletter :
abonner à la newsletter
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [QF-Test] Wrong thread events error level to warning
Hello Krati, as stated in the below exerpt from the QF-Test manual, the option OPT_PLAY_WRONG_THREAD_ERROR_LEVEL requires an 'SUT script' (not a 'Server script'). To check an option value, use rc.getOption(). Best regards, Robert --On Donnerstag, April 25, 2013 12:36:38 +0000 "Rahkola, Katri (NSN - FI/Tampere)" <katri.rahkola@?.com> wrote: 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 -- Get the most out of QF-Test - through training directly from the authors * via webinar http://www.qfs.de/en/info/OnlineTraining_QF-Test.pdf * here at QFS http://www.qfs.de/en/info/Training_QF-Test.pdf ------------------------------------------------------------------------ QFS Support - Robert Lahmer Quality First Software GmbH http://www.qfs.de Tulpenstr. 41 Tel: +49 8171 38648-20 DE-82538 Geretsried Fax: +49 8171 38648-16 GF: Gregor Schmid, Karlheinz Kellerer HRB München 140833
|
1. Cookies fonctionnels
Nous utilisons des cookies fonctionnels pour garantir la fonctionnalité de base du site web.
2. Cookies de performance et de statistique
Nous utilisons Matomo pour analyser et améliorer notre site web. Des cookies permettent une collection anonyme des informations qui nous aident à vous offrir un visite clair et facile à utiliser de nos pages web.
This cookie contains a unique, pseudonymized visitor ID internal to Matomo for recognizing repeat visitors.
This cookie is used to track from which website the anonymized user proceeded to any page or sub-page.
The Matomo session cookie is used to track the visitor's page requests during the session. The cookie is automatically deleted at the end of each session (website visit), at the latest after one day.
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.