Markus,
afaik the tests were disabled in the early stages of the
PDOM indexer, because it would make content assist tests fail so miserably
that it simply did not make sense to run them.
I have now run the individual packages of the
cdt.ui.tests plugin as tests and found the following:
org.eclipse.cdt.ui.tests.chelp is green (5
tests)
org.eclipse.cdt.ui.tests.text has 94 tests with two minor
failures, in fact just warnings that some classes do not contain test
cases.
org.eclipse.cdt.ui.tests.viewsupport is green (5
tests)
org.eclipse.cdt.ui.tests.selectiontests, org.eclipse.cdt.ui.tests.contentassist and org.eclipse.cdt.ui.tests.contentassist2 (my pet) fail pretty badly,
probably because they are relying on the
indexer.
Maybe we could at least bring the green
packages back into the nightly build and leave bad ones out of the suite for
the time being?
What do you
think?
Norbert
Thanks for the link, I was not aware of the fact that JUnit results are
published. It looks like that three test-suites are run:
org.eclipse.cdt.core.suite.AutomatedIntegrationSuite
org.eclipse.cdt.debug.core.tests.AllDebugTests
org.eclipse.cdt.managedbuilder.tests.suite.AllManagedBuildTests
I think it'd make
sense to also run the test-suite for the cdt.ui plugin. The according target
is commented out in the test.xml file of the 'org.eclipse.cdt.testing'
plugin. Is there a reason for that? I'd like to change it.
Markus.
Hey
gang,
Just a reminder to please check
the JUnit results, or even better run the JUnit tests. I notice now that a
few more are failing in the nightly/weekly builds. As always, the builds are
at: http://download.eclipse.org/tools/cdt/builds/
with the JUnit results available as a link in each build’s build
page.
Thanks,
Doug
Schaefer
QNX Software
Systems
Eclipse CDT Project
Lead
http://cdtdoug.blogspot.com
