You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tamaya.apache.org by "Oliver B. Fischer" <o....@swe-blog.net> on 2015/02/01 22:29:17 UTC
Re: Testing Tamaya with custom classpath
Hi,
it seems so that the Arquillian daemon is exactly doing what we need:
https://github.com/arquillian/arquillian-daemon
Bye,
Oliver
Am 29.01.15 um 08:31 schrieb Mark Struberg:
> That's why I wanted some 'isolating' Arquillian SE adaptor :)
> I prefer using Arquillian over any homegrown solution as we might use that to later test EE containers as well.
>
> LieGrue,
> strub
>
>
>
>
>> On Thursday, 29 January 2015, 0:33, Romain Manni-Bucau <rm...@gmail.com> wrote:
>> have a test classloader, should be far enough and avoid to depend on
>> SW and having to create archives (we just switch the classloader which
>> knows the SPI we want and that's it).
>>
>>
>> Romain Manni-Bucau
>> @rmannibucau
>> http://www.tomitribe.com
>> http://rmannibucau.wordpress.com
>> https://github.com/rmannibucau
>>
>>
>>
>> 2015-01-29 0:28 GMT+01:00 Oliver B. Fischer <o....@swe-blog.net>:
>> using
>> self-defined
--
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fischer@swe-blog.net
S oliver.b.fischer
J oliver.b.fischer@jabber.org
X http://xing.to/obf
Re: Testing Tamaya with custom classpath
Posted by "Oliver B. Fischer" <o....@swe-blog.net>.
Yes, Daemon.
Am 05.02.15 um 09:14 schrieb Romain Manni-Bucau:
> Which adapter (since arq doesnt solve all our issues)? Daemon? If it cant
> leak processes even with a bad kill - eclipse or idea stop button - of a
> running test let start this way.
> Le 5 févr. 2015 08:16, "Oliver B. Fischer" <o....@swe-blog.net> a
> écrit :
>
>> So, if no objects I will use Arquillian for the first tests. Later, if we
>> have a better solution, I will migrate all the tests.
>>
>> Bye
>>
>> Oliver
>>
>> Am 02.02.15 um 07:20 schrieb Mark Struberg:
>>
>> --
>> N Oliver B. Fischer
>> A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
>> P +49 30 44793251
>> M +49 178 7903538
>> E o.b.fischer@swe-blog.net
>> S oliver.b.fischer
>> J oliver.b.fischer@jabber.org
>> X http://xing.to/obf
>>
>>
--
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fischer@swe-blog.net
S oliver.b.fischer
J oliver.b.fischer@jabber.org
X http://xing.to/obf
Re: Testing Tamaya with custom classpath
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Which adapter (since arq doesnt solve all our issues)? Daemon? If it cant
leak processes even with a bad kill - eclipse or idea stop button - of a
running test let start this way.
Le 5 févr. 2015 08:16, "Oliver B. Fischer" <o....@swe-blog.net> a
écrit :
> So, if no objects I will use Arquillian for the first tests. Later, if we
> have a better solution, I will migrate all the tests.
>
> Bye
>
> Oliver
>
> Am 02.02.15 um 07:20 schrieb Mark Struberg:
>
>> That's right, we should be able to run tests in parallel and on Jenkins
>> without blocking other runs. What about Lincolns SE adapter?
>>
>> LieGrue,
>> strub
>>
>>
>>
>>
>>
>> On Sunday, 1 February 2015, 23:35, Romain Manni-Bucau <
>>> rmannibucau@gmail.com> wrote:
>>> If we start using remote solutions we ll have other issues (we need
>>> random
>>> ports at least) and how do you simulate provided libs? + There are
>>> alternative like pax and karaf testing integration. All looks complicated
>>> for compared to what we actually need
>>>
>>> Wdyt?
>>> Le 1 févr. 2015 22:31, "Oliver B. Fischer"
>>> <o....@swe-blog.net> a
>>> écrit :
>>>
>>>
>>> :)
>>> on
>>> which
>>> <o....@swe-blog.net>:
>>>
>>
> --
> N Oliver B. Fischer
> A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
> P +49 30 44793251
> M +49 178 7903538
> E o.b.fischer@swe-blog.net
> S oliver.b.fischer
> J oliver.b.fischer@jabber.org
> X http://xing.to/obf
>
>
Re: Testing Tamaya with custom classpath
Posted by "Oliver B. Fischer" <o....@swe-blog.net>.
So, if no objects I will use Arquillian for the first tests. Later, if
we have a better solution, I will migrate all the tests.
Bye
Oliver
Am 02.02.15 um 07:20 schrieb Mark Struberg:
> That's right, we should be able to run tests in parallel and on Jenkins without blocking other runs. What about Lincolns SE adapter?
>
> LieGrue,
> strub
>
>
>
>
>
>> On Sunday, 1 February 2015, 23:35, Romain Manni-Bucau <rm...@gmail.com> wrote:
>> If we start using remote solutions we ll have other issues (we need random
>> ports at least) and how do you simulate provided libs? + There are
>> alternative like pax and karaf testing integration. All looks complicated
>> for compared to what we actually need
>>
>> Wdyt?
>> Le 1 févr. 2015 22:31, "Oliver B. Fischer"
>> <o....@swe-blog.net> a
>> écrit :
>>
>>
>> :)
>> on
>> which
>> <o....@swe-blog.net>:
--
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fischer@swe-blog.net
S oliver.b.fischer
J oliver.b.fischer@jabber.org
X http://xing.to/obf
Re: Testing Tamaya with custom classpath
Posted by "Oliver B. Fischer" <o....@swe-blog.net>.
Hi Mark,
for integration tests it is fine to run them sequentially if there are
not so many. At least if we start with Java EE support we will need
Arquillian. For real container tests I don't know a better solution at
the moment which supports so many different containers.
wdyt?
Oliver
Am 02.02.15 um 07:20 schrieb Mark Struberg:
> That's right, we should be able to run tests in parallel and on Jenkins without blocking other runs. What about Lincolns SE adapter?
>
> LieGrue,
> strub
>
>
>
>
>
>> On Sunday, 1 February 2015, 23:35, Romain Manni-Bucau <rm...@gmail.com> wrote:
>> If we start using remote solutions we ll have other issues (we need random
>> ports at least) and how do you simulate provided libs? + There are
>> alternative like pax and karaf testing integration. All looks complicated
>> for compared to what we actually need
>>
>> Wdyt?
>> Le 1 févr. 2015 22:31, "Oliver B. Fischer"
>> <o....@swe-blog.net> a
>> écrit :
>>
>>
>> :)
>> on
>> which
>> <o....@swe-blog.net>:
--
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fischer@swe-blog.net
S oliver.b.fischer
J oliver.b.fischer@jabber.org
X http://xing.to/obf
Re: Testing Tamaya with custom classpath
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Ok, let's see what this week brings and if needed I'll try to reserve
few hours to help on this topic this week end
Romain Manni-Bucau
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wordpress.com
https://github.com/rmannibucau
2015-02-02 18:01 GMT+01:00 Oliver B. Fischer <o....@swe-blog.net>:
> What is Lincoln?
>
> Oliver
>
> Am 02.02.15 um 07:20 schrieb Mark Struberg:
>>
>> That's right, we should be able to run tests in parallel and on Jenkins
>> without blocking other runs. What about Lincolns SE adapter?
>>
>> LieGrue,
>> strub
>>
>>
>>
>>
>>
>>> On Sunday, 1 February 2015, 23:35, Romain Manni-Bucau
>>> <rm...@gmail.com> wrote:
>>> If we start using remote solutions we ll have other issues (we need
>>> random
>>> ports at least) and how do you simulate provided libs? + There are
>>> alternative like pax and karaf testing integration. All looks complicated
>>> for compared to what we actually need
>>>
>>> Wdyt?
>>> Le 1 févr. 2015 22:31, "Oliver B. Fischer"
>>> <o....@swe-blog.net> a
>>> écrit :
>>>
>>>
>>> :)
>>> on
>>> which
>>> <o....@swe-blog.net>:
>
>
> --
> N Oliver B. Fischer
> A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
> P +49 30 44793251
> M +49 178 7903538
> E o.b.fischer@swe-blog.net
> S oliver.b.fischer
> J oliver.b.fischer@jabber.org
> X http://xing.to/obf
>
Re: Testing Tamaya with custom classpath
Posted by "Oliver B. Fischer" <o....@swe-blog.net>.
What is Lincoln?
Oliver
Am 02.02.15 um 07:20 schrieb Mark Struberg:
> That's right, we should be able to run tests in parallel and on Jenkins without blocking other runs. What about Lincolns SE adapter?
>
> LieGrue,
> strub
>
>
>
>
>
>> On Sunday, 1 February 2015, 23:35, Romain Manni-Bucau <rm...@gmail.com> wrote:
>> If we start using remote solutions we ll have other issues (we need random
>> ports at least) and how do you simulate provided libs? + There are
>> alternative like pax and karaf testing integration. All looks complicated
>> for compared to what we actually need
>>
>> Wdyt?
>> Le 1 févr. 2015 22:31, "Oliver B. Fischer"
>> <o....@swe-blog.net> a
>> écrit :
>>
>>
>> :)
>> on
>> which
>> <o....@swe-blog.net>:
--
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fischer@swe-blog.net
S oliver.b.fischer
J oliver.b.fischer@jabber.org
X http://xing.to/obf
Re: Testing Tamaya with custom classpath
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Still dont get why we need it Mark and your answers make it worse...
Le 2 févr. 2015 07:24, "Mark Struberg" <st...@yahoo.de> a écrit :
> That's right, we should be able to run tests in parallel and on Jenkins
> without blocking other runs. What about Lincolns SE adapter?
>
> LieGrue,
> strub
>
>
>
>
>
> > On Sunday, 1 February 2015, 23:35, Romain Manni-Bucau <
> rmannibucau@gmail.com> wrote:
> > > Just for my knowledge why classloader rule solution is not an option?
> >
> > If we start using remote solutions we ll have other issues (we need
> random
> > ports at least) and how do you simulate provided libs? + There are
> > alternative like pax and karaf testing integration. All looks complicated
> > for compared to what we actually need
> >
> > Wdyt?
> > Le 1 févr. 2015 22:31, "Oliver B. Fischer"
> > <o....@swe-blog.net> a
> > écrit :
> >
> >
> >> Hi,
> >>
> >> it seems so that the Arquillian daemon is exactly doing what we need:
> >>
> >> https://github.com/arquillian/arquillian-daemon
> >>
> >> Bye,
> >>
> >> Oliver
> >>
> >> Am 29.01.15 um 08:31 schrieb Mark Struberg:
> >>
> >>> That's why I wanted some 'isolating' Arquillian SE adaptor
> > :)
> >>> I prefer using Arquillian over any homegrown solution as we might use
> >>> that to later test EE containers as well.
> >>>
> >>> LieGrue,
> >>> strub
> >>>
> >>>
> >>>
> >>>
> >>> On Thursday, 29 January 2015, 0:33, Romain Manni-Bucau <
> >>>> rmannibucau@gmail.com> wrote:
> >>>> have a test classloader, should be far enough and avoid to depend
> > on
> >>>> SW and having to create archives (we just switch the classloader
> > which
> >>>> knows the SPI we want and that's it).
> >>>>
> >>>>
> >>>> Romain Manni-Bucau
> >>>> @rmannibucau
> >>>> http://www.tomitribe.com
> >>>> http://rmannibucau.wordpress.com
> >>>> https://github.com/rmannibucau
> >>>>
> >>>>
> >>>>
> >>>> 2015-01-29 0:28 GMT+01:00 Oliver B. Fischer
> > <o....@swe-blog.net>:
> >>>> using
> >>>> self-defined
> >>>>
> >>>
> >> --
> >> N Oliver B. Fischer
> >> A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
> >> P +49 30 44793251
> >> M +49 178 7903538
> >> E o.b.fischer@swe-blog.net
> >> S oliver.b.fischer
> >> J oliver.b.fischer@jabber.org
> >> X http://xing.to/obf
> >>
> >>
> >
>
Re: Testing Tamaya with custom classpath
Posted by Mark Struberg <st...@yahoo.de>.
That's right, we should be able to run tests in parallel and on Jenkins without blocking other runs. What about Lincolns SE adapter?
LieGrue,
strub
> On Sunday, 1 February 2015, 23:35, Romain Manni-Bucau <rm...@gmail.com> wrote:
> > Just for my knowledge why classloader rule solution is not an option?
>
> If we start using remote solutions we ll have other issues (we need random
> ports at least) and how do you simulate provided libs? + There are
> alternative like pax and karaf testing integration. All looks complicated
> for compared to what we actually need
>
> Wdyt?
> Le 1 févr. 2015 22:31, "Oliver B. Fischer"
> <o....@swe-blog.net> a
> écrit :
>
>
>> Hi,
>>
>> it seems so that the Arquillian daemon is exactly doing what we need:
>>
>> https://github.com/arquillian/arquillian-daemon
>>
>> Bye,
>>
>> Oliver
>>
>> Am 29.01.15 um 08:31 schrieb Mark Struberg:
>>
>>> That's why I wanted some 'isolating' Arquillian SE adaptor
> :)
>>> I prefer using Arquillian over any homegrown solution as we might use
>>> that to later test EE containers as well.
>>>
>>> LieGrue,
>>> strub
>>>
>>>
>>>
>>>
>>> On Thursday, 29 January 2015, 0:33, Romain Manni-Bucau <
>>>> rmannibucau@gmail.com> wrote:
>>>> have a test classloader, should be far enough and avoid to depend
> on
>>>> SW and having to create archives (we just switch the classloader
> which
>>>> knows the SPI we want and that's it).
>>>>
>>>>
>>>> Romain Manni-Bucau
>>>> @rmannibucau
>>>> http://www.tomitribe.com
>>>> http://rmannibucau.wordpress.com
>>>> https://github.com/rmannibucau
>>>>
>>>>
>>>>
>>>> 2015-01-29 0:28 GMT+01:00 Oliver B. Fischer
> <o....@swe-blog.net>:
>>>> using
>>>> self-defined
>>>>
>>>
>> --
>> N Oliver B. Fischer
>> A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
>> P +49 30 44793251
>> M +49 178 7903538
>> E o.b.fischer@swe-blog.net
>> S oliver.b.fischer
>> J oliver.b.fischer@jabber.org
>> X http://xing.to/obf
>>
>>
>
Re: Testing Tamaya with custom classpath
Posted by "Oliver B. Fischer" <o....@swe-blog.net>.
Hi Romain,
I wouldn't say it is possible. Arquillian Daemon is at least a possible
working solution. May be there is possibility to achive a full class
path isolation but I am not a classloader expert. On the otherhand OSGI
shows that it is possible.
A classloader based solution must be able to use only provided Jars and
to run all tests in the context of these provided Jars.
So, I am open to every working solution, even writing it by my own. But
for this I need some help ;-)
Bye,
Oliver
Am 01.02.15 um 23:34 schrieb Romain Manni-Bucau:
> Just for my knowledge why classloader rule solution is not an option?
>
> If we start using remote solutions we ll have other issues (we need random
> ports at least) and how do you simulate provided libs? + There are
> alternative like pax and karaf testing integration. All looks complicated
> for compared to what we actually need
>
> Wdyt?
> Le 1 févr. 2015 22:31, "Oliver B. Fischer" <o....@swe-blog.net> a
> écrit :
>
>> Hi,
>>
>> it seems so that the Arquillian daemon is exactly doing what we need:
>>
>> https://github.com/arquillian/arquillian-daemon
>>
>> Bye,
>>
>> Oliver
>>
>> Am 29.01.15 um 08:31 schrieb Mark Struberg:
>>
>> --
>> N Oliver B. Fischer
>> A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
>> P +49 30 44793251
>> M +49 178 7903538
>> E o.b.fischer@swe-blog.net
>> S oliver.b.fischer
>> J oliver.b.fischer@jabber.org
>> X http://xing.to/obf
>>
>>
--
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fischer@swe-blog.net
S oliver.b.fischer
J oliver.b.fischer@jabber.org
X http://xing.to/obf
Re: Testing Tamaya with custom classpath
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Just for my knowledge why classloader rule solution is not an option?
If we start using remote solutions we ll have other issues (we need random
ports at least) and how do you simulate provided libs? + There are
alternative like pax and karaf testing integration. All looks complicated
for compared to what we actually need
Wdyt?
Le 1 févr. 2015 22:31, "Oliver B. Fischer" <o....@swe-blog.net> a
écrit :
> Hi,
>
> it seems so that the Arquillian daemon is exactly doing what we need:
>
> https://github.com/arquillian/arquillian-daemon
>
> Bye,
>
> Oliver
>
> Am 29.01.15 um 08:31 schrieb Mark Struberg:
>
>> That's why I wanted some 'isolating' Arquillian SE adaptor :)
>> I prefer using Arquillian over any homegrown solution as we might use
>> that to later test EE containers as well.
>>
>> LieGrue,
>> strub
>>
>>
>>
>>
>> On Thursday, 29 January 2015, 0:33, Romain Manni-Bucau <
>>> rmannibucau@gmail.com> wrote:
>>> have a test classloader, should be far enough and avoid to depend on
>>> SW and having to create archives (we just switch the classloader which
>>> knows the SPI we want and that's it).
>>>
>>>
>>> Romain Manni-Bucau
>>> @rmannibucau
>>> http://www.tomitribe.com
>>> http://rmannibucau.wordpress.com
>>> https://github.com/rmannibucau
>>>
>>>
>>>
>>> 2015-01-29 0:28 GMT+01:00 Oliver B. Fischer <o....@swe-blog.net>:
>>> using
>>> self-defined
>>>
>>
> --
> N Oliver B. Fischer
> A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
> P +49 30 44793251
> M +49 178 7903538
> E o.b.fischer@swe-blog.net
> S oliver.b.fischer
> J oliver.b.fischer@jabber.org
> X http://xing.to/obf
>
>