Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Equinox Testing - 3.3"
Line 10: | Line 10: | ||
===Application Model=== | ===Application Model=== | ||
* [http://www.eclipsecon.org/2007/ EclipseCon 2007] [[Equinox Application Model Demo | demo]] | * [http://www.eclipsecon.org/2007/ EclipseCon 2007] [[Equinox Application Model Demo | demo]] | ||
+ | * verifying that the scheduling works | ||
+ | * locking an application from running | ||
+ | * other advanced capabilities | ||
===Extension Registry=== | ===Extension Registry=== | ||
* dynamic contributions | * dynamic contributions | ||
+ | * verify that it works stand-alone | ||
+ | |||
+ | ===File-system=== | ||
+ | * verify that it works stand-alone | ||
+ | |||
+ | ===Jobs=== | ||
+ | * verify that it works stand-alone | ||
===Launcher=== | ===Launcher=== | ||
Line 21: | Line 31: | ||
* mutliple versions of the launcher JAR (exe search algorithm) | * mutliple versions of the launcher JAR (exe search algorithm) | ||
* headless mode with the exe (no dialogs) | * headless mode with the exe (no dialogs) | ||
+ | * plug-ins not co-located with exe | ||
===OSGi=== | ===OSGi=== | ||
Line 30: | Line 41: | ||
* Extension Registry and JSPs | * Extension Registry and JSPs | ||
* Test pieces used with other compatible components | * Test pieces used with other compatible components | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==PDE/Build== | ==PDE/Build== |
Revision as of 10:51, 19 March 2007
Contents
Test Machines
- MacOSx - Pascal
- Linux (RedHat) - DJ
- Linux (Suse) - Andrew
- Windows XP - Oleg, Simon
- Windows Vista - John
Equinox
Application Model
- EclipseCon 2007 demo
- verifying that the scheduling works
- locking an application from running
- other advanced capabilities
Extension Registry
- dynamic contributions
- verify that it works stand-alone
File-system
- verify that it works stand-alone
Jobs
- verify that it works stand-alone
Launcher
- command-line args
- specifying a splash (both in a jar and not)
- specifying a library
- failure cases
- mutliple versions of the launcher JAR (exe search algorithm)
- headless mode with the exe (no dialogs)
- plug-ins not co-located with exe
OSGi
- Running the JAR
- configuring the JAR
Server-Side
- Test on other servers (test bridge)
- Extension Registry and JSPs
- Test pieces used with other compatible components
PDE/Build
- There is a good demo from EclipseCon 2007.
- Bundle/Plug-in export.
- Headless builds.
- Reproduce product export.
- Packager
- Plug-in/Fragment classpaths
- Extensible API
- Cycle detection