---
# System prepended metadata

title: Ideas for chart-testing v3

---

# Ideas for chart-testing v3

* General Helm v3 compatibility https://github.com/helm/chart-testing/pull/184
* Possible public GitHub Action (and depending, also possible GH App) to run chart-testing v3
* Revisit test modes (changed charts, all charts, specific charts, ...)
* Use plugin system for adding linters
  https://github.com/helm/chart-testing/pull/165
* Maybe no longer bundle linters but document how to add them (yamllint, conftest, kubeval)?
    * These could be supported via the exec-based plugin system and be bundled by the chart-testing docker image but not used by default with the go binary.
* Stream pod logs (from deployments, statefulsets, etc)
* Stream hook/test logs (depends on https://github.com/helm/helm/issues/6020)
* Stream k8s events attached to hook/test resources
* Refactor codebase
  * Be more idiomatic
  * Better testability
  * Generate mocks?
* Look at existing issues
* Option to create test reports with pluggable formats (e. g. JUnit)
* Add more linting to CI (use golangci as Helm does?)
* ~~Switch to Go modules~~
* ~~Start dev-v3 branch?~~
* Drop goreleaser? We should push a latest image from master which is probably not so easy with goreleaser
* Support single chart testing use case (https://github.com/helm/chart-testing/issues/125)
* Improve error handling and logging. Should we use a logging library and structured logging?
