You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Overview

The following results are for the core framework OSGi TCK test suites:

  • test.framework.classloading - Tests a gamut of covering including class loading and service registry behavior.
  • test.framework.classpath - Performs test covering importing and exporting of packages among bundles.
  • test.framework.div - Performs a diverse set of tests covering native code loading, bundle interface method implementations, and execution environment checking.
  • test.framework.dynpkgimport - Tests the dynamic import package mechanism.
  • test.framework.filter - Tests the Filter implementation.
  • test.framework.lifecycle - Tests bundle lifecycle behavior.
  • test.framework.registry - Tests the service registry.
  • test.framework.syncbundlelistener - Tests synchronous bundle listener support.
  • test.packageadmin.tc1 - Tests the Package Admin implementation.
  • test.packageadmin.tc2 - Tests the Package Admin implementation.
  • test.packageadmin.tc3 - Tests the Package Admin implementation.
  • test.packageadmin.tc5 - Tests the Package Admin implementation.
  • test.startlevel - Tests the Start Level implementation.
  • test.url - Tests the URL Handlers implementation.

Some of the above test suites do partially cover optional R4 features; however, test suites that specifically target optional core capabilities, such as the following, were not tested:

  • test.framework.fragments
  • test.permissionadmin.conditional
  • test.permissionadmin.main
  • test.permissionadmin.nosecurity
  • test.permissionadmin.security
  • test.permissionadmin.signature

Results

Results from: July 25th, 2006

The results for the core test suites are as follows:

  • test.framework.classloading
    • FAILED (passed 46 of 62 tests)
      • 2 failures need BundleContext.getAllServiceReferences(). (FELIX-32)
      • 11 failures need Require-Bundle. (FELIX-28)
      • 1 failure needs to check for duplicate directives on symbolic name when installing. (FELIX-100)
      • 1 failure needs support for exporting the same package more than once. (FELIX-101)
      • 1 failure needs support for singleton bundles. (FELIX-102)
  • test.framework.classpath
    • PASSED
  • test.framework.div
    • FAILED (passed 24 of 37 tests)
      • 1 failure needs execution environment checking. (FELIX-23)
      • 8 failures need improved native algorithm processing. (FELIX-26)
      • 1 failure needs Bundle.getResources() implemented. (FELIX-31)
      • 2 failures needs fragment support. (FELIX-29)
      • 1 failure needs bundle manifest localization. (FELIX-27)
  • test.framework.dynpkgimport
    • PASSED
  • test.framework.filter
    • PASSED
  • test.framework.lifecycle
    • PASSED
  • test.framework.registry
    • PASSED
  • test.framework.syncbundlelistener
    • PASSED
  • test.packageadmin.tc1
    • PASSED
  • test.packageadmin.tc2
    • PASSED
  • test.packageadmin.tc3
    • PASSED
  • test.packageadmin.tc5
    • FAILED (passed 0 of 40 tests)
      • Effectively, all 40 tests need Require-Bundle or fragment support. (FELIX-28 and FELIX-29)
  • test.startlevel
    • PASSED
  • test.url
    • PASSED

These results show that if optional OSGi R4 features are ignored, Felix is very close to being compliant with mandatory OSGi R4 features.

  • No labels