4:04 p.m.
Hi all,
Someone reported an issue in SWTBot 2.1.0 using Kepler M6 because of an
API change in hamcrest. See
https://bugs.eclipse.org/bugs/show_bug.cgi?id=404346 (release train
ships a newer version of hamcrest).
It affects only *some* SWTBot methods, and most of SWTBot is still
working (tests report 22 failure for 413 tests
https://hudson.eclipse.org/hudson/view/SWTBot/job/swtbot-tycho-e4.2/ ).
In case you notice that our tests fail because of this issue, please
tell me so I'll raise the priority of this bug and try to get it fixed ASAP.
Cheers,
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
11:40 a.m.
New subject: SWTBot 2.1 is available... should we upgrade?
Hi Mickael,
Today we started testing JBT 4.1.0.Alpha2 and noticed that this is quite a big problem for
us. Most of our tests fail with something like this:
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NoSuchMethodError:
org.hamcrest.core.IsAnything.any(Ljava/lang/Class;)Lorg/hamcrest/Matcher;)
at org.eclipse.swt.SWT.error(SWT.java:4392)
at org.eclipse.swt.SWT.error(SWT.java:4307)
Right now we don't know how to overcome this in automated jenkins test runs - swtbot
always takes the newest version of hamcrest from the kepler platform, so even adding older
hamcrest repo wouldn't help here. Do you have any suggestion for us? :)
Also, what will be the fix in SWTBot? If you fix it to work with the new hamcrest, it
won't work with the older version, right? So this new swtbot will not be able to work
with Juno with older hamcrest then?
Thanks,
Martin
On 28. 3. 2013, at 16:04, Mickael Istria <mistria(a)redhat.com> wrote:
Hi all,
Someone reported an issue in SWTBot 2.1.0 using Kepler M6 because of an API change in
hamcrest. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=404346 (release train ships a
newer version of hamcrest).
It affects only *some* SWTBot methods, and most of SWTBot is still working (tests report
22 failure for 413 tests
https://hudson.eclipse.org/hudson/view/SWTBot/job/swtbot-tycho-e4.2/ ).
In case you notice that our tests fail because of this issue, please tell me so I'll
raise the priority of this bug and try to get it fixed ASAP.
Cheers,
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Martin Malina
JBoss QA Engineer
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno, Czech Republic
Tel.: +420 532 294 265
11:52 a.m.
New subject: SWTBot 2.1 is available... should we upgrade?
On 04/08/2013 11:40 AM, Martin Malina wrote:
Hi Mickael,
Today we started testing JBT 4.1.0.Alpha2 and noticed that this is
quite a big problem for us. Most of our tests fail with something like
this:
org.eclipse.swt.SWTException: Failed to execute runnable
(java.lang.NoSuchMethodError:
org.hamcrest.core.IsAnything.any(Ljava/lang/Class;)Lorg/hamcrest/Matcher;)
at org.eclipse.swt.SWT.error(SWT.java:4392)
at org.eclipse.swt.SWT.error(SWT.java:4307)
This is
https://bugs.eclipse.org/bugs/show_bug.cgi?id=404346
Right now we don't know how to overcome this in automated jenkins
test
runs - swtbot always takes the newest version of hamcrest from the
kepler platform, so even adding older hamcrest repo wouldn't help
here. Do you have any suggestion for us? :)
That's because Kepler M6 ships
Junit 4.10 which depends on Hamcrest 1.3.
SWTBot builds against Hamcrest 1.1 and Hamcrest has API breaks between
1.1 and 1.3.
The general workaround is to make sure that you test bundle will resilve
to Junit < 4.10 and hamcrest 1.1. This can be achieved by setting strict
version range in your test bundle MANIFEST for org.junit and
org.hamcrest, so Tycho will use the older ones, and test should work.
Also, what will be the fix in SWTBot? If you fix it to work with the
new hamcrest, it won't work with the older version, right? So this new
swtbot will not be able to work with Juno with older hamcrest then?
Cf bug
comments.
The fix consist in using different way to instantiate Matchers.
Fortunately, there are still some public constructors that we can use
directly and that are available with hamcrest 1.1 and 1.3.
I'm totally opposed to break backward-compatibility in SWTBot. Since
you're having trouble because of this bug, I'll try to fix it soon. Any
help is welcome.
Cheers,
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
4036
days inactive
4047
days old
jbosstools-dev@lists.jboss.org
2 comments
2 participants
participants (2)
-
Martin Malina -
Mickael Istria