List Icon
Mailing list Archive

2019 up to July 2022 | 20182017  |  2016  2015 2014 | 2013

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] How to check the status label text after clicking on a button

  • Subject: [QF-Test] How to check the status label text after clicking on a button
  • From: "Liu, Kevin (DPTI)" <Kevin.Liu@?.au>
  • Date: Tue, 29 Aug 2017 08:09:15 +0000
  • Delivered-to: qftest-list@?.net

Hi everyone,


I have a search button to do a person query based on last name, by default, say the status label A has a text ‘please input last name’, when I entered a non-existing last name and clicked the search button, the GUI panel rendered text ‘No records found’ in label A.

But when QF-Test executed the check text node (as shown in disabled state below) or try and catch fragment, it popped up an error stating ‘An event was triggered outside the AWT Event Dispatch Thread’ and Jython Server script wasn’t executed at all.


So is it possible to check the label text dynamically based on different searching criteria? If so, how to check the label text?




Jython Server script

rc.check(0, "No records found label invisible", level=rc.ERROR, report=True, nowrap=False)


An event was triggered outside the AWT Event Dispatch Thread.


This is not a bug in QF-Test, rather the opposite: Herewith QF-Test

informs you about a potentially very serious problem in your application.

Please notify the developers of the application and include the

event and stack-trace information provided below.


For further information, please see section 31.3.3 of the QF-Test manual,

specifically the documentation for the option

Replay->Events->How to handle events coming from the wrong thread.


Details for developers:


Event: javax.swing.event.ChangeEvent[source=javax.swing.DefaultButtonModel@5969af31]


Stack-trace: java.lang.Exception: Stack dump

                at de.qfs.lib.util.Misc.getCurrentStackTrace(

                at de.qfs.apps.qftest.client.awt.s.a(SourceFile:2272)

                at de.qfs.apps.qftest.client.awt.s.stateChanged(SourceFile:1750)

                at javax.swing.DefaultButtonModel.fireStateChanged(

                at javax.swing.DefaultButtonModel.setEnabled(

                at javax.swing.AbstractButton.setEnabled(

                at trelis.presentation.client.AddClientWizard.enableNextButton(

                at trelis.presentation.client.AddClientSearchPanelController.doSearch(

                at trelis.presentation.client.AddClientSearchPanel$1.doInBackground(

                at trumps.presentation.component.swing.TaskActionListener$







                at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:238)


                at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:393)

                at scala.concurrent.forkjoin.ForkJoinTask.doExec(

                at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(

                at scala.concurrent.forkjoin.ForkJoinPool.runWorker(






PNG image