bdelacretaz commented on pull request #5: URL: https://github.com/apache/sling-org-apache-sling-junit-core/pull/5#issuecomment-732835451
> One option can delete the tests I made which were useful for my development efforts... That wouldn't be good! But modifying the tests so that they run automatically and are kept out of the final bundle is good, and that would address Julian's concern as well. I just added tests to the servlets-annotations module that run in a distinct build using `maven-invoker-plugin`and talk to the Sling instance under test via HTTP, in [commit 8c5fb2b](https://github.com/apache/sling-org-apache-sling-servlets-annotations/commit/8c5fb2becdb6cd79ff1798a041400829af3e5229). I think a similar setup would work for your tests, creating a distinct test bundle in the same junit-core repository and testing it via the invoker plugin? Happy to help with the "details" if needed. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
