Eclipse test results' analysis
please, send suggestions to joaoarthurbm@gmail.com
Sign in to Google to save your progress. Learn more
About the data
I analyzed the official test reports. I'm analyzing them over time, that is, the data regards to all the reports between versions 3.4 and 4.3. Since I have historical data, I’m able to determine the lifecycle of a problem.

The problems are categorized as follows:

1) API Usage Problems (illegally extends,illegally implements, illegally instantiates... )

2) Using some entity that is not defined in the bundle.

Example: The method java.util.regex.Pattern.pattern() referenced in ui.internal.activities.ActivityPatternBinding.getString() is not defined in the bundle's required execution environment: CDC-1.1/Foundation-1.1

3) Binaries Incompatibility/Versioning.

Example: The minor version should be incremented in version 3.3.100.v20080521, because reexported bundle org.eclipse.ui has changed its minor version

Please, answer as many as possible. I really appreciate it!
How many years have you been contributing to Eclipse?
Did you know about the restriction rules that produce these problems?
Clear selection
Distribution of Problems per Category
What is the most critical category?
Clear selection
What is the less critical category?
Clear selection
Distribution of Problem per plugin (considering all versions)
Why do you think jdt.ui, swt and ui.workbench concentrate so many problems?
Distribution of Problem per plugin in the last version (4.3)
In the past, a number of jdt.ui problems were fixed. Why and how were they fixed?
Next
Clear form
Never submit passwords through Google Forms.
This content is neither created nor endorsed by Google. - Terms of Service - Privacy Policy

Does this form look suspicious? Report

Google Forms