improve CI with integration tests
Open
Nobody has claimed this yet.
ci
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
we should improve CI so that we can run proper integration tests (i.e. the charts actually work). This is important for things like:
- ensuring any obvious runtime issues are caught during development (like runtime Kubernetes YAML rejections that the linter does not catch)
- ensuring tests work (i.e. diagnostics in the
rstudio-workbenchchart)
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
Start by reviewing the repository's existing CI configuration and the charts, especially rstudio-workbench. Determine how integration tests can exercise rendered charts against Kubernetes and cover runtime YAML rejection and diagnostics. Done means CI runs these checks reliably and catches the stated failures during development.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100