How to mock Jenkins commands (like steps.stash) to test shared library about jenkinspipelineunit HOT 5 CLOSED

@barlogy

To mock httpRequest I've just did

helper.registerAllowedMethod(
    method("httpRequest", Map.class),
    { _ -> ["content": "{}"] }
)

It's working but I don't know if there is a better way

from jenkinspipelineunit.

is it still actual?

from jenkinspipelineunit.

In my test, I needed to mock readJSON. Well, it's not fully a mock, since it does actually parse the JSON.

helper.registerAllowedMethod('readJSON', [Map], { req -> new groovy.json.JsonSlurper().parseText(req.text) })`

from jenkinspipelineunit.

Can this library provide default mocks? For readJSON something that actually reads JSON like the above would be a nice default. Having mocked out readJSON a few times, I understand that this would be difficult tho - it accepts a path to a file including a relative path and so such a mock needs to have a sense for where its workspace is.

from jenkinspipelineunit.

@jcrben This library provides default mocks for all basic pipeline steps (which was finalized in #518). However, as the readJSON step is part of a plugin (pipeline-utility-steps), there is no default mock for it and you must create your own as @gene-pavlovsky detailed above.

Generally speaking, I don't think that this library should provide default mocks for anything other than the basic pipeline steps, or else it'll be a slippery slope and BasePipelineTest will get bloated.

There is one notable exception to this policy, which is for the docker-workflow plugin, because its mocks are somewhat complex and also because it is very widely-used.

from jenkinspipelineunit.