On Fri, Sep 29, 2017 at 5:40 AM, Robert Sandell <[email protected]> wrote: > The original "selling points" for me with the ATH was that it provided ways > to test plugin functionality together with other plugins already installed. > […] > > Now getting that mode to work in the ATH is not simple so I guess very few > (if anyone) are running it in that way, I don't even know if that run mode > even works any more.
Not sure. If you just run against a regular 2.x WAR and specify `@WithPlugins`, only the specified plugins (and transitive dependencies) will be installed. I agree that it would be valuable to have a mode whereby everything mentioned in `platform-plugins.json` (or at least those which are `"suggested": true`) get loaded as well. This would let us know if some extensions or listeners conflict, if there are weird class loading issues with duplicated libraries, if some Jelly or JavaScript errors break rendering of unrelated page sections, and so on. Ullrich Hafner wrote: > converting them to integration tests would not make them much faster In my experience ATH-based tests are about an order of magnitude slower than `JenkinsRule`-based tests. YMMV -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr05j9VBZZPENUJFaNLpFH2Az6EKZVF6Hhb4Zd8hWa0GPA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
