[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [iam-dev] Re: Is there a reason IAM has plugin source and tests conjoined?
|
There are two kinds of tests:
- "normal" unit tests (can be executed without eclipse running):
these have been coded inside the plug-in as a typical maven project
- "eclipse" unit tests, which (need an eclipse instance to run):
these are already in separate plug-ins (I think the only case is
iam.wizard.test).
For "normal" unit tests, I don't have a strong opinion in either way
(having them in the same project allows/will allow running "mvn test"
from a single location, which might be a plus, but is not integrated
on PDE build system).
For eclipse unit tests, I agree they must be isolated.
El 19/11/2008, a las 1:25, Joakim Erdfelt escribió:
While researching this I discovered the following article with the
pros/cons of each approach ...
http://rcpquickstart.com/2007/06/20/unit-testing-plug-ins-with-fragments/
- Joakim Erdfelt
On Tue, Nov 18, 2008 at 2:04 PM, Joakim Erdfelt
<joakim.erdfelt@xxxxxxxxx> wrote:
I'm curious as to why IAM has the plugin source and the test cases
conjoined in the same project?
I'd like to propose that we split all of those unit tests out into
org.eclipse.iam.*.test projects instead.
I'll be happy to expand our unit testing of projects, I can work on
the wtp specifics first.
(as I need to introduce some fixes for webapps on RAD 7.5)
- Joakim Erdfelt
_______________________________________________
iam-dev mailing list
iam-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/iam-dev
