| Eclipse
3.2 Test Plan |
 |
Equinox - Platform/Runtime (the REAL runtime - OSGi, bundles, extensions, etc.)
- configuration area
- read/only configurations
- run from locked (read-only) install
- shared configurations
- moving configurations
- buddy loading and usage of context finders. Pay attention to RMI based use cases.
- standalone OSGi with and without security enabled
- use bundles that do not require OSGi in a regular java app without OSGi (common, registry, ...)
- run the equinox bundles on the smallest VM specified in the Required EE (this might mean getting an xml parser from somewhere else, see eRCP for example)
- test that the hooks that are supposed to handle multiple instances of an OSGi adaptor do so
- verify readability of the error message when eclipse is started with the wrong level of JRE
- test extensibility of the registry API
|
|
RCP App
- Author and run an RCP app against foundation (or the smallest EE required for RCP)
|
|
Platform/Resources
|
|
PDE/Build
- Headless product builds. Try a case where code is actually fetched from CVS.
- Branding for all the official eclipse platforms (change icons, executable, splash screen, etc.)
- Cross-platform export from windows, linux, mac to all the official supported platforms
- Use execution environment exception rules from the build.properties
- Access restrictions based on import / export package, require bunde and x-friends
- Custom steps in a plug-in
|