...

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

• test.activationpolicy - Tests activation policies, i.e., lazy activation.
• 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.fragments- Tests bundle fragment behavior.
• 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.permissionadmin.conditional
• test.permissionadmin.main
• test.permissionadmin.nosecurity
• test.permissionadmin.security
• test.permissionadmin.signature

Results

Results from: September 1st, 2006 with some updates from December 20th, 2007 (all failure results should be freshened)October 17th, 2008

The results for the core test suites are as follows:

• test.activationpolicy
  • Not tested, since not yet implemented.
• test.framework.classloading
  • FAILED (passed 61 of 62 tests)
    • 1 failure needs support for singleton bundles. (FELIX-102)
  • PASSED
• test.framework.classpath
  • PASSED
• test.framework.div
  • FAILED (passed 30 25 of 37 40 tests)
    • 1 failure needs execution environment checking. (FELIX-23)
    • 1 failure needs native selection algorithm parameter alias processing. (FELIX-26)
    • 1 failure needs fragment support for native libraries. (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
• • • Need to investigate, there have been regressions.
• test.framework.dynpkgimport
  • PASSED
• test.framework.filter
  • PASSES
• test.framework.filter
  • FAILED (passed 7 of 36 tests)
    • 8 failures for boot class path extensions, but we don't set SUPPORTS_BOOTCLASSPATH_EXTENSION to true. Need to re-test with property set.
    • 9 failures for framework extensions.
• 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)PASSED
• 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.