CheckOps
chart-testing
chart-testing (ct) is an Apache-2.0 CLI from the Helm project for linting and install-testing Helm charts changed in a pull request, typically on a kind cluster.
Latest public signals
Not refreshed yet. Refresh reads the public site and, when the entry has a GitHub repository, the latest release.
Introduction
chart-testing, or ct, is the Helm project’s CLI for linting and testing Helm charts. It is designed for chart repositories and monorepos: it detects which charts changed compared with a target branch and tests only those.
ct lint runs helm lint, validates Chart.yaml against a schema, checks maintainers and enforces version bumps. ct install installs each changed chart into a cluster (often kind), runs helm test hooks, optionally tests upgrades from the previous version, and cleans up. The official chart-testing GitHub Action wraps it for CI.
In the quality loop it is the integration test for charts, confirming they actually install and pass their own tests.
The source code is at helm/chart-testing on GitHub under the Apache-2.0 licence, with about 1,600 stars; the most recent commit was on 10 November 2026.
Features
- Change detection: Tests only charts changed against a target branch.
- Lint: helm lint plus schema and version checks.
- Install tests: Install charts and run helm test hooks.
- Upgrade tests: Upgrade from the previous chart version.
- Values files: Test multiple ci/*-values.yaml configurations.
- GitHub Action: Official action for CI.
Pros
- Official tooling: Maintained under the Helm organisation.
- Free to use: Open source under the Apache-2.0 licence, so the core tool costs nothing to use.
- Actively maintained: The repository had commits as recent as 10 November 2026.
Cons
- Cluster required: Install tests need a cluster.
- Repo conventions: Assumes a chart repository layout.
- Slower: Real installs take minutes.
Usage and Links (Example)
ct lint --target-branch main
kind create cluster
ct install --target-branch main --upgrade
Resources:
Pricing
chart-testing is free and open source under the Apache-2.0 licence.
Recommended for?
- Helm chart repositories with many charts.
- Teams that want install and upgrade tests in pull requests.
Conclusion
chart-testing is the standard way to lint and install-test changed charts.
Pair it with helm-unittest for fast template-level checks.
On CheckOps, chart-testing is filed under the Integration testing and Release & CI gates stages. Related tools listed here include KUTTL, Chainsaw, kind, helm-unittest, kubeconform and kube-score. A short trial on a real project, with your own code, data and pipeline, is usually the fastest way to choose between them, because fit matters more than feature lists. Facts here come from the official site, documentation and repository, checked on 11 November 2026.
Alternatives
Other tools on CheckOps that cover similar ground. Open a page, or compare one with chart-testing side by side.
KKUTTLKUTTL (KUbernetes Test TooL) is an Apache-2.0 declarative testing tool for Kubernetes operators and resources, using YAML test steps and assertions against a real or kind cluster.Compare with chart-testing
CChainsawChainsaw is an Apache-2.0 declarative end-to-end testing tool for Kubernetes operators and controllers from the Kyverno project, with steps, assertions, cleanup and reports in YAML.Compare with chart-testing
Kkindkind (Kubernetes IN Docker) is an Apache-2.0 tool from Kubernetes SIGs that runs local multi-node Kubernetes clusters in Docker containers, widely used for CI testing.Compare with chart-testing
Hhelm-unittesthelm-unittest is an MIT Helm plugin for BDD-style unit tests of Kubernetes Helm chart templates, written in YAML with snapshot support.Compare with chart-testing
Kkubeconformkubeconform is an Apache-2.0 fast Kubernetes manifest validator that checks YAML against Kubernetes JSON schemas, including custom resources.Compare with chart-testing- Kkube-scorekube-score is an MIT static analysis tool for Kubernetes objects that gives recommendations for reliability and security, such as resource limits, probes and pod disruption budgets.Compare with chart-testing