kudobuilder / kudobuilder/operators
run tests for operators which are relevant to the changes in the PR
- Dominant language
- Shell
- Stars
- 237
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
right now we are running some tests for any change in the repository. Those tests are for just for zookeeper operator. In case we change some other operator logic, these tests are irrelevant.
we should only run the tests related to that operator or no tests in case we don't have any for that operator. We need to ensure that:
- CI run tests that are relevant to the changes done in the PR
- PR status provide feedback on which tests are being run
- Provide documentation/examples on how to add tests for an operator
In all cases, the PR checks should provide information around which tests have been run for a certain PR. To enable users to write tests for their own operators that can live in this repository.
Contributor guide
Research direction
Start by examining the repository's existing CI checks and the current Zookeeper operator test setup. Determine how changed operators can be identified and how test selection and reporting should work. Done means relevant checks run for each change, PR status identifies them, and contributors have examples for adding operator tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, documentation, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100