Yeah, I'm not to sure about how to test groovy scripts in general, but testing anything in vars can be tough when Jenkins steps like sh are used. So as you said, the general approach here is to keep the code inside vars as small and trivial as possible while testing can be done for "conventional" classes. Therefore I don't have any code coverage numbers for the vars stuff
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great guide! Have you tried getting code coverage numbers for the vars files?
I guess it doesn't matter in this approach, since the var files don't really have much logic, but curious nevertheless.
Yeah, I'm not to sure about how to test groovy scripts in general, but testing anything in
varscan be tough when Jenkins steps likeshare used. So as you said, the general approach here is to keep the code insidevarsas small and trivial as possible while testing can be done for "conventional" classes. Therefore I don't have any code coverage numbers for thevarsstuff