Difference between revisions of "Equinox Testing - 3.3"

From Eclipsepedia

Jump to: navigation, search
(PDE/Build)
(OSGi)
Line 42: Line 42:
 
* Running the JAR
 
* Running the JAR
 
* configuring the JAR
 
* configuring the JAR
* Running the OSGi TCK
 
 
* testing the supplement bundle
 
* testing the supplement bundle
 +
==== Running the OSGi TCK ====
 +
The project equinox-incubator/org.eclipse.equinox.tcksetup in the equinox incubator provides the necessary scripts and configuration settings to run the osgi TCK.  Checkout the project and follow the instructions in the readme file in the root of the project.
  
 
===Server-Side===
 
===Server-Side===

Revision as of 12:20, 20 March 2007

Contents

Test Machines

Eclipse 3.3 M6

  • Tom - Application Model, OSGi
  • Andrew - Launcher/Splash Screen
  • Oleg - Extension Registry
  • Simon - Server-side
  • John - Jobs
  • DJ - File-system, OSGi
  • Pascal - PDE/Build

Test machine allocation (post 3.3 M6)

  • 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
  • testing the supplement bundle

Running the OSGi TCK

The project equinox-incubator/org.eclipse.equinox.tcksetup in the equinox incubator provides the necessary scripts and configuration settings to run the osgi TCK. Checkout the project and follow the instructions in the readme file in the root of the project.

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
  • Review contribution of integration tests