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é
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com

Reply via email to