Jump to: navigation, search

Difference between revisions of "Equinox Testing - 3.3"

(Application Model)
(Application Model)
Line 20: Line 20:
  
 
===Application Model===
 
===Application Model===
The following test scenario use [[Equinox Application Model Demo | Application Model Demo]] presented at [http://www.eclipsecon.org/2007/ EclipseCon 2007]
+
The following test scenario use [[Equinox Application Model Demo | Application Model Demo]] presented at [http://www.eclipsecon.org/2007/ EclipseCon 2007].  Checkout the following projects from the equinox incubator and follow the steps below:
# checkout the following projects from the equinox incubator
+
 
<code>
 
<code>
 
  equinox-incubator/demos/app-model/org.eclipse.equinox.examples.app.selector
 
  equinox-incubator/demos/app-model/org.eclipse.equinox.examples.app.selector
Line 31: Line 30:
 
  equinox-incubator/demos/app-model/org.eclipse.swt.examples.paint
 
  equinox-incubator/demos/app-model/org.eclipse.swt.examples.paint
 
</code>
 
</code>
 +
 
# Export a project using the file /org.eclipse.equinox.examples.app.selector/AppSelector.product
 
# Export a project using the file /org.eclipse.equinox.examples.app.selector/AppSelector.product
 
# Launch the product with the -console option (e.g. eclipse -console)
 
# Launch the product with the -console option (e.g. eclipse -console)

Revision as of 16:03, 20 March 2007

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

The following test scenario use Application Model Demo presented at EclipseCon 2007. Checkout the following projects from the equinox incubator and follow the steps below:

equinox-incubator/demos/app-model/org.eclipse.equinox.examples.app.selector
equinox-incubator/demos/app-model/org.eclipse.equinox.examples.sharedisplay
equinox-incubator/demos/app-model/org.eclipse.swt.examples.addressbook
equinox-incubator/demos/app-model/org.eclipse.swt.examples.browserexample
equinox-incubator/demos/app-model/org.eclipse.swt.examples.clipboard
equinox-incubator/demos/app-model/org.eclipse.swt.examples.graphics
equinox-incubator/demos/app-model/org.eclipse.swt.examples.paint

  1. Export a project using the file /org.eclipse.equinox.examples.app.selector/AppSelector.product
  2. Launch the product with the -console option (e.g. eclipse -console)
  3. Attempt to launch all the applications using the application selector. Verify that the status of each application changes to "running"
  4. Stop all the applications by closing each individual application window (except for the application selector window). Verify that the status for each application changes to "inactive"
  5. Run the "apps" console command to get a list of available applications
  6. Start each launchable application using the "startApp" console command. Note that you can use a substring of the application id when launching (e.g. startApp paint). Verify that the status for each application started is reflected in the application selector. You can also verify the status by running the "apps" command.
  7. Stop each app using the "stopApp" console command. Verify that each application window is closed and the proper status is reflected in the application selector.
  8. Lock the paint application by running the console command "lockApp paint".
  9. Attempt to start the paint application by running the console command "startApp paint". Verify that an exception is thrown indicating the application is locked. Also run the console command "apps" to verify that paint application is locked.
  10. Close and restart the application selector. Verify the paint application is persistently locked.
  11. Unlock the paint application by running the console comand "unlockApp paint".
  12. Attempt to start the paint application by running the console command "startApp paint". Verify that the application is launched. Close and restart the application selector. Verify the paint application is not locked.
  13. Schedule a reccuring launch of the paint application by running the console command "schedApp paint (minute=*) true". This schedules the application to be launched once every minute. Run the apps command to confirm that the paint application is scheduled. Verify that the paint application is launched within 1 minute.
  14. Close the paint application. Wait for 1 minute and and verify that the paint application is launched again.
  15. Close and restart the application selector. Verify that the paint application is still scheduled. Wait for 1 minute and verify that the paint application is launched.
  16. Unschedule the paint application by running the console command "unschedApp paint". Verify the paint application is no longer scheduled. Close the paint application and wait for 2 minutes and verify the paint application is not launched.
  17. Close and restart the application selector. Verify that the paint application is no longer scheduled.

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