As an open source project, we encourage contributions from the community to help Testrun remain an expanding but stable product. To contribute, follow the steps below:
-
Sign the Google Contributor License Agreement (CLA).
- Whether you're an individual or contributing on behalf of your organization, you must be covered by a Google CLA.
-
Determine the scope of your contribution.
- Keep it simple. Your contribution is more likely to be accepted if you change fewer files.
- Ensure your pull request addresses one thing, such as a bug fix, dependency issue, or new framework capability.
-
Reach out to the core maintainers at [email protected].
- They can provide confirmation that your proposed changes meet our objectives and align with Testrun principles, making them more likely to be accepted.
-
Fork Testrun and get developing.
- We aim to provide thorough and clear developer documentation to help you contribute successfully.
To ensure code quality, use the appropriate style guide when developing code for Testrun:
The current code base has zero code lint issues. To maintain this, all lint checks are enforced on pull requests to dev and main. You should ensure these lint checks pass before marking your pull requests as Ready for review.