[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [egit-dev] UI tests: current SWTBot requires JUnit 4
|
On Tue, Feb 9, 2010 at 9:59 AM, Shawn Pearce <spearce@xxxxxxxxxxx> wrote:
> On Sun, Jan 31, 2010 at 1:51 PM, Matthias Sohn
> <matthias.sohn@xxxxxxxxxxxxxx> wrote:
>> 2010/1/31 Chris Aniszczyk <caniszczyk@xxxxxxxxx>
>>>
>>> On Sun, Jan 31, 2010 at 12:07 PM, Matthias Sohn
>>> <matthias.sohn@xxxxxxxxxxxxxx> wrote:
>>> > Could you advise how to proceed here ? In order to allow test execution
>>> > in
>>> > Eclipse 3.4, 3.5, 3.6 we should depend on JUnit 4.3.1 (which is the
>>> > version
>>> > coming
>>> > with Eclipse 3.4). Eclipse 3.5 comes with JUnit 4.5.1 and 3.6 currently
>>> > has
>>> > 4.7.1.
>>> > For which JUnit versions do we need to create a CQ ?
>>>
>>> Since we don't ship the tests, we don't need to create CQs for them.
>>>
>>> CQs are only needed when you ship code from Eclipse.org, tests are
>>> generally excluded from them.
>>
>> Ok, this implies we also don't need a CQ for hamcrest.org since that is
>> required for SWTBot tests only :-)
>
> I've gotten incredibly vague replies back from EMO IP team about this.
That's what lawyers are paid for! :P
Forgive me for taking awhile on this. I confirm that we DO NOT need a
CQ for SWTBot. If you depend on an
Eclipse.org project, you don't need to file a CQ for it.
The rule is generally quite simple:
"As a general rule, if you have code in a VCS that needs some
third party library to compile, you need a CQ."
The exception is Eclipse.org projects.
Onwards for UI tests!
Cheers,
--
Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk
