Thanks Jesse, indeed I'm using the JenkinsRule for some non UI integrations tests.
Why did I ask for such a specific question? My aim is to ensure the shared library has been tested not just using the JenkinsPipelineUnit but a more realistic use cases, therefore I can minimise the chances to find any errors either when the CI ecosystem is updated/upgraded and help to use Gherkin or a similar BDD approach to help to any of the users. A kind of similar approach has been done with JCasC, for instance https://github.com/jenkinsci/configuration-as-code-plugin/tree/master/demos/active-directory is now validated using a specific IT: - https://github.com/jenkinsci/configuration-as-code-plugin/blob/master/integrations/src/test/java/io/jenkins/plugins/casc/ActiveDirectoryTest.java The complexity of that particular approach is to define all the dependencies, including the ones which should be excluded, for instance: https://github.com/jenkinsci/configuration-as-code-plugin/pull/1080#issuecomment-536287707 . Within the maven POM file. That's the reason I wanted to use the CWP to help to build the customised Jenkins war with the plugins which are required to be used within the JenkinsRule. ATH might be too overkilling as I'm not interested in using the UI though. Any suggestions/approaches to tackle this? Thanks On Friday, 27 September 2019 21:13:03 UTC+1, Jesse Glick wrote: > > On Fri, Sep 27, 2019 at 2:43 PM Victor Martinez > <[email protected] <javascript:>> wrote: > > Unfortunately, the JenkinsRule does not populate all the plugins which > were bundled with, > > > > Is that the expected behaviour? > > Yes. `JenkinsRule` cares nothing for bundled plugins. Only plugins in > the test classpath are loaded. > > Did you really want to use `acceptance-test-harness` or something? I > think you are using `jenkins-test-harness` for something well outside > its design space. > -- 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/12dc3366-ae01-4088-94cf-73d3442b3a35%40googlegroups.com.
