da561762dd
|
||
|---|---|---|
| .. | ||
| katib/installs | ||
| legacy_kustomizations | ||
| scripts | ||
| stacks | ||
| testdata_gcp_kpt/gcp | ||
| tests/legacy_kustomizations | ||
| tools | ||
| workflows | ||
| Makefile | ||
| OWNERS | ||
| README.md | ||
| doc.go | ||
| go.mod | ||
| go.sum | ||
| test_util.go | ||
| validate_resources_test.go | ||
README.md
Kustomize Manifest Tests
Unittests
There are two goals for the unittests:
- Verify that kustomizations are applied correctly (kubeflow/manifests#1014)
- Verify that various conventions are enforced (kubeflow/manifests#1015)
Verifying Kustomizations Are Applied Correctly
Examples of kustomizations that we would like to verify are applied and generate the expected output
- Patches
- Variable substitution
- Composition of resources
The general approach to doing this is
-
Check in one more "kustomization.yaml" files corresponding to test cases
-
Run "kustomize build -o ..." and check in the output as the expected test output
- Reviewers can verify changes to the expected output to ensure changes have the desired effect on the expected output
-
Unittests run "kustomize build" and compare output to expected output to ensure kustomize packages are in sync with the expected output
-
Make commands make it easy to regenerate the expected output as part of a change.
cd tests make generate-changed-only