Improve error when no bundle context is available #504
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: BJ Hargrave <hargrave@us.ibm.com>
We add a new common method to obtain the BundleContext for a test class. If the class is not in a bundle or the bundle is not started, the method will now throw an exception with the appropriate message. A test class must be in a bundle loaded by an OSGi framework and that bundle must be started (lazy activation is OK since the test runner must have loaded the test class which would complete activation). Signed-off-by: BJ Hargrave <hargrave@us.ibm.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We add a new common method to obtain the BundleContext for a test class.
If the class is not in a bundle or the bundle is not started, the
method will now throw an exception with the appropriate message.
A test class must be in a bundle loaded by an OSGi framework and that
bundle must be started (lazy activation is OK since the test runner
must have loaded the test class which would complete activation).