volker.raschekandCopilot
fef4190a74
Bash / bash-unittest (push) Successful in 14s
Bash / shellcheck (push) Successful in 20s
changelog / changelog (push) Successful in 16s
Helm / helm-lint (push) Successful in 15s
Helm / helm-unittest (push) Successful in 32s
Markdown linter / markdown-lint (push) Successful in 15s
Markdown linter / markdown-link-checker (push) Successful in 56s
The contributor guidelines never defined how a `suite` title has to look, only how an `it` title has to look. Without a rule five competing schemes grew side by side: `config template | cache config`, `deployment template (probes)`, `ServiceMonitor template (basic)`, `Test Gateway API httpRoute.yaml` and `Dependency checks | Customization integrity | valkey`. 24 of the 49 titles started with a lowercase letter, which contradicts the sentence rule that already applies to the test titles. More than cosmetics, the missing rule produced three concrete defects: - `deployment template` was used by both deployment-additional-config.yaml and extraInitContainers.yaml, and `Init template` by both init_directory_structure.sh.yaml and its rootless counterpart. `helm unittest` identifies a failing suite by its title, so a failure in either file printed the same header and the report did not say which file to open. - deployment/inline-config.yaml was titled `config template`, although it lives in the deployment directory and asserts on secret_inlineConfig.yaml. It read like a sixth member of the `config template | ...` group. - persistentVolumeClaim.yaml was titled `PVC template`, using exactly the short name the chart conventions forbid for files and keys. All suites now follow `Test <subject> <scenario>`, for example `Test deployment probes` or `Test gateway API httpRoute`. The subject is the template under test, the scenario is what distinguishes the suite from its siblings, so every title is unique and sorts next to its related suites. The `Test ` prefix of the Gateway API, ingress and route suites is kept, because it is the only part of the old schemes that already read as a sentence; the redundant `.yaml` suffix and the `tests` suffix of the storage class suite are dropped. The rule is written down in the Unit Tests section of the copilot instructions, so the next suite does not have to guess which of the five schemes was meant. Co-authored-by: Copilot <copilot@github.com>
114 lines
3.7 KiB
YAML
114 lines
3.7 KiB
YAML
suite: Test deployment extraInitContainers
|
|
release:
|
|
name: gitea-unittests
|
|
namespace: testing
|
|
templates:
|
|
- templates/deployment.yaml
|
|
- templates/secret_admin.yaml
|
|
- templates/secret_config.yaml
|
|
- templates/secret_gpg.yaml
|
|
- templates/secret_init.yaml
|
|
- templates/secret_inlineConfig.yaml
|
|
- templates/secret_metrics.yaml
|
|
tests:
|
|
- it: "Render the Deployment with the default init containers"
|
|
asserts:
|
|
- hasDocuments:
|
|
count: 1
|
|
template: templates/deployment.yaml
|
|
- lengthEqual:
|
|
path: spec.template.spec.initContainers
|
|
count: 3
|
|
template: templates/deployment.yaml
|
|
|
|
- it: "Render the Deployment with the signing init container"
|
|
set:
|
|
secrets.gpg.enabled: true
|
|
secrets.gpg.existingSecret.enabled: true
|
|
secrets.gpg.existingSecret.secretName: "custom-gpg-secret"
|
|
asserts:
|
|
- hasDocuments:
|
|
count: 1
|
|
template: templates/deployment.yaml
|
|
- lengthEqual:
|
|
path: spec.template.spec.initContainers
|
|
count: 4
|
|
template: templates/deployment.yaml
|
|
|
|
- it: "Render the Deployment with extraInitContainers"
|
|
set:
|
|
deployment.initContainers:
|
|
- container:
|
|
name: bar
|
|
image: docker.io/library/busybox:latest
|
|
- link: "initDirectories"
|
|
- link: "initAppIni"
|
|
- link: "initConfigureGPG"
|
|
- link: "initConfigureGitea"
|
|
- container:
|
|
name: foo
|
|
image: docker.io/library/busybox:latest
|
|
secrets.gpg.enabled: true
|
|
secrets.gpg.existingSecret.enabled: true
|
|
secrets.gpg.existingSecret.secretName: "custom-gpg-secret"
|
|
asserts:
|
|
- hasDocuments:
|
|
count: 1
|
|
template: templates/deployment.yaml
|
|
- lengthEqual:
|
|
path: spec.template.spec.initContainers
|
|
count: 6
|
|
template: templates/deployment.yaml
|
|
- equal:
|
|
path: spec.template.spec.initContainers[0].name
|
|
value: bar
|
|
template: templates/deployment.yaml
|
|
- equal:
|
|
path: spec.template.spec.initContainers[5].name
|
|
value: foo
|
|
template: templates/deployment.yaml
|
|
|
|
- it: "Render the chart-managed init containers in the configured order"
|
|
template: templates/deployment.yaml
|
|
set:
|
|
deployment.initContainers:
|
|
- link: "initConfigureGitea"
|
|
- link: "initDirectories"
|
|
asserts:
|
|
- equal:
|
|
path: spec.template.spec.initContainers[0].name
|
|
value: configure-gitea
|
|
- equal:
|
|
path: spec.template.spec.initContainers[1].name
|
|
value: init-directories
|
|
|
|
- it: "Fail when an init container entry sets both container and link"
|
|
template: templates/deployment.yaml
|
|
set:
|
|
deployment.initContainers:
|
|
- link: "initDirectories"
|
|
container:
|
|
name: foo
|
|
image: docker.io/library/busybox:latest
|
|
asserts:
|
|
- failedTemplate:
|
|
errorMessage: "deployment.initContainers[0]: `container` and `link` are mutually exclusive"
|
|
|
|
- it: "Fail when an init container entry sets neither container nor link"
|
|
template: templates/deployment.yaml
|
|
set:
|
|
deployment.initContainers:
|
|
- name: foo
|
|
asserts:
|
|
- failedTemplate:
|
|
errorMessage: "deployment.initContainers[0]: either `container` or `link` must be set"
|
|
|
|
- it: "Fail when an init container links to an unknown configuration"
|
|
template: templates/deployment.yaml
|
|
set:
|
|
deployment.initContainers:
|
|
- link: "initSomething"
|
|
asserts:
|
|
- failedTemplate:
|
|
errorMessage: "deployment.initContainers[0]: unknown link `initSomething`, expected one of: initAppIni, initConfigureGPG, initConfigureGitea, initDirectories"
|