There are two goals for the unittests:

1. Verify that kustomizations are applied correctly (kubeflow#1014)
2. Verify that various conventions are enforced (kubeflow#1015)

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

1. Check in one more "kustomization.yaml" files corresponding to test cases

2. 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

3. Unittests run "kustomize build" and compare output to expected output to ensure kustomize packages are in sync with the expected output

4. Make commands make it easy to regenerate the expected output as part of a change.

   cd tests
   make generate-changed-only