unify cloud and kind integration tests
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
We have two different integration test jobs, one which runs integration tests in kind, and one which runs integration tests in a number of clouds. The kind integration tests run the deep, upgrade, helm, custom_domain, and external_issuer tests whereas the cloud integration tests run only the deep, upgrade, and helm tests.
The fact that both jobs run a different set of tests is confusing and it can be difficult to know which tests are or should be run in each environment. Furthermore, having the list of tests defined in two different places means that the two lists could unintentionally drift apart.
Ideally there would be one single list of tests which is run in all environments.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the kind and cloud integration-test jobs and compare where their test lists are defined. Start with the existing deep, upgrade, helm, custom_domain, and external_issuer integration tests, then verify that both environments consume one shared list and no longer drift.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- ci-cd, testing
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100