Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-test-dev] New 3.0.0 Build Available


Hi Alain,

As Doug indicated the test suite classes are in the junit results page clickable from the build page in the email he sent yesterday.
Also I sent this out earlier, which mentions the 4 suites. There are more junit tests for core and ui, but AutomatedIntegrationSuite and AutomatedSuite are the ones selected for the nightly regression tests. There isn't a subset of AllDebugTests or All ManagedBuildTests recommended for regression yet, but hopefully the teams working on those features can select some.

Hope it helps!
Tanya



The automated tests get included in the nightly builds in this patch, as well as including the new ui regression tests in the automated suite. The main class that the eclipse test application runs is shown for each of the following cdt test plugins, as well as which test application runs it: org.eclipse.test.uitestapplication (runs eclipse ui during tests) or org.eclipse.test.coretestapplication (doesn't need eclipse ui).

org.eclipse.cdt.core.tests: org.eclipse.cdt.core.suite.AutomatedIntegrationSuite (coretestapplication)
org.eclipse.cdt.ui.tests: org.eclipse.cdt.ui.tests.AutomatedSuite (uitestapplication)
org.eclipse.cdt.debug.ui.tests: org.eclipse.cdt.debug.core.tests.AllDebugTests (uitestapplication)
org.eclipse.managedbuilder.core.tests: org.eclipse.cdt.managedbuilder.tests.suite.AllManagedBuildTests (uitestapplication)

For the Debug and ManagedBuilder tests, let me know if these are not the correct suite for the nightly builds.  

I have only included the core, ui, and debug in the nightly build since managed build tests would fail with a NPE at the first test: the suite itself is likely ok, just having troubles getting started with the AntRunner.

Error: java.lang.NullPointerException

org.eclipse.test.EclipseTestRunner$TestFailedException: Error: java.lang.NullPointerException
at org.eclipse.test.EclipseTestRunner.runFailed(EclipseTestRunner.java:269)
at org.eclipse.test.EclipseTestRunner.getTest(EclipseTestRunner.java:238)
at org.eclipse.test.EclipseTestRunner.<init>(EclipseTestRunner.java:213)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:197)
at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:188)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:118)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:2780)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2451)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1569)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1540)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:285)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:144)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:102)
at org.eclipse.test.UITestApplication.runApplication(UITestApplication.java:131)
at org.eclipse.test.UITestApplication.run(UITestApplication.java:58)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:220)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:273)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at org.eclipse.core.launcher.Main.basicRun(Main.java:185)
at org.eclipse.core.launcher.Main.run(Main.java:710)
at org.eclipse.core.launcher.Main.main(Main.java:694)  

Also, only 2 of 7 Debug tests are passing, so these should be looked at for our next milestone.


"Alain Magloire" <alain@xxxxxxx>
Sent by: cdt-test-dev-admin@xxxxxxxxxxx

10/02/2005 01:38 PM

Please respond to
cdt-test-dev

To
cdt-test-dev@xxxxxxxxxxx
cc
Subject
Re: [cdt-test-dev] New 3.0.0 Build Available





>
> You could simply run them as JUnit plug-in tests like you do when you
> write them :-)
>

I meant if there was any particular suites that were run on the builds
to detect regression.  For example, I run
  org.eclipse.cdt.core.suite.AutomatedIntegrationSuite
regularly after making changes to the Core.


_______________________________________________
cdt-test-dev mailing list
cdt-test-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-test-dev


Back to the top