Hi Sling Dev SlingAnnotationsTestRunner is one of my favorite ways to test because it make my life simpler when doing Test Driven Development in Sling. Using this tool I have had fewer setup and dependency problems because it runs in the instance I develop and deploy to. SlingAnnotationsTestRunner can run JUnit tests in any of my various Sling instances (local, staging and production), which is super handy when diagnosing and troubleshooting remote server problems. QA, Ops, Admins and developers can easily run the JUnit tests after updates and restarts using the web-based user interface.
Unfortunately SlingAnnotationsTestRunner was marked as deprecated in 2015 stating "TeleporterRule is a much simpler way of executing” That maybe true in your experience, but TeleporterRule does not provide me the same value. IMO project developers should have a choice whether to use SlingAnnotationsTestRunner or TeleporterRule for their project. For some TeleporterRule may be better indeed. For me, SlingAnnotationsTestRunner is perfect when I’m trying to develop projects in Sling. SlingAnnotationsTestRunner Junit tests do not increase Maven build speed, and the UI allows me to run all the tests or just the ones I want. In summary, could I please volunteer to keep SlingAnnotationsTestRunner.java alive, supported and not deprecated? Regards Cris https://github.com/apache/sling-org-apache-sling-junit-core/blob/master/src/main/java/org/apache/sling/junit/annotations/SlingAnnotationsTestRunner.java
