The UI ones were turned off since a lot of
these assumed the old indexer/search framework and almost all of them fail. My
bad for not replacing them with tests against the new framework.
I think having more JUnit coverage should
be one of our highest priorities. I’d also like to see someone in the
Eclipse community muck with the Automated GUI Recorder so that it can generate
tests that can be integrated with any JUnit test suite (not just TPTP tests).
So whatever you can do to enhance our
JUnit coverage, please do so. To help, I’ll make sure I add a section to
the Summit
agenda on JUnits and how these tests are run.
Cheers,
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Schorn,
Markus
Sent: Thursday, August 31, 2006
3:43 AM
To: CDT
General developers list.
Subject: RE: [cdt-dev] JUnit
failures
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.
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
Sent: Mittwoch, 30. August 2006
19:42
To: CDT General
developers list.
Subject: [cdt-dev] JUnit failures
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
