Overview
The following results are for the following core framework OSGi R4.2 TCK test suites:
- activationpolicy - Tests activation policies, i.e., lazy activation.
- classloading - Tests a gamut of covering including class loading and service registry behavior.
- classpath - Performs test covering importing and exporting of packages among bundles.
- div - Performs a diverse set of tests covering native code loading, bundle interface method implementations, execution environment checking, and manifest localization.
- dynpkgimport - Tests the dynamic import package mechanism.
- filter - Tests the Filter implementation.
- fragments- Tests bundle fragment behavior.
- lifecycle - Tests bundle lifecycle behavior.
- packageadmin - Tests the Package Admin implementation.
- resources - Tests access to resources using entry-related methods.
- service - Tests the service registry behavior, including service factories and service exceptions.
- startlevel - Tests the Start Level implementation.
- syncbundlelistener - Tests synchronous bundle listener support.
- url - Tests the URL Handlers implementation.
- framework.launch - Tests the launching and embedding API.
Some of the above test suites do partially cover optional features; however, test suites that specifically target optional core capabilities, such as the following, were not tested:
- permissionadmin.conditional
- permissionadmin.main
- permissionadmin.nosecurity
- permissionadmin.security
- permissionadmin.signature
Results
Results from: July 2nd, 2009
The results for the core test suites are as follows:
- activationpolicy
- classloading
- classpath
- div
- FAILED
- Passed 31 of 40 diverse tests (failing some execution environment and native library tests).
- Passed 10 of 13 manifest localization tests (failing localization with fragments).
- dynpkgimport
- filter
- fragments
- lifecycle
- packageadmin
- resources
- service
- startlevel
- syncbundlelistener
- url
- framework.launch
- FAILED
- Passed 14 of 15 tests (failing configuration support for trust repositories, this test will likely be moved to the security test suite).
Note that these results are based on the OSGi R4.2 TCK which has not officially been finalized yet, so details may change until that point.