karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jamie G." <jamie.goody...@gmail.com>
Subject Re: [PROPOSAL] Refactore the itests to be more consistent
Date Thu, 06 Sep 2012 10:59:41 GMT
+1

On Thu, Sep 6, 2012 at 5:22 AM, Willem jiang <willem.jiang@gmail.com> wrote:
> It's good to see paxexam-karaf be a part of karaf :)
>
> --
> Willem Jiang
>
> FuseSource
> Web: http://www.fusesource.com (http://www.fusesource.com/)
> Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English)
>           http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese)
> Twitter: willemjiang
> Weibo: willemjiang
>
>
>
> On Thursday, September 6, 2012 at 2:05 AM, Andreas Pieber wrote:
>
>> BIIIIIIIIIIIIIIIIIIIG +1! Getting one paxexam-karaf release out with
>> 2.3.0 would finally let me get rid of the labs-paxexam-karaf version
>> :-) In addition it would make things easier for us.
>>
>> Great idea and great work JB.
>>
>> Kind regards,
>> Andreas
>>
>> On Wed, Sep 5, 2012 at 7:16 PM, Jean-Baptiste Onofré <jb@nanthrax.net (mailto:jb@nanthrax.net)>
wrote:
>> > Hi all,
>> >
>> > I started to work on integration tests and tooling in both Karaf 2.3.x and
>> > trunk this afternoon.
>> >
>> > The purpose is:
>> > - to improve the test coverage (at least testing most of/all Karaf commands,
>> > features installation, MBeans, etc).
>> > - rationalize the provided artifacts
>> >
>> > I have a couple of proposals:
>> > 0/ provide Karaf tooling exam in Karaf 2.3.x. We already discussed of that
>> > previously, but FYI, it's ready to be committed.
>> > 1/ move tooling/exam/regression into itests: the regression tests are a good
>> > thing, but I don't think it makes sense to have it in a separated module
>> > from exam. I would like to move the regression tests in the main itests
>> > module (in a dedicated package).
>> > 2/ remove itests/kittests. With the new Karaf tooling exam, the kittests are
>> > no more required. More over, this artifactId is not use in any part of Karaf
>> > anymore. I propose to remove the kittests module, if some util classes are
>> > required, they should be in the exam (options or container depending of the
>> > type of utils).
>> > 3/ increase itests coverage. I would like to tests most of/all Karaf
>> > commands, features and MBeans provided in Karaf.
>> >
>> > WDYT ?
>> >
>> > If you are OK, I have all these changes on my local git, I will commit it
>> > tomorrow.
>> >
>> > Regards
>> > JB
>> > --
>> > Jean-Baptiste Onofré
>> > jbonofre@apache.org (mailto:jbonofre@apache.org)
>> > http://blog.nanthrax.net
>> > Talend - http://www.talend.com
>>
>
>
>

Mime
View raw message