Investigate automated testing for shared library

[michaelsauter]

See discussion in #146.

From #146 (comment):

Hm, for experimenting locally with Jenkinsfiles I often use https://github.com/jenkinsci/jenkinsfile-runner since @ungerts recommended it to me a few months ago.

From #146 (comment):

On my agenda is also to take a look at https://github.com/jenkinsci/JenkinsPipelineUnit

[michaelsauter]

@oalyman Can you add your findings to this ticket as well?

[oalyman]

As the ods-jenkins-shared-library uses the jenkins-client-plugin I had a look into how this is tested.

They are doing a full-blown integration test by building a Jenkins image with a snapshot of their changes and then running the extended tests from origin e.g. pipeline_jenkins_e2e.go

Reference Link PR-Testing ods-jenkins-shared-library.

[metmajer]

Worth noting that there seemed to be some consensus on using Spock for unit testing in #146, so this shouldn't go unmentioned.

[metmajer]

@hugowschneider I invite you to a tour through how we automatically test the MRO Jenkins shared library that powers the Release Manager. Meanwhile > 7500 autoamted tests ;-)

[renedupont]

I picked that up again and integrated https://github.com/jenkinsci/JenkinsPipelineUnit next to Spock to the shared lib in this merged PR #202
If no one objects, I'd see that issue as completed as we now have Spock and this JenkinsPipelineUnit integrated in the shared lib.
There are still many tests to write, but I guess that is another story.

[michaelsauter]

I see this as closed. @renedupont put the framework in place, and I am doing further refactoring and adding tests along the way.