felix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r929911 - in /websites/staging/felix/trunk/content: ./ documentation/development/using-the-osgi-compliance-tests.html
Date Thu, 20 Nov 2014 21:40:35 GMT
Author: buildbot
Date: Thu Nov 20 21:40:34 2014
New Revision: 929911

Log:
Staging update by buildbot for felix

Modified:
    websites/staging/felix/trunk/content/   (props changed)
    websites/staging/felix/trunk/content/documentation/development/using-the-osgi-compliance-tests.html

Propchange: websites/staging/felix/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Nov 20 21:40:34 2014
@@ -1 +1 @@
-1640817
+1640824

Modified: websites/staging/felix/trunk/content/documentation/development/using-the-osgi-compliance-tests.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/development/using-the-osgi-compliance-tests.html
(original)
+++ websites/staging/felix/trunk/content/documentation/development/using-the-osgi-compliance-tests.html
Thu Nov 20 21:40:34 2014
@@ -116,17 +116,26 @@ bundle subprojects.</p>
 <h2 id="testing-the-felix-framework">Testing the Felix framework</h2>
 <p>The Felix framework is tested against the core CT. The first thing to do is extract
the core
 CT JAR file, which includes test suites for:</p>
+<h3 id="core-functionality">Core functionality</h3>
 <ul>
-<li>Framework core (mandatory)</li>
-<li>Framework security (optional)</li>
-<li>Framework launching (mandatory)</li>
-<li>Framework launching security (optional)</li>
-<li>Package Admin (optional)</li>
-<li>Start Level (optional)</li>
-<li>URL Handlers (optional)</li>
-<li>Permission Admin (optional)</li>
-<li>Conditional Permission Admin (optional)</li>
+<li>Framework core (<code>org.osgi.test.cases.framework.bnd</code>)</li>
+<li>Framework launching (<code>org.osgi.test.cases.framework.launch.bnd</code>)</li>
+<li>Tracker Specification (<code>org.osgi.test.cases.tracker.bnd</code>)</li>
+<li>URL Handlers (<code>org.osgi.test.cases.url.bnd</code>)</li>
 </ul>
+<p>While the Tracker and URL Handler specifications are optional as per the OSGi Specification,
they are implemented by the 
+Felix Framework and therefore the tests should be run and pass.</p>
+<h3 id="security-components">Security components</h3>
+<p>OSGi Security components are optional. They are supported by Felix but require
+security support to be enabled. See the <a href="#security">Security</a> section
below for more details.</p>
+<ul>
+<li>Framework security (<code>org.osgi.test.cases.framework.secure.bnd</code>)</li>
+<li>Framework launching security (<code>org.osgi.test.cases.framework.launch.secure.bnd</code>)</li>
+<li>Permission Admin (<code>org.osgi.test.cases.permissionadmin.bnd</code>)</li>
+<li>Conditional Permission Admin (<code>org.osgi.test.cases.condpermadmin.bnd</code>)</li>
+</ul>
+<p>With security correctly enabled in Felix all the above security CT suites should
pass.</p>
+<h3 id="running-the-tests">Running the tests</h3>
 <p>For each of the associated BND files, the <code>-runpath</code> needs
to be edited to refer to the Felix
 framework. The easiest way to do this is by modifying the <code>shared.inc</code>
file which is included by 
 all BND files. It should look something like this after editing:</p>
@@ -138,14 +147,7 @@ all BND files. It should look something 
 
 <p>Typically, it is not necessary to change anything else in the BND files and it is
normal that
 the <code>-runbundles</code> setting is empty, since there are no additional
bundles associated with
-testing the framework. The exception to this is for the framework test suites for security.
-To test with security enabled, you will need to add the framework security provider in
-<code>-runbundles</code> like this:</p>
-<div class="codehilite"><pre><span class="o">-</span><span class="n">runbundles</span>
<span class="p">=</span> <span class="o">\</span>
-    <span class="o">/</span><span class="n">path</span><span class="o">/</span><span
class="n">to</span><span class="o">/</span><span class="n">felix</span><span
class="o">/</span><span class="n">framework</span><span class="p">.</span><span
class="n">security</span><span class="o">/</span><span class="n">org</span><span
class="p">.</span><span class="n">apache</span><span class="p">.</span><span
class="n">felix</span><span class="p">.</span><span class="n">framework</span><span
class="p">.</span><span class="n">security</span><span class="o">-</span>1<span
class="p">.</span>0<span class="p">.</span>0<span class="p">.</span><span
class="n">jar</span><span class="p">.</span><span class="n">jar</span><span
class="p">;</span><span class="n">version</span><span class="p">=</span><span
class="n">file</span>
-</pre></div>
-
-
+testing the framework. </p>
 <p>After editing the BND files, run the tests using:</p>
 <div class="codehilite"><pre><span class="n">source</span> <span
class="n">runtests</span>
 </pre></div>
@@ -165,6 +167,16 @@ framework.
 
 <p>Reports for the tests suites are generated in the <code>reports/</code>
subdirectory and are named
 after the appropriate test suite.</p>
+<h3 id="wzxhzdk11wzxhzdk12security"><a id="security"></a>Security</h3>
+<p><strong><em>TODO this section is unfinished.</em></strong></p>
+<p>The exception to this is for the framework test suites for security.
+To test with security enabled, you will need to add the framework security provider in
+<code>-runbundles</code> like this:</p>
+<div class="codehilite"><pre><span class="o">-</span><span class="n">runbundles</span>
<span class="p">=</span> <span class="o">\</span>
+    <span class="o">/</span><span class="n">path</span><span class="o">/</span><span
class="n">to</span><span class="o">/</span><span class="n">felix</span><span
class="o">/</span><span class="n">framework</span><span class="p">.</span><span
class="n">security</span><span class="o">/</span><span class="n">org</span><span
class="p">.</span><span class="n">apache</span><span class="p">.</span><span
class="n">felix</span><span class="p">.</span><span class="n">framework</span><span
class="p">.</span><span class="n">security</span><span class="o">-</span>1<span
class="p">.</span>0<span class="p">.</span>0<span class="p">.</span><span
class="n">jar</span><span class="p">.</span><span class="n">jar</span><span
class="p">;</span><span class="n">version</span><span class="p">=</span><span
class="n">file</span>
+</pre></div>
+
+
 <h3 id="deviations">Deviations</h3>
 <h4 id="core-r5">Core R5</h4>
 <p>When running the Core R5 CT the following error appears:</p>
@@ -222,7 +234,7 @@ after the appropriate test suite.</p>
 message to <a href="mailto:dev-subscribe@felix-apache-org">dev-subscribe@felix.apache.org</a>;
after
 subscribing, email questions or feedback to <a href="mailto:dev@felix.apache.org">dev@felix.apache.org</a>.</p>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1640817 by davidb on Thu, 20 Nov 2014 21:18:52 +0000
+        Rev. 1640824 by davidb on Thu, 20 Nov 2014 21:40:22 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project



Mime
View raw message