Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [epp-dev] package-wise source code & bug data information

Thank you Markus for the reply.

In the case of Eclipse, if I want to get some information such as coverage for Eclipse, etc. is it possible to find test suites or integration test cases that have been used to test the final package of Eclipse? I can reuse those tests after assembling Eclipse from the source and try to find coverage report for Eclipse.

Is there any way to get such test cases?

Thanks,
Sandeep Krishnan

On 10/28/2010 9:30 AM, Markus Knauer wrote:
Hi,

first some words about the bugs: Each and every Eclipse project defines one product and at least one component in Bugzilla. For the EPP packages there is exactly one component for every package that may be used by the users for filing bugs, but you cannot be sure what users are really doing. If you are looking at a package details page in the web (such as http://www.eclipse.org/downloads/packages/eclipse-ide-java-developers/heliossr1) you will find numbers and queries to resolved and open bugs for this particular package.

About the content: There is a list of features on the package details page (see above for an example) that defines the packages content. But please be aware that this list of feature is only a starting point for the p2 director that tries to find a solution to the given dependencies. So in the end there are *more* features installed in every package. That about the features... now: Every feature includes a set of bundles that are in the plugins directory of the package. All these bundles are from Eclipse projects and you should be able to guess from the bundle name which project created it. And these plugins/bundles *are* your package (i.e. not the features!). IMO the source doesn't help you that much, but maybe you should look at the Usage Data Collector output (http://eclipse.org/org/usagedata/ - for some unknown reason the data is currently unavailable).

Regards, Markus





Back to the top