[
https://issues.apache.org/jira/browse/SLING-10497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Sedding resolved SLING-10497.
------------------------------------
Fix Version/s: Junit Core 1.1.4
Resolution: Fixed
Implemented with commit
[f6e6837|https://github.com/apache/sling-org-apache-sling-junit-core/commit/f6e6837f6445e492c3b43b024e847fe98a33eca7].
> JUnit Jupiter ParameterResolver for OSGi
> ----------------------------------------
>
> Key: SLING-10497
> URL: https://issues.apache.org/jira/browse/SLING-10497
> Project: Sling
> Issue Type: New Feature
> Components: JUnit Core, Testing
> Affects Versions: JUnit Core 1.1.2
> Reporter: Julian Sedding
> Assignee: Julian Sedding
> Priority: Minor
> Fix For: Junit Core 1.1.4
>
>
> Sling JUnit Core provides support for server-side tests, i.e. tests running
> within an OSGi environment. The bundle has recently been enhanced to
> (optionally) support the use of "JUnit Platform"-based {{TestEngine}}s. This
> allows running e.g. Jupiter (aka JUnit 5) tests.
> However, currently there is no Jupiter-style way to easily access OSGi
> services, as all existing utilities are tied to JUnit 4 APIs (e.g.
> {{TestRunner}} or {{TestRule}}).
> It would be desirable to allow easy access to OSGi services and the
> {{BundleContext}}/{{Bundle}} objects in Jupiter tests. This is typically done
> using a {{ParameterResolver}}, which allows injecting objects as method or
> constructor parameters.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
