Community
Participate
Working Groups
"SWTBot":http://www.eclipse.org/swtbot is a great way to test the UI. It's now part of Eclipse.org, which makes me think that we should consider using it. I have experience with SWTBot and have found that it adds huge value to UI tests. While the SWTBot build is still somewhat immature, when it's easy to consume let's start using it. For an interesting read on SWTBot take a look at this article: "Eclipse GUI Testing Is Viable With SWTBot":http://greensopinion.blogspot.com/2008/09/eclipse-gui-testing-is-viable-with.html
That sounds great! I personally don't have any experience with SWTBot. David, would you be willing to contribute an examplatory UI test?
(In reply to comment #1) > That sounds great! I personally don't have any experience with SWTBot. David, > would you be willing to contribute an examplatory UI test? Of course! As soon as we can link in the SWTBot binaries, I can put together some tests that demonstrate typical test scenarios, such as clicking menus, opening editors, exercising wizards, etc. How does Mylyn normally consume 3rd party plug-ins, like Ant for example?
Ant is provided by the SDK. Other 3rd party bundles are included from the Orbit cvs. Is SWTBot available from an update site or from source?
(In reply to comment #3) > Ant is provided by the SDK. Other 3rd party bundles are included from the Orbit > cvs. Is SWTBot available from an update site or from source? Currently SWTBot is available from source, however they're still waiting for at least one dependency to make it into Orbit.
I'd be willing to contribute some tests and some basic structure for an initial framework that Mylyn can consume. In case Mylyn wishes to use SWTBot, I'd recommend that you start getting IP approval, since you'll be depending on hamcrest for writing SWTBot tests. Some links that may help: http://dev.eclipse.org/ipzilla/show_bug.cgi?id=2860 and https://dev.eclipse.org/ipzilla/show_bug.cgi?id=2907
(In reply to comment #5) > I'd be willing to contribute some tests and some basic structure for an initial > framework that Mylyn can consume. Ketan, that's fabulous! Perhaps Mylyn could be an exemplar for other Eclipse.org projects in adopting SWTBot. Looks like there may be some dependency issues with JUnit4 and hamcrest (bug 254608). Will this be a problem for us if we're consuming SWTBot and hamcrest using JUnit 3.x?
(In reply to comment #6) > Ketan, that's fabulous! Perhaps Mylyn could be an exemplar for other > Eclipse.org projects in adopting SWTBot. That's good to hear. > Looks like there may be some dependency issues with JUnit4 and hamcrest (bug > 254608). Will this be a problem for us if we're consuming SWTBot and hamcrest > using JUnit 3.x? It would not be a problem with either junit 3.8.x or 4.x. Part of hamcrest (v.1.1) is packaged in the upstream JUnit jar available from junit.org. This was made into a the JUnit bundle, the bundle exports the hamcrest packages as version 4.5, the same as the junit version. It should not be a problem as long as you're depending on a hamcrest bundle (v 1.1), and not depending on a particular package, since there may be no guarantee about what hamcrest version you get. Also you'll need to stick to junit 3.8.x if you plan on running the tests as part of your build, since the eclipse-test-framework has no support for junit4 (bug 153429).
Thanks Ketan. I have added myself to the CQs. Once those are approved we can request reuse for Mylyn.
Mylyn is now using (but not distributing) SWTbot for UI tests.
