Jump to: navigation, search

Difference between revisions of "Equinox Testing - 3.3"

Line 16: Line 16:
 
===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
 
* verify that it works stand-alone
  
Line 42: Line 36:
 
* Extension Registry and JSPs
 
* Extension Registry and JSPs
 
* Test pieces used with other compatible components
 
* Test pieces used with other compatible components
 +
 +
==Runtime==
 +
 +
===File-system===
 +
* verify that it works stand-alone
 +
 +
===Jobs===
 +
* verify that it works stand-alone
 +
  
 
==PDE/Build==
 
==PDE/Build==

Revision as of 12:02, 19 March 2007

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

Launcher & Splash Screen

  • 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
  • splash screen demos from EclipseCon 2007

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

Runtime

File-system

  • verify that it works stand-alone

Jobs

  • verify that it works stand-alone


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