-
Notifications
You must be signed in to change notification settings - Fork 116
Migrate tests to JUnit5 #302
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Migrate tests to JUnit5 #302
Conversation
* Migrate annotations and imports * Migrate assertions * Remove public visibility for test classes and methods * Minor code cleanup
basil
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Incomplete:
There is one exception where a migration was not possible as the tests rely on
Ruleimplementations that have not (yet) been migrated to JUnit5:ThrottleJobPropertyPipelineRestartTestusingJenkinsSessionRule(in combination withSemaphoreStep)
While it is possible to use |
|
From what I understood https://github.com/jenkinsci/workflow-support-plugin/blob/a600813d04aac835e7e2bf62a8aaa775c4cd4437/src/test/java/org/jenkinsci/plugins/workflow/test/steps/SemaphoreStep.java#L60 uses the |
basil
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Incomplete:
There is one exception where a migration was not possible as the tests rely on
Ruleimplementations that have not (yet) been migrated to JUnit5:ThrottleJobPropertyPipelineRestartTestusingJenkinsSessionRule(in combination withSemaphoreStep)
6714355 to
1a58f3d
Compare
|
@basil Now all tests are migrated using the latest JTH version |
This PR aims to migrate all tests to JUnit5. Changes include:
I also took the freedom of re-enabling
ThrottleConcurrentTestand refactor it to no longer rely onjgiven.IMHO there is no need for this test in particualar to use it and its better to streamline it with other tests in this plugin.
I am well aware that this is a quite large changeset however I hope that there is still interest in this PR and it will be reviewed.
If there are any questions, please do not hesitate to ping me.
Submitter checklist