Error seen everytime I start AUT from Jubula [message #1724604] |
Wed, 24 February 2016 15:49  |
Eclipse User |
|
|
|
I am new to Jubula and successfully ran through the samples and am able to start writing test on our own swing application.
I noticed this error everytime I start the AUT:
2016-02-16 12:43:52.542 [Thread-7] ERROR o.e.j.r.s.c.AUTSwingHierarchy - Method called outside of the dispatch thread. This may indicate a potential error in the AUT.
java.lang.Exception: null
at org.eclipse.jubula.rc.swing.components.AUTSwingHierarchy.checkDispatchThread(AUTSwingHierarchy.java:1018) [org.eclipse.jubula.rc.swing_4.0.0.201602030740.jar:na]
at org.eclipse.jubula.rc.swing.components.AUTSwingHierarchy.name(AUTSwingHierarchy.java:757) [org.eclipse.jubula.rc.swing_4.0.0.201602030740.jar:na]
at org.eclipse.jubula.rc.swing.components.AUTSwingHierarchy.addToHierarchyDown(AUTSwingHierarchy.java:695) [org.eclipse.jubula.rc.swing_4.0.0.201602030740.jar:na]
at org.eclipse.jubula.rc.swing.components.AUTSwingHierarchy.addComponent(AUTSwingHierarchy.java:465) [org.eclipse.jubula.rc.swing_4.0.0.201602030740.jar:na]
at org.eclipse.jubula.rc.swing.components.AUTSwingHierarchy.componentAdded(AUTSwingHierarchy.java:414) [org.eclipse.jubula.rc.swing_4.0.0.201602030740.jar:na]
at java.awt.Container.processContainerEvent(Container.java:2262) [na:1.8.0_65]
at java.awt.Container.processEvent(Container.java:2233) [na:1.8.0_65]
at java.awt.Component.dispatchEventImpl(Component.java:4891) [na:1.8.0_65]
at java.awt.Container.dispatchEventImpl(Container.java:2294) [na:1.8.0_65]
at java.awt.Component.dispatchEvent(Component.java:4713) [na:1.8.0_65]
at java.awt.Container.addImpl(Container.java:1138) [na:1.8.0_65]
at java.awt.Container.add(Container.java:417) [na:1.8.0_65]
at com.xenos.framework.gui.dock.plaf.BasicDockingPortUI.showDockable(BasicDockingPortUI.java:450) [Xenos-framework-gui.jar:16.0.BETA.01.]
at com.xenos.framework.gui.dock.plaf.BasicDockingPortUI.propertyChange(BasicDockingPortUI.java:165) [Xenos-framework-gui.jar:16.0.BETA.01.]
at java.beans.PropertyChangeSupport.fire(PropertyChangeSupport.java:335) [na:1.8.0_65]
at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:327) [na:1.8.0_65]
at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:263) [na:1.8.0_65]
at java.awt.Component.firePropertyChange(Component.java:8430) [na:1.8.0_65]
at com.xenos.framework.gui.dock.JDockingPort.setSelectedDockable(JDockingPort.java:120) [Xenos-framework-gui.jar:16.0.BETA.01.]
at com.xenos.framework.gui.dock.JDockPane.activateDockable(JDockPane.java:231) [Xenos-framework-gui.jar:16.0.BETA.01.]
at com.xenos.framework.gui.dock.JDockPane.activateDockable(JDockPane.java:239) [Xenos-framework-gui.jar:16.0.BETA.01.]
at com.xenos.framework.gui.dock.JDockPane.activateDockable(JDockPane.java:239) [Xenos-framework-gui.jar:16.0.BETA.01.]
at com.xenos.framework.gui.dock.JDockPane.setActiveDockable(JDockPane.java:75) [Xenos-framework-gui.jar:16.0.BETA.01.]
at com.xenos.framework.gui.DockingManager.setSelected(DockingManager.java:208) [Xenos-framework-gui.jar:16.0.BETA.01.]
at com.xenos.framework.gui.environment.EnvironmentManager$InitEnvironmentThread.doTask(EnvironmentManager.java:1784) [Xenos-framework-gui.jar:16.0.BETA.01.]
at com.xenos.framework.gui.dialog.ProgressThread.run(ProgressThread.java:39) [Xenos-framework-gui.jar:16.0.BETA.01.]
I checked with our developers and as far as they are concerned we only use the Java swing components so there should be nothing that would run outside the Dispatch thread.
I also noticed that I get a ClassCastException when I attempt to store the JMenuItem property (which appears on Object Mapping) like text or label. Not sure if this is related but that is what got me started researching into the log files to find out why I cannot capture the property.
Here is the basic information:
Jubula standalone versions 8.2.0.021 and 8.2.2.50
AUT is a java app that uses the swing toolkit. I used a modified batch file to start the AUT from Jubula.
JVM - Java 1.7.0.45 64 bit
OS - Windows 7 64 bit
Please let me know if you need more information.
Thank-you!
Lynette H.
|
|
|
|
|
|
|
|
Re: Error seen everytime I start AUT from Jubula [message #1725133 is a reply to message #1725087] |
Tue, 01 March 2016 02:10   |
Eclipse User |
|
|
|
Hi Lynette,
That the properties can't be checked is not very well handled, but it is actually not supported currently for menu bars. It's never come up before 
To verify whether something exists before clicking on it, I'd probably build a generic module that looked like this:
- "Checked select from menu" [TEXTPATH]
-- ubm: check existence of entry by textpath [=TEXTPATH]
-- ubm select entry by textpath [=TEXTPATH]
The =TEXTPATH means that the parameter is referenced, so the whole module can be reused with different textpaths.
However, from a test automation perspective, it's worth considering what the information about existence is worth: the select action will fail with an action error if the entry is not there. If there's something you can do when the check fails to ensure that the menu item appears, then it can be worth checking. Otherwise, you may not need the action.
I've prodded the team again about the other error. We moved offices last week, so it may have gone under a pile of boxes 
Best regards,
Alex
|
|
|
|
Powered by
FUDForum. Page generated in 0.07930 seconds