-
Notifications
You must be signed in to change notification settings - Fork 258
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
Improve automated test coverage #114
Comments
Hi @MarkEWaite could you assign me to this issue? Appreciate any initial pointers for working on this as a first time contributor. Thanks in advance. |
@adamtkac I'm delighted that you're willing to contribute. There is enough work on this topic that I don't bother to assign it to a single person. You can start the work and submit a pull request. See the Jenkins gitter Hacktoberfest chat channel for a recent discussion about assessing test coverage of a plugin and writing new unit tests based on that result. The steps are:
|
Thank you for your answer. It is possible to divide issue to partial issues, depending on parts of code which needs to be covered first? I will start do my best as soon as I can. |
Yes, you're welcome to create additional issues that track specific classes where you are focusing implementation. |
…extensions package
Improve automated test coverage #114 - Add test for classes in default package
Improve automated test coverage #114 - Add test for classes in extensions package
|
I've not seen that failure before. I don't have access to a macOS machine, but I confirmed that the tests run as expected multiple times on a FreeBSD 13.1 machine (closest thing I have to macOS). The web response is definitely a Jenkins response. I don't know why it would report that the resource cannot be found. |
Thanks Mark, I thought it might be related to SECURITY-595, because I did also run into 404 with
But I'm not sure where to add this while running unittest...Im gonna try couple things see if I can get it working.. |
Increase automated test coverage
Automated test coverage of the embeddable build status plugin is quite low. Improve the automated test coverage by submitting pull requests with new automated tests.
Review current coverage
Review the current test coverage with the commands:
Linux
Windows
More information is in the "code coverage" section of the contributing guide.
Create a new test for a class that is not well covered
Most integrated development environments have tools that will create a test stub that is a good beginning. Apache Netbeans has "Create / Update tests" . JetBrains IntelliJ has "Create tests". Visual Studio Code has the "Extension Pack for Java".
Use the IDE or your own coding to create a test for one of the classes that is not well covered by tests.
Keep the test small so that the pull request is easy to review.
The text was updated successfully, but these errors were encountered: