volker.raschekandCopilot
bb3b59f1ee
The contributor guidelines require that the title of a unit test is "a short sentence starting with a capital
letter and ending without a period". Only 30 of the 269 titles followed that rule. The remaining ones were
lowercase verb phrases ("renders a deployment"), which made the test output read inconsistently depending on
which suite was running, and made it impossible to tell a convention violation from an intentional style.
All titles are now imperative, capitalized and unquoted-safe:
renders a deployment -> Render a Deployment
should not render when gatewayAPI.enabled is false -> Skip rendering when gatewayAPI.enabled is false
skips gpg volume spec -> Skip the gpg volume spec
The bracketed prefixes of the dependency checks and of the server section suite are kept, because they group
the tests by the chart they assert on. Only the sentence behind the prefix was rewritten.
Beyond the pure capitalization three classes of titles needed real rewording:
- The titles in image-configuration.yaml named a subject instead of a scenario ("default values", "tag
override", "digest and global registry"). They now describe what is rendered.
- init_directory_structure.sh-rootless.yaml carried "it does not chown /data ...", which rendered as
"it it does not chown" in the test output.
- The "should" prefix in the Gateway API and route suites added no information once the title is a sentence.
The title of the GIT_GC_REPOS test lost its embedded double quotes. The title was previously an unquoted YAML
scalar, so the quotes were literal characters; quoting the title turned them into a parse error. The value is
unambiguous without them.
Three byte-identical tests asserting pgpool.adminPassword existed in customization-integrity-postgresql-ha.yaml
- same template, same assertion, same expected value. They were a copy-paste artifact and shared one title, so
two of them are removed. No coverage is lost, which is why the test count drops from 269 to 267.
No snapshot files are tracked and no suite uses matchSnapshot, so retitling cannot invalidate stored snapshots.
Co-authored-by: Copilot <copilot@github.com>
131 lines
4.2 KiB
YAML
131 lines
4.2 KiB
YAML
suite: deployment template (signing enabled)
|
|
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: "Add the gpg init container"
|
|
template: templates/deployment.yaml
|
|
set:
|
|
secrets.gpg.enabled: true
|
|
secrets.gpg.existingSecret.enabled: true
|
|
secrets.gpg.existingSecret.secretName: "custom-gpg-secret"
|
|
asserts:
|
|
- equal:
|
|
path: spec.template.spec.initContainers[2].name
|
|
value: configure-gpg
|
|
- equal:
|
|
path: spec.template.spec.initContainers[2].command
|
|
value: ["/usr/sbinx/configure_gpg_environment.sh"]
|
|
- equal:
|
|
path: spec.template.spec.initContainers[2].securityContext
|
|
value:
|
|
runAsUser: 1000
|
|
- equal:
|
|
path: spec.template.spec.initContainers[2].env
|
|
value:
|
|
- name: GNUPGHOME
|
|
valueFrom:
|
|
secretKeyRef:
|
|
name: custom-gpg-secret
|
|
key: gpgHome
|
|
- name: TMP_RAW_GPG_KEY
|
|
value: /raw/private.asc
|
|
- equal:
|
|
path: spec.template.spec.initContainers[2].volumeMounts
|
|
value:
|
|
- name: init
|
|
mountPath: /usr/sbinx
|
|
- name: data
|
|
mountPath: /data
|
|
- name: gpg-private-key
|
|
mountPath: /raw
|
|
readOnly: true
|
|
- it: "Add the gpg env to the `init-directories` init container"
|
|
template: templates/deployment.yaml
|
|
set:
|
|
secrets.gpg.enabled: true
|
|
secrets.gpg.existingSecret.enabled: true
|
|
secrets.gpg.existingSecret.secretName: "custom-gpg-secret"
|
|
asserts:
|
|
- contains:
|
|
path: spec.template.spec.initContainers[0].env
|
|
content:
|
|
name: GNUPGHOME
|
|
valueFrom:
|
|
secretKeyRef:
|
|
name: custom-gpg-secret
|
|
key: gpgHome
|
|
- it: "Add the gpg env to the runtime container"
|
|
template: templates/deployment.yaml
|
|
set:
|
|
secrets.gpg.enabled: true
|
|
secrets.gpg.existingSecret.enabled: true
|
|
secrets.gpg.existingSecret.secretName: "custom-gpg-secret"
|
|
asserts:
|
|
- contains:
|
|
path: spec.template.spec.containers[0].env
|
|
content:
|
|
name: GNUPGHOME
|
|
valueFrom:
|
|
secretKeyRef:
|
|
name: custom-gpg-secret
|
|
key: gpgHome
|
|
- it: "Read the gpg home from the configured key of an existing Secret"
|
|
template: templates/deployment.yaml
|
|
set:
|
|
secrets.gpg.enabled: true
|
|
secrets.gpg.existingSecret.enabled: true
|
|
secrets.gpg.existingSecret.secretName: "custom-gpg-secret"
|
|
secrets.gpg.existingSecret.gpgHomeKey: custom-gpg-home
|
|
asserts:
|
|
- contains:
|
|
path: spec.template.spec.containers[0].env
|
|
content:
|
|
name: GNUPGHOME
|
|
valueFrom:
|
|
secretKeyRef:
|
|
name: custom-gpg-secret
|
|
key: custom-gpg-home
|
|
- it: "Add the gpg volume spec"
|
|
template: templates/deployment.yaml
|
|
set:
|
|
secrets.gpg.enabled: true
|
|
secrets.gpg.new.privateKey: "gpg-key-placeholder"
|
|
asserts:
|
|
- contains:
|
|
path: spec.template.spec.volumes
|
|
content:
|
|
name: gpg-private-key
|
|
secret:
|
|
secretName: gitea-unittests-gpg-key
|
|
items:
|
|
- key: privateKey
|
|
path: private.asc
|
|
defaultMode: 0100
|
|
- it: "Render the gpg volume spec with an external reference"
|
|
template: templates/deployment.yaml
|
|
set:
|
|
secrets.gpg.enabled: true
|
|
secrets.gpg.existingSecret.enabled: true
|
|
secrets.gpg.existingSecret.secretName: custom-gpg-secret
|
|
secrets.gpg.existingSecret.privateKeyKey: custom-private-key
|
|
asserts:
|
|
- contains:
|
|
path: spec.template.spec.volumes
|
|
content:
|
|
name: gpg-private-key
|
|
secret:
|
|
secretName: custom-gpg-secret
|
|
items:
|
|
- key: custom-private-key
|
|
path: private.asc
|
|
defaultMode: 0100
|