Bugzilla – Full Text Bug Listing
| Summary: | Re-enable SWTBot Tests | ||
|---|---|---|---|
| Product: | [Modeling] Graphiti | Reporter: | Michael Wenz <michael.wenz> |
| Component: | Core | Assignee: | Michael Wenz <michael.wenz> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | Flags: | michael.wenz:
indigo+
|
| Version: | 0.8.0 | ||
| Target Milestone: | 0.8.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | Indigo M7 theme_release_train | ||
| Bug Depends on: | 340906 | ||
| Bug Blocks: | |||
|
Description
Michael Wenz
We use a JUnit Plugin Test run configuation to start our SWTBot based tests on the Eclipse Hudson; in this configuration the flag "Run in UI thread" is set to false. This leads with Indigo M6 as basis to the runtime Eclipse being started (UI comes up) but the test class gets not started (not even loaded). Setting "Run in UI thread" to true will get the tests started, but they of course fail with errors. Using a SWTBot Test run configuration will work, but this cannot be used on the Eclipse Hudson, because there the Buckminster installation is used as Eclipse IDE from which the tests are started and no SWTBot is installed there. All of this can locally be reproduced with the latest Indigo M6 installation. Workaround for running the tests is to use such a SWTBot configuration locally, but centrally no test execution is possible right now. Local debugging of the cause of this lead to plugin org.eclipse.pde.junit.runtime. A change for M6 leads to UITestApplication.start no longer calling WorkbenchTestable.setTestHarness any more. The change was done for https://bugs.eclipse.org/bugs/show_bug.cgi?id=311979. Not sure if this is a regression in PDE JUnit runtime of a missuse of the functionality from our side. Used this kind of run configuration because this was recommended as the way to start SWTBot tests via Buckminster on Hudson. See Bugzilla 340906. This could be considered as a regression in PDE integration. Alternative solution for this would be running SWTBot tests using a SWTBot run configuration. Doing this from within Buckminster probably needs some additional work from SWTBot and/or Buckminster. For now the SWTBot tests are disabled on Hudson, developers need to start the tests locally before check-in. I added an additional provider to our rmap file that adds the newest integration build for PDE to our build (via update site http://download.eclipse.org/eclipse/updates/3.7-I-builds). After re-enabling the SWTBot tests they automatically run again on the Eclipse Hudson. This is a preliminary solution only, as soon as the newest PDE version is available via the Indigo update sites the above provider needs to be removed again. The fix is now available via the regular Eclipse milestones update site. Removed the additional provider from the rmap file again (see comment 5). Michael Part of Graphiti Indigo 0.8.0 |