[
https://issues.apache.org/jira/browse/SLING-9915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17239302#comment-17239302
]
Bertrand Delacretaz commented on SLING-9915:
--------------------------------------------
One note on debugging the integration tests setup from
[https://github.com/apache/sling-org-apache-sling-junit-core/tree/SLING-9915-junit-annotation-int-tests]
: a convenient way to check the instance under test is to start the tests with
{code}
cd src/it/annotations-it/
mvn clean verify -Dannotations.bundle.version=1.1.1-SNAPSHOT
-Dmaven.failsafe.debug
{code}
And set a breakpoint in the {{ReferenceIT.waitForSling()}} method. The Sling
instance under test should be ready, and the {{/system/sling/junit}} servlet
available.
This is convenient for troubleshooting the instance's setup, unresolved bundles
etc.
The OSGi framework runs in a different process than the {{ReferenceIT}} class ,
to debug it the {{pax.vm.options}} POM property should be used to setup that
JVM for debugging.
> Remove deprecated flags for SlingAnnotationsTestRunner and TestReference
> ------------------------------------------------------------------------
>
> Key: SLING-9915
> URL: https://issues.apache.org/jira/browse/SLING-9915
> Project: Sling
> Issue Type: Task
> Components: JUnit Core
> Affects Versions: JUnit Core 1.1.0
> Reporter: Cris Rockwell
> Assignee: Cris Rockwell
> Priority: Minor
> Labels: test, tools
>
> As per discussion thread
> https://www.mail-archive.com/[email protected]/msg100097.html
> Revert this commit
> https://github.com/apache/sling-org-apache-sling-junit-core/commit/c7f98b1172126f1e5f961ec9d17d12b239c34e0d
> Reviving annotations
> @TestReference
> @SlingAnnotationsTestRunner
> Review docs and suggest updates
> https://sling.apache.org/documentation/development/sling-testing-tools.html
> https://sling.apache.org/documentation/bundles/org-apache-sling-junit-bundles.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
