dpishchukhin / org.knowhowlab.osgi.testing Goto Github PK

• Bundle events
• Service events
• Framework events

See https://groups.google.com/forum/#!topic/knowhowlab-osgi-testing/gXRpKRTTL3s

Basically there needs to be a way to assert that an event is posted when the event will be triggered by a call from the test code itself. The following will likely miss the event.

fireEvent(topicX);
assertEvent(topicX, 500);

And the following will fail before the event is ever fired:

assertEvent(topicX, 500);
fireEvent(topicX);

Perhaps something like:

EventListener listener = new EventListener(topicX, filter);
fireEvent(topicX);
listener.assertEvent(500);

• Bundle events
• Service events
• Framework events

when using any bundle assertion method, as the assertBundleAvailable("org.my.bundle", new Version("6.0.0")) and it fails then I get this kind of message:
java.lang.AssertionError: null

Would be nice to get a default message, probably "Bundle 'org.my.bundle' is not available"

Create an artifact with utils and assertions together.

now that osgi 6 is out with consolidated support of resources capabilities, would be good to have methods to assert that the bundle provides or requires the right capabilities (between others) at IT runtime...

I think the implementation in

https://github.com/dpishchukhin/org.knowhowlab.osgi.testing/blob/master/org.knowhowlab.osgi.testing.assertions/src/main/java/org/knowhowlab/osgi/testing/assertions/ServiceAssert.java#L455

is incorrect.
Instead the call must wait for the specified amount (timeout). If it sees the service to be null once within that timeframe, it should return true.
Right now the call returns "false" even though i said that i expect the service goes away within the next 1000ms. E.g. because i just removed a configuration object for a managed factory service.