-
Notifications
You must be signed in to change notification settings - Fork 23
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
Unit tests for PluginModernizer class #731
Comments
Hi Sir @jonesbusy , The error logs indicate that the version for the artifact plugin was expected to be 5.5, but it was found to be 5.6. Here’s the specific part of the error log:
It seems like this version change is causing the build to fail. Could you please look into this discrepancy? I’ve attached the relevant portion of the pom.xml file that is causing the issue. Thank you for your time, and I look forward to your feedback. |
I also checked my java, maven versions . They are fine too ! |
yaa tests are failing in system too |
Why not bump version until updatecli merge the PR? We have a contributor that did it on his PR Don't expect maintainers to give you always the information. |
See #733 |
Thanks Sir for your quick response, and sorry for any confusion caused earlier! |
Fixes jenkins-infra#731 Add unit tests for the `PluginModernizer` class. * Add `PluginModernizerTest` class in `plugin-modernizer-core/src/test/java/io/jenkins/tools/pluginmodernizer/core/impl/PluginModernizerTest.java`. * Mock dependencies: `Config`, `MavenInvoker`, `GHService`, `PluginService`, `CacheManager`. * Test `validate` method to ensure it calls `mavenInvoker.validateMaven`, `mavenInvoker.validateMavenVersion`, and `ghService.connect`. * Test `listRecipes` method to ensure it logs available recipes. * Test `isDryRun`, `getGithubOwner`, `getSshPrivateKeyPath`, `getMavenVersion`, `getMavenHome`, `getMavenLocalRepo`, `getCachePath`, `getJavaVersion` methods to ensure they return correct values. * Test `cleanCache`, `start`, `process`, `collectMetadata`, `compilePlugin`, `verifyPlugin`, `printResults`, `printModifiedFiles` methods to ensure they perform expected actions.
What feature do you want to see added?
This class doesn't have any test.
It's implicitly validaded by integration tests, but it deserve unit test as well
Upstream changes
No response
Are you interested in contributing this feature?
No response
The text was updated successfully, but these errors were encountered: