[jbosstools-issues] [JBoss JIRA] Closed: (JBIDE-7571) org.jboss.tools.jsf.ui.test.JsfUiPreferencesPagesTest causes org.jboss.tools.jsf.ui.test JUnit Test run to fail

Vlado Pakan (JIRA) jira-events at lists.jboss.org
Mon Nov 29 07:31:09 EST 2010


     [ https://jira.jboss.org/browse/JBIDE-7571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vlado Pakan closed JBIDE-7571.
------------------------------

    Assignee: Victor Kukharchuk  (was: Viacheslav Kabanovich)


> org.jboss.tools.jsf.ui.test.JsfUiPreferencesPagesTest causes org.jboss.tools.jsf.ui.test JUnit Test run to fail
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-7571
>                 URL: https://jira.jboss.org/browse/JBIDE-7571
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JSF, testing
>    Affects Versions: 3.2.0.Beta1
>            Reporter: Victor Rubezhny
>            Assignee: Victor Kukharchuk
>             Fix For: 3.2.0.Beta2
>
>
> org.jboss.tools.jsf.ui.test.JsfUiPreferencesPagesTest suite causes JsfUiAllTests JUnit test to fail.
> For some reason JsfUiPreferencesPagesTest test suite causes all the suites which run after it to fail in their test projects setup / clean up stage (actually, they fail when the WaitForIdle procedure is invoked first time after JsfUiPreferencesPagesTest has finished its execution).
> So, if some test suites are to be invoked after JsfUiPreferencesPagesTest suite, then these tests will fail.
> If I try to move JsfUiPreferencesPagesTest test suite to be the last test suite within the test, then the TestWizardsProject (which is the root suite for the test) fails in its tear down procedure (where it invokes WaitForIdle procedure). So, it doesn't help. 
> See the log below for the case when JsfUiPreferencesPagesTest test suite is moved to be the last test. There are no clues to JsfUiPreferencesPagesTest itself, but I caught it experimentally by disabling/enabling the suites and running the tests. If I disable the execution of JsfUiPreferencesPagesTest test suite, then all the tests finish with success. So, I supposed that the reason of fail is in JsfUiPreferencesPagesTest test suite.
> Tests run: 46, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 865.72 sec <<< FAILURE!
> JSF UI tests(org.jboss.tools.jsf.ui.test.TestWizardsProject)  Time elapsed: 0.456 sec  <<< ERROR!
> org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTException: Widget is disposed)
> 	at org.eclipse.swt.SWT.error(SWT.java:4083)
> 	at org.eclipse.swt.SWT.error(SWT.java:3998)
> 	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:137)
> 	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3515)
> 	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3164)
> 	at org.jboss.tools.test.util.JobUtils.delay(JobUtils.java:61)
> 	at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:38)
> 	at org.jboss.tools.test.util.JobUtils.waitForIdle(JobUtils.java:27)
> 	at org.jboss.tools.test.util.ProjectImportTestSetup.tearDown(ProjectImportTestSetup.java:83)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:24)
> 	at junit.framework.TestResult.runProtected(TestResult.java:128)
> 	at junit.extensions.TestSetup.run(TestSetup.java:27)
> 	at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
> 	at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
> 	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
> 	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
> 	at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
> 	at org.codehaus.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:75)
> 	at org.codehaus.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:25)
> 	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> 	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
> 	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3515)
> 	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3164)
> 	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
> 	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
> 	at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
> 	at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
> 	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> 	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
> 	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> 	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
> 	at org.codehaus.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:21)
> 	at org.codehaus.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:109)
> 	at org.codehaus.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:27)
> 	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> 	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> 	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:616)
> 	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
> 	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
> 	at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
> 	at org.eclipse.equinox.launcher.Main.main(Main.java:1383)
> Caused by: org.eclipse.swt.SWTException: Widget is disposed
> 	at org.eclipse.swt.SWT.error(SWT.java:4083)
> 	at org.eclipse.swt.SWT.error(SWT.java:3998)
> 	at org.eclipse.swt.SWT.error(SWT.java:3969)
> 	at org.eclipse.swt.widgets.Widget.error(Widget.java:466)
> 	at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:403)
> 	at org.eclipse.swt.widgets.Table.getSelectionIndex(Table.java:1687)
> 	at org.jboss.tools.common.model.ui.objecteditor.XTable.getSelectionIndex(XTable.java:219)
> 	at org.jboss.tools.common.model.ui.objecteditor.XChildrenEditor.setObject(XChildrenEditor.java:145)
> 	at org.jboss.tools.jsf.ui.preferences.JSFCapabilitiesPreferencesPage.capabilitySelectionChanged(JSFCapabilitiesPreferencesPage.java:177)
> 	at org.jboss.tools.jsf.ui.preferences.JSFCapabilitiesPreferencesPage.access$0(JSFCapabilitiesPreferencesPage.java:175)
> 	at org.jboss.tools.jsf.ui.preferences.JSFCapabilitiesPreferencesPage$1.run(JSFCapabilitiesPreferencesPage.java:90)
> 	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> 	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
> 	... 44 more
> Results :
> Tests in error: 
>   JSF UI tests(org.jboss.tools.jsf.ui.test.TestWizardsProject)
> Tests run: 46, Failures: 0, Errors: 1, Skipped: 0
> !ENTRY org.eclipse.ui 4 4 2010-11-13 02:21:21.292
> !MESSAGE Invalid preference page path: JSP Syntax
> !ENTRY org.eclipse.ui 4 4 2010-11-13 02:21:21.293
> !MESSAGE Invalid preference page path: HTML Syntax
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 16:31.535s
> [INFO] Finished at: Sat Nov 13 02:21:26 MSK 2010
> [INFO] Final Memory: 93M/462M
> [INFO] ------------------------------------------------------------------------

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbosstools-issues mailing list