Refactor JenkinsJobRunner to allow unit testing#54
Merged
null511 merged 1 commit intonull511:masterfrom May 9, 2025
Merged
Conversation
… mock (so it uses interface and not concrete class)
Owner
|
I haven't worked on this in quite a while, but looks like a good change; not sure how I missed that. Going to blindly merge without testing now 👍 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In order to properly unit test code that relies on the library, I would like to adjust the
JenkinsJobRunnerto accept an interface, thus allowing the whole flow that uses it to be mockable.