Re: Integration testing

2009-10-14 Thread Marcel Offermans

On Oct 14, 2009, at 22:22 , Peter Kriens wrote:

We're experimenting in the OSGi with the compilers -jsr16 target.  
This allows us to program in J5 but generate 1.4 output ... Really  
cool.


Sounds very interesting. Please do share your findings!

Greetings, Marcel




Re: Integration testing

2009-10-14 Thread Peter Kriens
We're experimenting in the OSGi with the compilers -jsr16 target. This  
allows us to program in J5 but generate 1.4 output ... Really cool.


Kind regards,

Peter Kriens


On 8 okt 2009, at 13:44, Karl Pauls wrote:


On Thu, Oct 8, 2009 at 12:43 PM, Don Brown  wrote:
I do have several that would be applicable, but they require Java  
1.5.

 I couldn't find anything about Felix's stance on Java compatibility
other than it seems Maven is targeting 1.3.  What would it take for
that to change?  Would it be possible to have the build require 1.5
(for tests) yet build 1.3 core jars?  Maven 2 already requires 1.5,  
so

the 1.5 JVM will be there.


Yes, that is no problem. The default is 1.3 but you can request 1.5 on
a per project basis.

regards,

Karl


Don

On Thu, Oct 8, 2009 at 9:34 PM, Karl Pauls   
wrote:
The more tests we have the better! Are you interested in bringing  
over

the tests as well? That would be cool :-)

regards,

Karl

On Thu, Oct 8, 2009 at 12:29 PM, Richard S. Hall > wrote:

On 10/8/09 12:24, Don Brown wrote:


Since the TCK seems to be a deadend for automated testing, what  
other
options do we have?  Richard, you said you were working on a  
testing

framework, but I don't see it svn.  Are there a set of
integration/functional tests I'm missing?  I have a little  
framework
we use in Atlassian Plugins for integration testing that I could  
bring

over.



I am using BND and my few tests are included in the my sandbox:

   http://svn.apache.org/repos/asf/felix/sandbox/rickhall/bnd-test/

There is some [likely outdated] description of this here:

   http://felix.apache.org/site/bnd-testing-harness.html

This isn't integrated in anyway, because there was no decision  
within the
community to go with it, but it is still what I use when I create  
a new test

cases. It is also what the OSGi TCK is based on.

-> richard


Any objections?

Don







--
Karl Pauls
karlpa...@gmail.com







--
Karl Pauls
karlpa...@gmail.com




Re: Integration testing

2009-10-08 Thread Karl Pauls
On Thu, Oct 8, 2009 at 12:43 PM, Don Brown  wrote:
> I do have several that would be applicable, but they require Java 1.5.
>  I couldn't find anything about Felix's stance on Java compatibility
> other than it seems Maven is targeting 1.3.  What would it take for
> that to change?  Would it be possible to have the build require 1.5
> (for tests) yet build 1.3 core jars?  Maven 2 already requires 1.5, so
> the 1.5 JVM will be there.

Yes, that is no problem. The default is 1.3 but you can request 1.5 on
a per project basis.

regards,

Karl

> Don
>
> On Thu, Oct 8, 2009 at 9:34 PM, Karl Pauls  wrote:
>> The more tests we have the better! Are you interested in bringing over
>> the tests as well? That would be cool :-)
>>
>> regards,
>>
>> Karl
>>
>> On Thu, Oct 8, 2009 at 12:29 PM, Richard S. Hall  
>> wrote:
>>> On 10/8/09 12:24, Don Brown wrote:

 Since the TCK seems to be a deadend for automated testing, what other
 options do we have?  Richard, you said you were working on a testing
 framework, but I don't see it svn.  Are there a set of
 integration/functional tests I'm missing?  I have a little framework
 we use in Atlassian Plugins for integration testing that I could bring
 over.

>>>
>>> I am using BND and my few tests are included in the my sandbox:
>>>
>>>    http://svn.apache.org/repos/asf/felix/sandbox/rickhall/bnd-test/
>>>
>>> There is some [likely outdated] description of this here:
>>>
>>>    http://felix.apache.org/site/bnd-testing-harness.html
>>>
>>> This isn't integrated in anyway, because there was no decision within the
>>> community to go with it, but it is still what I use when I create a new test
>>> cases. It is also what the OSGi TCK is based on.
>>>
>>> -> richard
>>>
 Any objections?

 Don

>>>
>>
>>
>>
>> --
>> Karl Pauls
>> karlpa...@gmail.com
>>
>



-- 
Karl Pauls
karlpa...@gmail.com


Re: Integration testing

2009-10-08 Thread Don Brown
The testing framework we use in Atlassian Plugins is really focused
testing the integration between Atlassian Plugins, Spring DM, and
Felix, so it may or may not be valuable for Felix.  Here is a class
that does some testing around plugin/bundle install:

https://studio.atlassian.com/source/browse/PLUG/trunk/atlassian-plugins-osgi/src/test/java/com/atlassian/plugin/osgi/TestPluginInstall.java?r=44906

In Atlassian Plugins, a plugin is basically a jar that may or may not
be a valid OSGi bundle.  If not, we convert it into one via bnd upon
installation.  This class is running through several tests that build
plugin jars, installs them, and verifies the installation was
successful and it operates as expected.  The interesting bit is how we
build jars at runtime in the test itself, to hopefully keep the test
readable in one pass.  If your bundle/plugin is small, this works
fine, but if you want to execute a bunch of code in the bundle, it
doesn't.  This is why it is well-suited, IMO, to integration testing.

I could see this being used to test the embedding API to
programmatically build and install bundles via a system activator,
which is actually how Atlassian Plugins interacts with Felix.  It can
also be used to easily test interactions between multiple bundles,
provided they contain little code.

Don

On Thu, Oct 8, 2009 at 9:40 PM, Toni Menzel  wrote:
> The Subject just drove me in somwhow ;)I would be very interested into a
> complete framework testing solution.
> Granted, Pax Exam is currently made for Application Integration Testing and
> not for Frameworks itself cause you always see everything from a 3rd persons
> perspective.
>
> What are the general requirements to offer such a thing (maybe based on pax
> exam/runner infrastructure) ?
>
> Also, i guess integration testing is a very diverse term which does not help
> to come up with a fit-it-all solution.
>
> So, maybe i should ask here, what are the things you feel are missing from
> TCK (think its it closeness but never seen it myself), bnd-test, atlassian
> framwork (dan, can we see that somehwere ?) and pax exam ?
>
> Toni
>
> On Thu, Oct 8, 2009 at 12:29 PM, Richard S. Hall wrote:
>
>> On 10/8/09 12:24, Don Brown wrote:
>>
>>> Since the TCK seems to be a deadend for automated testing, what other
>>> options do we have?  Richard, you said you were working on a testing
>>> framework, but I don't see it svn.  Are there a set of
>>> integration/functional tests I'm missing?  I have a little framework
>>> we use in Atlassian Plugins for integration testing that I could bring
>>> over.
>>>
>>>
>>
>> I am using BND and my few tests are included in the my sandbox:
>>
>>    http://svn.apache.org/repos/asf/felix/sandbox/rickhall/bnd-test/
>>
>> There is some [likely outdated] description of this here:
>>
>>    http://felix.apache.org/site/bnd-testing-harness.html
>>
>> This isn't integrated in anyway, because there was no decision within the
>> community to go with it, but it is still what I use when I create a new test
>> cases. It is also what the OSGi TCK is based on.
>>
>> -> richard
>>
>>  Any objections?
>>>
>>> Don
>>>
>>>
>>
>
>
> --
> Toni Menzel
> Independent Software Developer
> Professional Profile: http://okidokiteam.com
> t...@okidokiteam.com
> http://www.ops4j.org     - New Energy for OSS Communities - Open
> Participation Software.
>


Re: Integration testing

2009-10-08 Thread Don Brown
I do have several that would be applicable, but they require Java 1.5.
 I couldn't find anything about Felix's stance on Java compatibility
other than it seems Maven is targeting 1.3.  What would it take for
that to change?  Would it be possible to have the build require 1.5
(for tests) yet build 1.3 core jars?  Maven 2 already requires 1.5, so
the 1.5 JVM will be there.

Don

On Thu, Oct 8, 2009 at 9:34 PM, Karl Pauls  wrote:
> The more tests we have the better! Are you interested in bringing over
> the tests as well? That would be cool :-)
>
> regards,
>
> Karl
>
> On Thu, Oct 8, 2009 at 12:29 PM, Richard S. Hall  wrote:
>> On 10/8/09 12:24, Don Brown wrote:
>>>
>>> Since the TCK seems to be a deadend for automated testing, what other
>>> options do we have?  Richard, you said you were working on a testing
>>> framework, but I don't see it svn.  Are there a set of
>>> integration/functional tests I'm missing?  I have a little framework
>>> we use in Atlassian Plugins for integration testing that I could bring
>>> over.
>>>
>>
>> I am using BND and my few tests are included in the my sandbox:
>>
>>    http://svn.apache.org/repos/asf/felix/sandbox/rickhall/bnd-test/
>>
>> There is some [likely outdated] description of this here:
>>
>>    http://felix.apache.org/site/bnd-testing-harness.html
>>
>> This isn't integrated in anyway, because there was no decision within the
>> community to go with it, but it is still what I use when I create a new test
>> cases. It is also what the OSGi TCK is based on.
>>
>> -> richard
>>
>>> Any objections?
>>>
>>> Don
>>>
>>
>
>
>
> --
> Karl Pauls
> karlpa...@gmail.com
>


Re: Integration testing

2009-10-08 Thread Toni Menzel
The Subject just drove me in somwhow ;)I would be very interested into a
complete framework testing solution.
Granted, Pax Exam is currently made for Application Integration Testing and
not for Frameworks itself cause you always see everything from a 3rd persons
perspective.

What are the general requirements to offer such a thing (maybe based on pax
exam/runner infrastructure) ?

Also, i guess integration testing is a very diverse term which does not help
to come up with a fit-it-all solution.

So, maybe i should ask here, what are the things you feel are missing from
TCK (think its it closeness but never seen it myself), bnd-test, atlassian
framwork (dan, can we see that somehwere ?) and pax exam ?

Toni

On Thu, Oct 8, 2009 at 12:29 PM, Richard S. Hall wrote:

> On 10/8/09 12:24, Don Brown wrote:
>
>> Since the TCK seems to be a deadend for automated testing, what other
>> options do we have?  Richard, you said you were working on a testing
>> framework, but I don't see it svn.  Are there a set of
>> integration/functional tests I'm missing?  I have a little framework
>> we use in Atlassian Plugins for integration testing that I could bring
>> over.
>>
>>
>
> I am using BND and my few tests are included in the my sandbox:
>
>http://svn.apache.org/repos/asf/felix/sandbox/rickhall/bnd-test/
>
> There is some [likely outdated] description of this here:
>
>http://felix.apache.org/site/bnd-testing-harness.html
>
> This isn't integrated in anyway, because there was no decision within the
> community to go with it, but it is still what I use when I create a new test
> cases. It is also what the OSGi TCK is based on.
>
> -> richard
>
>  Any objections?
>>
>> Don
>>
>>
>


-- 
Toni Menzel
Independent Software Developer
Professional Profile: http://okidokiteam.com
t...@okidokiteam.com
http://www.ops4j.org - New Energy for OSS Communities - Open
Participation Software.


Re: Integration testing

2009-10-08 Thread Karl Pauls
The more tests we have the better! Are you interested in bringing over
the tests as well? That would be cool :-)

regards,

Karl

On Thu, Oct 8, 2009 at 12:29 PM, Richard S. Hall  wrote:
> On 10/8/09 12:24, Don Brown wrote:
>>
>> Since the TCK seems to be a deadend for automated testing, what other
>> options do we have?  Richard, you said you were working on a testing
>> framework, but I don't see it svn.  Are there a set of
>> integration/functional tests I'm missing?  I have a little framework
>> we use in Atlassian Plugins for integration testing that I could bring
>> over.
>>
>
> I am using BND and my few tests are included in the my sandbox:
>
>    http://svn.apache.org/repos/asf/felix/sandbox/rickhall/bnd-test/
>
> There is some [likely outdated] description of this here:
>
>    http://felix.apache.org/site/bnd-testing-harness.html
>
> This isn't integrated in anyway, because there was no decision within the
> community to go with it, but it is still what I use when I create a new test
> cases. It is also what the OSGi TCK is based on.
>
> -> richard
>
>> Any objections?
>>
>> Don
>>
>



-- 
Karl Pauls
karlpa...@gmail.com


Re: Integration testing

2009-10-08 Thread Richard S. Hall

On 10/8/09 12:24, Don Brown wrote:

Since the TCK seems to be a deadend for automated testing, what other
options do we have?  Richard, you said you were working on a testing
framework, but I don't see it svn.  Are there a set of
integration/functional tests I'm missing?  I have a little framework
we use in Atlassian Plugins for integration testing that I could bring
over.
   


I am using BND and my few tests are included in the my sandbox:

http://svn.apache.org/repos/asf/felix/sandbox/rickhall/bnd-test/

There is some [likely outdated] description of this here:

http://felix.apache.org/site/bnd-testing-harness.html

This isn't integrated in anyway, because there was no decision within 
the community to go with it, but it is still what I use when I create a 
new test cases. It is also what the OSGi TCK is based on.


-> richard


Any objections?

Don