Add unit tests for PrioritySorterRestriction class to address JENKINS-69757 #408
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.
This pull request introduces unit tests for the
PrioritySorterRestriction
class to address the issue outlined in JENKINS-69757.These tests ensure the class functions correctly and handles various scenarios, such as missing
ItemInfo
and priority range validations.These tests increase the code coverage of the code-base.
Testing done
PrioritySorterRestriction
logic:testCanTake_MissingItemInfo
: Verifies behavior whenItemInfo
is absent in theQueueItemCache
.testCanTake_PriorityRange
: TestscanTake
behavior for different priority values, validating edge conditions.testGetterMethods
: Ensures the correctness of getter methods and thatcanTake
works withRun
objects.Submitter checklist