[
https://issues.apache.org/jira/browse/SLING-8553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-8553:
-----------------------------------
Fix Version/s: (was: Connection Timeout Agent 1.0.2)
Connection Timeout Agent 1.0.4
> Add OSGi integration test
> -------------------------
>
> Key: SLING-8553
> URL: https://issues.apache.org/jira/browse/SLING-8553
> Project: Sling
> Issue Type: Task
> Components: Extensions
> Reporter: Robert Munteanu
> Priority: Major
> Fix For: Connection Timeout Agent 1.0.4
>
>
> In [sling-org-apache-sling-connection-timeout-agent commit
> 01d35c7|https://github.com/apache/sling-org-apache-sling-connection-timeout-agent/commit/01d35c7]
> an OSGi-specific fix was applied but there was no corresponding integration
> test.
> The potential fix is to add a Pax-Exam tests which adds:
> - a HTTP client bundle ( any of the supported ones should do )
> - a client using the HTTP client bundle
> And then assert that the requested class was transformed. It may be a good
> idea to do the assertion using JMX.
> The only issue to consider is that I did not find good information on running
> Pax-Exam with JUnit 5. We currently use JUnit 5 for the connection timeout
> agent.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
