base on BDD styled unit test framework for Kubernetes Helm charts as a Helm plugin. # helm unittest [](https://github.com/helm-unittest/helm-unittest/actions) [](https://goreportcard.com/report/github.com/helm-unittest/helm-unittest) [](https://sonarcloud.io/dashboard?id=helm-unittest_helm-unittest) [](https://www.bestpractices.dev/projects/9365) [](https://scorecard.dev/viewer/?uri=github.com/helm-unittest/helm-unittest) Unit test for _helm chart_ in YAML to keep your chart consistent and robust! Feature: - write test file in pure YAML - render locally - create **nothing** on your cluster - [wildcard selection for templates](./DOCUMENT.md#test-suite) - [define values and release options](./DOCUMENT.md#test-job) - [snapshot testing](#snapshot-testing) - [test suite code completion and validation](#test-suite-code-completion-and-validation) ## Documentation If you are ready for writing tests, check the [DOCUMENT](./DOCUMENT.md) for the test API in YAML. - [Install](#install) - [Docker Usage](#docker-usage) - [Get Started](#get-started) - [Test Suite File](#test-suite-file) - [Templated Test Suites](#templated-test-suites) - [Usage](#usage) - [Flags](#flags) - [Yaml JsonPath Support](#yaml-jsonpath-support) - [DocumentSelector](#documentselector) - [Example](#example) - [Snapshot Testing](#snapshot-testing) - [Dependent subchart Testing](#dependent-subchart-testing) - [Tests within subchart](#tests-within-subchart) - [Test suite code completion and validation](#test-suite-code-completion-and-validation) - [Frequently Asked Questions](#frequently-asked-questions) - [Related Projects / Commands](#related-projects--commands) - [Contributing](#contributing) ## Install ``` $ helm plugin install https://github.com/helm-unittest/helm-unittest.git ``` It will install the latest version of binary into helm plugin directory. ## Docker Usage ``` # run help of latest helm with latest helm unittest plugin docker run -ti --rm -v $(pwd):/apps helmunittest/helm-unittest # run help of specific helm version with specific helm unittest plugin version docker run -ti --rm -v $(pwd):/apps helmunittest/helm-unittest:3.11.1-0.3.0 # run unittests of a helm 3 chart # make sure to mount local folder to /apps in container docker run -ti --rm -v $(pwd):/apps helmunittest/helm-unittest:3.11.1-0.3.0 . # run unittests of a helm 3 chart with Junit output for CI validation # make sure to mount local folder to /apps in container # the test-output.xml will be available in the local folder. docker run -ti --rm -v $(pwd):/apps helmunittest/helm-unittest:3.11.1-0.3.0 -o test-output.xml -t junit . ``` The docker container contains the fully installed helm client, including the helm-unittest plugin. ## Get Started Add `tests` in `.helmignore` of your chart, and create the following test file at `$YOUR_CHART/tests/deployment_test.yaml`: ```yaml suite: test deployment templates: - deployment.yaml tests: - it: should work set: image.tag: latest asserts: - isKind: of: Deployment - matchRegex: path: metadata.name pattern: -my-chart$ - equal: path: spec.template.spec.containers[0].image value: nginx:latest ``` and run: ``` $ helm unittest $YOUR_CHART ``` Now there is your first test! ;) ## Test Suite File The test suite file is written in pure YAML, and default placed under the `tests/` directory of the chart with suffix `_test.yaml`. You can also have your own suite files arrangement with `-f, --file` option of cli set as the glob patterns of test suite files related to chart directory, like: ```bash $ helm unittest -f 'my-tests/*.yaml' -f 'more-tests/**/*.yaml' my-chart ``` Check [DOCUMENT](./DOCUMENT.md) for more details about writing tests. ### Templated Test Suites You may find yourself needing to set up a lots o tests that are a parameterization of a single test. For instance, let's say that you deploy to 3 environments `env = dev | staging | prod`. In order to do this, you can actually write your tests as a helm chart as well. If you go about this route, you must set the `--chart-tests-path` option. Once you have done so, helm unittest will run a standard helm render against the values.yaml in your specified directory. ``` /my-chart /tests-chart /Chart.yaml /values.yaml /templates /per_env_snapshots.yaml /Chart.yaml /values.yaml /.helmignore /templates /actual_template.yaml ``` In the above example file structure, you would maintain a helm chart that will render out against the Chart.yaml that as provided and the values.yaml. With rendered charts, any test suite that is generated is automatically ran we do not look for a file postfix or glob. **Note:** since you can create multiple suites in a single template file, you must provide the suite name, since we can no longer use the test suite file name meaningfully. **Note 2:** since you can be running against subcharts and multiple charts, you need to make sure that you do not designate your `--chart-tests-path` to be the same folder as your other tests. This is because we will try to render those non-helm test folders and fail during the unit test. **Note 3:** for snapshot tests, you will need to provide a helm ignore that ignores `*/__snapshot__/*`. Otherwise, subsequent runs will try to render those snapshots. The command for the above chart and test configuration would be: ```shell helm unittest --chart-tests-path tests-chart my-chart ``` ## Usage ``` $ helm unittest [flags] CHART [...] ``` This renders your charts locally (without tiller) and runs tests defined in test suite files. ### Flags ``` --color enforce printing colored output even stdout is not a tty. Set to false to disable color --strict strict parse the testsuites (default false) -d --debugPlugin enable debug logging (default false) -v, --values stringArray absolute or glob paths of values files location to override helmchart values -f, --file stringArray glob paths of test files location, default to tests\*_test.yaml (default [tests\*_test.yaml]) -q, --failfast direct quit testing, when a test is failed (default false) -h, --help help for unittest -t, --output-type string the file-format where testresults are written in, accepted types are (JUnit, NUnit, XUnit) (default XUnit) -o, --output-file string the file where testresults are written in format specified, defaults no output is written to file -u, --update-snapshot update the snapshot cached if needed, make sure you review the change before update -s, --with-subchart charts include tests of the subcharts within charts folder (default true) --chart-tests-path string the folder location relative to the chart where a helm chart to render test suites is located ``` ### Yaml JsonPath Support Now JsonPath is supported for mappings and arrays. This makes it possible to find items in an array, based on JsonPath. For more detail on the [`jsonPath`](https://github.com/vmware-labs/yaml-jsonpath#syntax) syntax. Due to the change to JsonPath, the map keys in `path` containing periods (`.`) or special characters (`/`) are now supported with the use of `""`: ```yaml - equal: path: metadata.annotations["kubernetes.io/ingress.class"] value: nginx ``` The next releases it will be possible to validate multiple paths when JsonPath result into multiple results. ### DocumentSelector The test job or assertion can also specify a documentSelector rather than a documentIndex. Note that the documentSelector will always override a documentIndex if a match is found. This field is particularly useful when helm produces multiple templates and the order is not always guaranteed. The `path` in the documentSelector has Yaml JsonPath Support, using JsonPath expressions it is possible to filter on multiple fields. The `value` in the documentSelector can validate complete yaml objects. ```yaml ... tests: - it: should pass values: - ./values/staging.yaml set: image.pullPolicy: Always resources: limits: memory: 128Mi template: deployment.yaml documentSelector: path: metadata.name value: my-service-name asserts: - equal: path: metadata.name value: my-deploy ``` ## Example Check [`test/data/v3/basic/`](./test/data/v3/basic) for some basic use cases of a simple chart. ## Snapshot Testing Sometimes you may just want to keep the rendered manifest not changed between changes without every details asserted. That's the reason for snapshot testing! Check the tests below: ```yaml templates: - templates/deployment.yaml tests: - it: pod spec should match snapshot asserts: - matchSnapshot: path: spec.template.spec # or you can snapshot the whole manifest - it: manifest should match snapshot asserts: - matchSnapshot: {} ``` The `matchSnapshot` assertion validate the content rendered the same as cached last time. It fails if the content changed, and you should check and update the cache with `-u, --update-snapshot` option of cli. ``` $ helm unittest -u my-chart ``` The cache files is stored as `__snapshot__/*_test.yaml.snap` at the directory your test file placed, you should add them in version control with your chart. ## Dependent subchart Testing If you have hard dependency subcharts (installed via `helm dependency`) existed in `charts` directory (they don't need to be extracted), it is possible to unittest these from the root chart. This feature can be helpful to validate if good default values are accidentally overwritten within your default helm chart. ```yaml # $YOUR_CHART/tests/xxx_test.yaml templates: - charts/postgresql/templates/xxx.yaml tests: - it: set: # this time required to prefix with "postgresql." postgresql.somevalue: should_be_scoped asserts: - ... ``` Note 1: if dependent subcharts uses an alias, use the alias name in the templates. Note 2: using the folder structure in templates can also be used to unittest templates which are placed in subfolders or unittest subcharts from the rootchart. Check [`test/data/v3/with-subchart/`](./test/data/v3/with-subchart) as an example. ## Tests within subchart If you have customized hard dependency subchart (not installed via `helm dependency`, but added manually) existed in `charts` directory, tests inside would also be executed by default. You can disable this behavior by setting `--with-subchart=false` flag in cli, thus only the tests in root chart will be executed. Notice that the values defined in subchart tests will be automatically scoped, you don't have to add dependency scope yourself: ```yaml # with-subchart/charts/child-chart/tests/xxx_test.yaml templates: - templates/xxx.yaml tests: - it: set: # no need to prefix with "child-chart." somevalue: should_be_scoped asserts: - ... ``` Check [`test/data/v3/with-subchart/`](./test/data/v3/with-subchart) as an example. ## Test Suite code completion and validation Most popular IDEs (IntelliJ, Visual Studio Code, etc.) support applying schemas to YAML files using a JSON Schema. This provides comprehensive documentation as well as code completion while editing the test-suite file:  In addition, test-suite files can be validated while editing so wrongfully added additional properties or incorrect data types can be detected while editing:  ### Visual Studio Code When developing with VSCode, the very popular YAML plug-in (created by RedHat) allows adding references to schemas by adding a comment line on top of the file: ```yaml # yaml-language-server: $schema=https://raw.githubusercontent.com/helm-unittest/helm-unittest/main/schema/helm-testsuite.json suite: http-service.configmap_test.yaml templates: [configmap.yaml] release: name: test-release namespace: TEST_NAMESPACE ``` Alternatively, you can add the schema globally to the IDE, using a well defined pattern: ```json "yaml.schemas": { "https://raw.githubusercontent.com/helm-unittest/helm-unittest/main/schema/helm-testsuite.json": ["charts/*/tests/*_test.yaml"] } ``` ### IntelliJ Similar to VSCode, IntelliJ allows mapping file patterns to schemas via preferences: Languages & Frameworks -> Schemas and DTDs -> JSON Schema Mappings  ## Frequently Asked Questions As more people use the unittest plugin, more questions will come. Therefore a [Frequently Asked Question page](./FAQ.md) is created to answer the most common questions. If you are missing an answer to a question, feel free to raise a ticket. ## Related Projects / Commands This plugin is inspired by [helm-template](https://github.com/technosophos/helm-template), and the idea of snapshot testing and some printing format comes from [jest](https://github.com/facebook/jest). And there are some other helm commands you might want to use: - [`helm template`](https://github.com/kubernetes/helm/blob/master/docs/helm/helm_template.md): render the chart and print the output. - [`helm lint`](https://github.com/kubernetes/helm/blob/master/docs/helm/helm_lint.md): examines a chart for possible issues, useful to validate chart dependencies. - [`helm test`](https://github.com/kubernetes/helm/blob/master/docs/helm/helm_test.md): test a release with testing pod defined in chart. Note this does create resources on your cluster to verify if your release is correct. Check the [doc](https://github.com/kubernetes/helm/blob/master/docs/chart_tests.md). Alternatively, you can also use generic tests frameworks: - [Python](https://github.com/apache/airflow/issues/11657) - Go - [terratest](https://blog.gruntwork.io/automated-testing-for-kubernetes-and-helm-charts-using-terratest-a4ddc4e67344) ## License MIT ## Contributing Issues and PRs are welcome! To start developing this plugin please follow the [Contribution](./CONTRIBUTING.md) guidelines. ", Assign "at most 3 tags" to the expected json: {"id":"12181","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"