We welcome and encourage community contributions to CloudSlang. Please familiarize yourself with the Contribution Guidelines and Project Roadmap before contributing. There are many ways to help CloudSlang:
- Report issues
- Fix issues
- Improve the documentation
The best way to directly collaborate with the project contributors is through GitHub: https://github.com/CloudSlang
- If you want to contribute to our code by either fixing a problem or creating a new feature, please open a GitHub pull request.
- If you want to raise an issue such as a defect, an enhancement request or a general issue, please open a GitHub issue.
Note that all patches from all contributors get reviewed. After a pull request is made, other contributors will offer feedback. If the patch passes review, a maintainer will accept it with a comment. When a pull request fails testing, the author is expected to update the pull request to address the failure until it passes testing and the pull request merges successfully.
At least one review from a maintainer is required for all patches (even patches from maintainers).
All contributions must include acceptance of the DCO:
Developer Certificate of Origin Version 1.1
Copyright (C) 2004, 2006 The Linux Foundation and its contributors. 660 York Street, Suite 102, San Francisco, CA 94110 USA
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or
(b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or
(c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.
(d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.
To accept the DCO, simply add this line to each commit message with your name and email address (git commit -s will do this for you):
Signed-off-by: Jane Example [email protected] For legal reasons, no anonymous or pseudonymous contributions are accepted.
We encourage and support contributions from the community. No fix is too small. We strive to process all pull requests as soon as possible and with constructive feedback. If your pull request is not accepted at first, please try again after addressing the feedback you received. To make a pull request you will need a GitHub account. For help, see GitHub's documentation on forking and pull requests. (https://help.github.com/articles/using-pull-requests/ )
Normally, all pull requests must include tests that test your change. Occasionally, a change will be very difficult to test. In those cases, please include a note in your commit message explaining why tests are not included.
JUnit is a unit testing framework that can be used to perform unit testing of software by writing test cases in Java. A common use for JUnit is to create a set of unit tests that can be run automatically when changes are made to software. In this way, developers can ensure that changes to the software they are creating do not break things that were previously functioning. Some common terms that you may encounter when reading about JUnit include:
- Test method: a method in a Java class that contains a single unit test;
- Test class: a Java class containing one or more test methods;
- Assertion: a statement that you include in a test method to check that the results of a test are as expected;
- Test suite: a grouping of test classes that are run together.
In general, unit tests should have the following characteristics:
- They test a small bit (or "unit") of code. If the tests test "too much" then they become less useful, as it will not be clear which bit of code is causing the test to fail;
- They do not depend on external resources such as databases. The reason for this is so that the tests can be run in a variety of environments and so that multiple concurrent executions of the unit tests do not interfere with each other;
- They should run quickly. This is to encourage the tests to be run as often as possible, even as often as every compile. If the tests take too long to execute, developers will be less likely to run them often.
Apply the following rules when writing unit tests for the cs-jenkins @Actions:
-
Create a consistent package structure between the tests and the classes under test
If you want to develop a unit test for the class ExampleClass located in the io.cloudslang.content.some_integration folder, under the test folder it is recommended to create the same package structure like the one the ExampleClass class is located in. This is the Apache Software Foundation's standard directory structure, and it enables the user to transition more easily from a plugin to another, while also be able to leverage modern IDE features that calculate unit test code coverage.
-
Mock server calls
In your test methods, don't use real calls to servers. If you want to test a method like executeHttpRequest(Url url), don't perform a real HTTP request, instead use one of the industry established mocking frameworks (e.g. Mockito, EasyMock, Powermock ) to mock the request and create isolation unit tests using a framework like JUnit.
Whether you are a regular contributor or a newcomer, we care about making this community a safe place for you.
We are committed to providing a friendly, safe and welcoming environment for all regardless of their background and the extent of their contributions. Please avoid using nicknames that might detract from a friendly, safe and welcoming environment for all. Be kind and courteous. Those who insult, demean or harass anyone will be excluded from interaction. In particular, behavior that excludes people in socially marginalized groups will not be tolerated. We welcome discussion about creating a welcoming, safe and productive environment for the community. If you have any questions, feedback or concerns please let us know. ([email protected])