[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [mdt-bpmn2.dev] Working on the ecore merger tool
- From: "Hille-Doering, Reiner" <reiner.hille-doering@xxxxxxx>
- Date: Thu, 29 Mar 2012 22:49:28 +0200
- Accept-language: de-DE
- Acceptlanguage: de-DE
- Delivered-to: email@example.com
- Thread-index: Ac0N7W4z3ra7oHDlQyONaNg5lyqsjg==
- Thread-topic: [mdt-bpmn2.dev] Working on the ecore merger tool
I'm fine with the idea. Feel free to reorganize the project to fit to Maven convention structure. Only note that for bundles (for which we use tycho), the structure is different and more PDE like - and bundle tests go to extra bundles or fragments.
Am 29.03.2012 um 22:40 schrieb "Benedikt Ritter" <beneritter@xxxxxxxxxxxxxx>:
> I'm planning to put some effort on the ecore merger tool, since there
> are several issues related with that tool (e.g.
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=357088 or the discussed
> splitting of the ecore model). However, I'm feeling uncomfortable,
> touching the code because there are no unit tests. So the first thing
> I want to do is to write some unit tests.
> Now at my company we use maven. Maven has a convention for the project
> structure, where unit tests reside in special source folder called
> src/test/java. Since the ecore merger tool does not stick to this
> convention, I do not know where to put my unit tests. I've seen the
> test bundle but I don't think that it is the right place for the ecore
> merger unit tests. So where should I put the tests?
> After bulding up a basic test coverage (and ATM I don't know how much
> effort that will be), I'd like to try to split the code up some more.
> The processor has several concerns that it has to deal with, and it
> would be good to separate concerns.
> mdt-bpmn2.dev mailing list