Hi Max
Thanks - actually looks like option 2 may be adequate (identifying the packages under test
as a 'friend' of the test plugin), and should still be ok with Tycho as the test
plugins can remain separate. Just means methods being tested need to be public, but if
they are not exposed by the plugin in general, that should be ok.
Regards
Gary
----- "Andersen Max" <max.andersen(a)redhat.com> wrote:
This should actually be on jbosstools-dev ;)
btw. the article describing this is
http://www.modumind.com/2007/06/20/unit-testing-plug-ins-with-fragments/
/max
On Jul 8, 2010, at 11:48, Gary Brown wrote:
> OK thanks - I'll see what I can find out.
>
> Regards
> Gary
>
> ----- "Andersen Max" <max.andersen(a)redhat.com> wrote:
>
>> found it ...the magic sauce is to use test plugin fragments.
>> Such fragments have access to the internals.
>>
>> But not sure how well that works in Tycho or even PDE build ?
>>
>> /max
>>
>> On Jul 8, 2010, at 11:01, Andersen Max wrote:
>>
>>> Good question - eclipse tend to export all classes anyway.
(googling
>> right now ;)
>>>
>>> May I ask how you exclude the tests from the build when they are
in
>> together with the eclipse PDE plugin project ?
>>>
>>> m/ax
>>>
>>> On Jul 7, 2010, at 22:57, Nick Boldt wrote:
>>>
>>>> Not sure. Coying a wider audience for advice.
>>>>
>>>> N
>>>>
>>>> On 07/07/2010 01:22 PM, Gary Brown wrote:
>>>>> Hi Nick
>>>>>
>>>>> I'm starting to reorg the Savara plugins to use Tycho, and one
of
>> the problems I have with splitting the tests out into a separate
>> plugin (in the tests sub-folder) is that some of the tests are for
>> classes that are no exported from the plugin being tested.
>>>>>
>>>>> What is the general wisdom in these situations? How can these
>> classes be tested without having to export the internal packages?
>>>>>
>>>>> Regards
>>>>> Gary
>>>>
>>>> --
>>>> Nick Boldt :: JBoss by Red Hat
>>>> Productization Lead :: JBoss Tools & Dev Studio
>>>> Release Engineer :: Eclipse Modeling & Dash Athena
>>>>
http://nick.divbyzero.com
>>>>
>>>