Hi David,
I'd like to turn this process around. If you see a failure in
jbosgi-repository please describe the issue in the context of that
project. The functional scope should be defined in the jbosgi-repository
testsuite and not in some external testsuite that is not publicly
accessible. The best approach is probably to create a pull request with
failing tests against jbosgi/jbosgi-repository.
cheers
-thomas
On 05/25/2012 09:09 AM, David Bosschaert wrote:
Hi Thomas,
I've written a few tests for the Repo CT most of which fail at the
moment. You can find them on my davidb/repo_ct branch in OSGi git here:
https://www.osgi.org/members/gitweb/build.git/blob/davidb/repo_ct:/org.os...
The two tests that are passing are testQueryByBundleID() and
testDisconnectedQueries(). The other tests fail.
It should be fairly clear what the tests are doing, I'm also attaching
a test report FYI to show what fails.
If you want to run it, you need to copy the following into the OSGi
build:
licensed/repo/org.jboss.logging.jboss-logging/
licensed/repo/org.jboss.repository.jbosgi-repository-tck/
licensed/repo/org.jboss.repository.jbosgi-repository/
The jbosgi-repository-tck is a bundle that currently exists here:
https://github.com/bosschaert/jbosgi-repository/tree/tckbundle/tck
The test suite is not yet complete, but this is a start to work through.
Cheers,
David
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx