re: How-To: Setup a unit-testable Jenkins shared pipeline library VIEW POST


Thanks for the article Adrian!
Nice implementation. One piece of feedback, in the test case, it is accepting any string as valid input. I was wondering if it would be better if the test case asserted the specific string.

verify(_steps).sh(echo \"building some/path/to.sln...\")


Good catch, it probably would. Looks like I was a little bit lazy at the time of writing and just decided to with anyString() ;) Thanks for the feedback

code of conduct - report abuse