Strategy to have SWTBot test cases working accross different windowing systems [message #556592] |
Wed, 01 September 2010 23:03 |
Eclipse User |
|
|
|
Originally posted by: manu_ny.optimum.net
Hi,
We have some SWTBot test cases that work well on MacOSX. Once deployed
on a testing machine which happens to be a linux machine with TWM window
manager, suddenly all our test cases fail because it seems that new
shell(s) do not get the focus or the activation they should. Is the only
way to get the test cases to work across different windowing systems is
to force some calls to SWTBot "activate" method? No chance that such
internals be encapsulated in the library?
On a side note, we get such exception from SWTBot:
org.eclipse.swtbot.swt.finder.exceptions.WidgetNotFoundExcep tion: The w
idget was null.
at
org.eclipse.swtbot.swt.finder.widgets.AbstractSWTBot.< ;init>(AbstractSWTBot.java:96)
at
org.eclipse.swtbot.swt.finder.widgets.AbstractSWTBotControl. <init>(AbstractSWTBotControl.java:47)
at
org.eclipse.swtbot.swt.finder.widgets.SWTBotShell.<in it>(SWTBotShell.java:49)
at
org.eclipse.swtbot.swt.finder.widgets.SWTBotShell.<in it>(SWTBotShell.java:38)
at
org.eclipse.swtbot.swt.finder.SWTBotFactory.activeShell(SWTB otFactory.java:341)
at
org.eclipse.swtbot.swt.finder.SWTBotFactory.menu(SWTBotFacto ry.java:208)
at
org.eclipse.swtbot.swt.finder.SWTBotFactory.menu(SWTBotFacto ry.java:198)
Would it be possible to add a bit more context to some of SWT
exceptions? The widget was null is rather limited. For instance, just
adding the name of the shell the system is trying to access would be a
big help for debugging.
Thanks.
Emmanuel.
|
|
|
|
Powered by
FUDForum. Page generated in 0.02434 seconds