helm-chart-tester SKILL.md skillA

helm-chart-tester from testland/qa is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add testland/qa/helm-chart-tester@git:20260813.aa0ffc9

Pins git:20260813.aa0ffc9 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: testland/qa
Path: plugins/qa-iac/skills/helm-chart-tester/SKILL.md
Versions recorded: 5
Latest version: git:20260813.aa0ffc9, committed Aug 13, 2026
First version recorded: Jul 6, 2026
Size: 7,603 bytes
Repository stars: 11
License: MIT

Configures helm-unittest for Helm chart unit testing - installs the `helm-unittest` plugin, authors `tests/*.yaml` per template, asserts on rendered manifests (`isKind`, `equal`, `matchRegex`, snapshots), plus `helm lint` and `helm template` render testing. Use to verify a chart's template logic and rendered shape; this is unit-level correctness testing, not security scanning - to enforce policy on rendered manifests use policy-as-code-runner, and to scan charts for misconfigurations use…

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# helm-chart-tester

## Overview

**helm-unittest** (Helm plugin) unit-tests the rendered chart
output - assert specific fields, conditional behaviors, value
substitutions - to catch template bugs before deploying.

## When to use

- Team ships Helm charts (in-house apps, OSS contributions).
- A chart has conditional logic (`{{ if .Values.foo }}`); tests
  verify both branches.
- A chart's rendered output must satisfy specific shape contracts
  (env vars, ports, labels).

## Step 1 - Install

```bash
helm plugin install https://github.com/helm-unittest/helm-unittest
helm plugin list   # verify
```

## Step 2 - Author a test

```yaml
# charts/mychart/tests/deployment_test.yaml
suite: deployment template
templates:
  - templates/deployment.yaml
tests:
  - it: should set the right image
    set:
      image.repository: myapp
      image.tag: v1.2.3
    asserts:
      - isKind:
          of: Deployment
      - equal:
          path: spec.template.spec.containers[0].image
          value: myapp:v1.2.3

  - it: should add the configured env vars
    set:
      env:
        - name: API_URL
          value: https://api.example.com
        - name: LOG_LEVEL
          value: debug
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add testland/qa/helm-chart-tester@sha256:0273a966d5748cca

The line at the top of this page pins the label git:20260813.aa0ffc9, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_krtp3jwurqiue5az.svg)](https://markdownregistry.com/a/art_krtp3jwurqiue5az)

1 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 5 versions of this file, between Jul 6, 2026 and Aug 13, 2026, about one every 10 days.

version	committed	commit	size	audit
git:20260813.aa0ffc9 latest	2026-08-13	aa0ffc9	7,603 B	A	view · diff
git:20260726.e26b0d9	2026-07-26	e26b0d9	7,602 B	A	view · diff
git:20260724.d4db756	2026-07-24	d4db756	7,469 B	A	view · diff
git:20260718.ab29907	2026-07-18	ab29907	7,543 B	A	view · diff
git:20260706.4e1409c	2026-07-06	4e1409c	7,644 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (7603 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

testland/qa · 11 stars · license MIT · pushed 2026-10-20 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_krtp3jwurqiue5az
GET https://markdownregistry.com/api/v1/resolve?ref=testland/qa/helm-chart-tester
GET https://markdownregistry.com/api/v1/blob/0273a966d5748ccaed812c573457ece69594cd03dcce4f7b92f35294d024b061

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from testland/qa

CLAUDE.md CLAUDE.md file

testland/qa · CLAUDE.md

git:20261011.164aa71 · audit A · 11 stars

a11y-violation-gate SKILL.md skill

testland/qa · plugins/qa-accessibility/skills/a11y-violation-gate/SKILL.md · Builds a CI gate that fails the build on **new** WCAG / a11y violations introduced by a PR while grandfathering…