|
We
could create a separate plugin, or re-use the cdt.ui.tests plugin. Originally,
the test plugin
name/layout was modeled after the JDT test plugin
layout, which includes both core and UI
tests
in the org.eclipse.jdt.ui.tests plugin. However, they have since split it to
have separate
test
plugins for the model, compiler and builder.
I have
to say that I am also getting a little concerned with the sheer number of
plugins that the CDT
has.
At the end of the day, we have to balance the number of plugins with the
amount
of
useful code in each one of them. Since we currently have very little JUNIT
testcases, the more
prudent approach might be to just build up the CDT
model tests in the org.eclipse.cdt.ui.tests
plugin
(we will likely build up the other tests as well), and, once we have a
significant testsuite,
potentially break it up in multiple
plugins.
Other
thoughts and comments?
Sebastien
I
would vote for creating a "org.eclipse.cdt.core.tests" plugins for the parsing
tests.
Sebastien can request this if this is the way we choose to
go.
-Judy
Hey all,
As we're working on the
parser/scanner/CDOM, we want to build up an extensive collection of JUnit
tests to make sure the model is functioning correctly. Should we
create a new plugin for this or should we reuse the
cdt.ui.tests?
Thanks,
Doug
Schaefer
Senior Staff Software
Engineer
Rational - the software development
company
Ottawa (Kanata), Ontario, Canada
| 