The composite tests should be ported because of the changes in
the API. However, there are also some changes in classes, which are not part of
the framework API, but still there are tests for them. These tests should be
modified too, in order to be able to run against the new version of the
framework. Probably one more bug will be needed, in which to submit patches for
them. I may open it, so we can submit patches there, as well as in the one you
opened for the composites.
equinox-dev-bounces@xxxxxxxxxxx [mailto:equinox-dev-bounces@xxxxxxxxxxx] On
Behalf Of Thomas Watson
Sent: Thursday, May 13, 2010 4:40 PM
To: Equinox development mailing list
Subject: Re: [equinox-dev] Equinox tests in OSGI_4_3_RI branch
Yes, porting of the tests are planned for 3.7.
I have not started a branch of the tests, but I can and would be glad for you
to provide patches to port the tests. Only the composite tests should need to
be ported since that is the only API that has changed between the branch and
what is in HEAD. My plan was to evaluate the tests for composites and see if
there is anything in there that is not already tested by the OSGi CT for
composites. The OSGi CT for composites is pretty good I think (well I can't
really say because I wrote them ;-) ). My hope is that all is covered by the CT
(and likely more) such that we could get rid of the composite tests in Equinox
or reduce it to a small set of smoke tests to ensure things are not broken from
build to build.
I opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=312784
to track this. I will create a branch for the tests.
"Kirchev, Lazar" ---05/13/2010 04:10:20
AM---Hello, In the OSGI_4_3_RI branch equinox tests are transferred as they are
in the HEAD branch. Due to the changes in the framew
Equinox development mailing list
05/13/2010 04:10 AM
[equinox-dev] Equinox tests in OSGI_4_3_RI
In the OSGI_4_3_RI branch equinox tests are transferred as they are in the HEAD
branch. Due to the changes in the framework, some of the tests do not compile â
there are modified constructors of non-API classes, ambiguous methods, etc.
I would like to ask is the porting of the tests already planned, and if yes â
is there any timeframe for finishing it? Since we will be working on the new
code, we are interested in the tests being fixed and being ready to run against
the new framework. If the porting of the tests has not already been planned, we
may participate in it with providing patches to fix the tests.
equinox-dev mailing list