We should develop some of our own testcases to get complete coverage. The OSGi test suite can be used by the committers (which are also OSGi members) during our test pass for each mile stone. The OSGi test cases should not be considered as a complete test suite, in many cases they will let bugs slip by. Every bug we fix which the OSGi test suite did not catch should likely have an automated testcase created.
We have looked into running the OSGi TCK with each build during the junit
tests, but the effort was high and in the end it was decided to run the
OSGi TCK as part of our manual milestone test pass.
Tom
From: Pavlin Dobrev <[EMAIL PROTECTED]>
To: Equinox development mailing list <[email protected]>
Date: 10/15/2007 10:11 AM
Subject: Re[2]: [equinox-dev] Graduation of Prosyst contributed bundles
All of the bundles that implement OSGi defined services:
org.eclipse.equinox.ds
org.eclipse.equinox.ip
org.eclipse.equinox.wireadmin
org.eclipse.equinox.io
pass the corresponding OSGi test cases. How you proceed in this case
because OSGi test cases are not publicly available?
-Pavlin
> We also will need to setup automated tests for the bundles which are
> graduated. (See
https://bugs.eclipse.org/bugs/show_bug.cgi?id=206333)
Tom
Thomas Watson---10/15/2007 09:28:05 AM---The bundles contributed by Prosyst
have been in
the incubator since July. The codebase Prosyst donated is already
production qu
From:
Thomas Watson/Austin/[EMAIL PROTECTED]
To:
[email protected]
Date:
10/15/2007 09:28 AM
Subject:
[equinox-dev] Graduation of Prosyst contributed
bundles
The bundles contributed by Prosyst have been in the incubator since July.
The codebase
Prosyst donated is already production quality and has been used in many
products at
Prosyst. A small number of issues have been reported against the bundles in
the incubator.
But these are to be expected and the committers from Prosyst have been
responsive in
addressing the issues. At this point I would like to ask Prosyst which of
the incubator
bundles would they like to graduate and support in the Equinox-Bundles
component?
We have the following bundles to consider:
org.eclipse.equinox.util
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=181731)
org.eclipse.equinox.ds
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=181733)
org.eclipse.equinox.ip
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=181734)
org.eclipse.equinox.wireadmin
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=181736)
org.eclipse.equinox.io
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=181737)
The last four bundles (ds, ip, wireadmin, io) all provide implementations
to OSGi
specifications and do not provide public API. I am concerned about the
amount of public API
in the org.eclipse.equinox.util bundle (see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=206151).
We should consider the following when making this decision:
1) Which bundles does the community need? We do not need to graduate all
the bundles if we
determine that the community is not interested in all of them.
2) Which bundles do we have sufficient resources to support at the
graduated level.
3) How much API will be graduated. Graduated API has a long term commitment
and requires a
lot of review and must be positioned such that we do not break
compatibility while evolving
the API after graduation.
Tom
_______________________________________________
equinox-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/equinox-dev
<<inline: graycol.gif>>
<<inline: ecblank.gif>>
<<inline: 11635088.gif>>
<<inline: 11456193.gif>>
_______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev
