e2e: remove redundant spaces in test names

The spaces are redundant because Ginkgo will add them itself when concatenating
the different test name components. Upcoming change in the framework will
enforce that there are no such redundant spaces.
This commit is contained in:
Patrick Ohly 2023-09-28 14:41:20 +02:00
parent fe6d64d080
commit 0e8a1f1816
23 changed files with 101 additions and 93 deletions

View File

@ -203,7 +203,8 @@
file: test/e2e/apimachinery/custom_resource_definition.go file: test/e2e/apimachinery/custom_resource_definition.go
- testname: Custom Resource Definition, list - testname: Custom Resource Definition, list
codename: '[sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin] codename: '[sig-api-machinery] CustomResourceDefinition resources [Privileged:ClusterAdmin]
Simple CustomResourceDefinition listing custom resource definition objects works [Conformance]' Simple CustomResourceDefinition listing custom resource definition objects works
[Conformance]'
description: Create a API extension client, define 10 labeled custom resource definitions description: Create a API extension client, define 10 labeled custom resource definitions
and list them using a label selector; the list result MUST contain only the labeled and list them using a label selector; the list result MUST contain only the labeled
custom resource definitions. Delete the labeled custom resource definitions via custom resource definitions. Delete the labeled custom resource definitions via
@ -1150,7 +1151,8 @@
release: v1.21 release: v1.21
file: test/e2e/auth/service_accounts.go file: test/e2e/auth/service_accounts.go
- testname: Service account tokens auto mount optionally - testname: Service account tokens auto mount optionally
codename: '[sig-auth] ServiceAccounts should allow opting out of API token automount [Conformance]' codename: '[sig-auth] ServiceAccounts should allow opting out of API token automount
[Conformance]'
description: Ensure that Service Account keys are mounted into the Pod only when description: Ensure that Service Account keys are mounted into the Pod only when
AutoMountServiceToken is not set to false. We test the following scenarios here. AutoMountServiceToken is not set to false. We test the following scenarios here.
1. Create Pod, Pod Spec has AutomountServiceAccountToken set to nil a) Service 1. Create Pod, Pod Spec has AutomountServiceAccountToken set to nil a) Service
@ -1262,7 +1264,8 @@
release: v1.19 release: v1.19
file: test/e2e/kubectl/kubectl.go file: test/e2e/kubectl/kubectl.go
- testname: Kubectl, create service, replication controller - testname: Kubectl, create service, replication controller
codename: '[sig-cli] Kubectl client Kubectl expose should create services for rc [Conformance]' codename: '[sig-cli] Kubectl client Kubectl expose should create services for rc
[Conformance]'
description: Create a Pod running agnhost listening to port 6379. Using kubectl description: Create a Pod running agnhost listening to port 6379. Using kubectl
expose the agnhost primary replication controllers at port 1234. Validate that expose the agnhost primary replication controllers at port 1234. Validate that
the replication controller is listening on port 1234 and the target port is set the replication controller is listening on port 1234 and the target port is set
@ -1272,7 +1275,8 @@
release: v1.9 release: v1.9
file: test/e2e/kubectl/kubectl.go file: test/e2e/kubectl/kubectl.go
- testname: Kubectl, label update - testname: Kubectl, label update
codename: '[sig-cli] Kubectl client Kubectl label should update the label on a resource [Conformance]' codename: '[sig-cli] Kubectl client Kubectl label should update the label on a resource
[Conformance]'
description: When a Pod is running, update a Label using 'kubectl label' command. description: When a Pod is running, update a Label using 'kubectl label' command.
The label MUST be created in the Pod. A 'kubectl get pod' with -l option on the The label MUST be created in the Pod. A 'kubectl get pod' with -l option on the
container MUST verify that the label can be read back. Use 'kubectl label label-' container MUST verify that the label can be read back. Use 'kubectl label label-'
@ -1323,7 +1327,8 @@
release: v1.9 release: v1.9
file: test/e2e/kubectl/kubectl.go file: test/e2e/kubectl/kubectl.go
- testname: Kubectl, proxy socket - testname: Kubectl, proxy socket
codename: '[sig-cli] Kubectl client Proxy server should support --unix-socket=/path [Conformance]' codename: '[sig-cli] Kubectl client Proxy server should support --unix-socket=/path
[Conformance]'
description: Start a proxy server on by running 'kubectl proxy' with --unix-socket=<some description: Start a proxy server on by running 'kubectl proxy' with --unix-socket=<some
path>. Call the proxy server by requesting api versions from http://locahost:0/api. path>. Call the proxy server by requesting api versions from http://locahost:0/api.
The proxy server MUST provide at least one version string The proxy server MUST provide at least one version string
@ -1346,7 +1351,8 @@
release: v1.9 release: v1.9
file: test/e2e/kubectl/kubectl.go file: test/e2e/kubectl/kubectl.go
- testname: Kubectl, scale replication controller - testname: Kubectl, scale replication controller
codename: '[sig-cli] Kubectl client Update Demo should scale a replication controller [Conformance]' codename: '[sig-cli] Kubectl client Update Demo should scale a replication controller
[Conformance]'
description: Create a Pod and a container with a given image. Configure replication description: Create a Pod and a container with a given image. Configure replication
controller to run 2 replicas. The number of running instances of the Pod MUST controller to run 2 replicas. The number of running instances of the Pod MUST
equal the number of replicas set on the replication controller which is 2. Update equal the number of replicas set on the replication controller which is 2. Update
@ -1355,7 +1361,8 @@
release: v1.9 release: v1.9
file: test/e2e/kubectl/kubectl.go file: test/e2e/kubectl/kubectl.go
- testname: Kubectl, logs - testname: Kubectl, logs
codename: '[sig-cli] Kubectl logs logs should be able to retrieve and filter logs [Conformance]' codename: '[sig-cli] Kubectl logs logs should be able to retrieve and filter logs
[Conformance]'
description: When a Pod is running then it MUST generate logs. Starting a Pod should description: When a Pod is running then it MUST generate logs. Starting a Pod should
have a expected log line. Also log command options MUST work as expected and described have a expected log line. Also log command options MUST work as expected and described
below. 'kubectl logs -tail=1' should generate a output of one line, the last line below. 'kubectl logs -tail=1' should generate a output of one line, the last line
@ -1529,8 +1536,8 @@
release: v1.19 release: v1.19
file: test/e2e/network/ingress.go file: test/e2e/network/ingress.go
- testname: IngressClass API - testname: IngressClass API
codename: '[sig-network] IngressClass API should support creating IngressClass codename: '[sig-network] IngressClass API should support creating IngressClass API
API operations [Conformance]' operations [Conformance]'
description: ' - The networking.k8s.io API group MUST exist in the /apis discovery description: ' - The networking.k8s.io API group MUST exist in the /apis discovery
document. - The networking.k8s.io/v1 API group/version MUST exist in the /apis/networking.k8s.io document. - The networking.k8s.io/v1 API group/version MUST exist in the /apis/networking.k8s.io
discovery document. - The ingressclasses resource MUST exist in the /apis/networking.k8s.io/v1 discovery document. - The ingressclasses resource MUST exist in the /apis/networking.k8s.io/v1
@ -1607,7 +1614,8 @@
release: v1.21 release: v1.21
file: test/e2e/network/proxy.go file: test/e2e/network/proxy.go
- testname: Proxy, logs service endpoint - testname: Proxy, logs service endpoint
codename: '[sig-network] Proxy version v1 should proxy through a service and a pod [Conformance]' codename: '[sig-network] Proxy version v1 should proxy through a service and a pod
[Conformance]'
description: Select any node in the cluster to invoke /logs endpoint using the description: Select any node in the cluster to invoke /logs endpoint using the
/nodes/proxy subresource from the kubelet port. This endpoint MUST be reachable. /nodes/proxy subresource from the kubelet port. This endpoint MUST be reachable.
release: v1.9 release: v1.9
@ -2322,16 +2330,6 @@
count MUST be zero. count MUST be zero.
release: v1.9 release: v1.9
file: test/e2e/common/node/container_probe.go file: test/e2e/common/node/container_probe.go
- testname: RuntimeClass API
codename: '[sig-node] RuntimeClass should support RuntimeClasses API operations
[Conformance]'
description: ' The node.k8s.io API group MUST exist in the /apis discovery document.
The node.k8s.io/v1 API group/version MUST exist in the /apis/mode.k8s.io discovery
document. The runtimeclasses resource MUST exist in the /apis/node.k8s.io/v1 discovery
document. The runtimeclasses resource must support create, get, list, watch, update,
patch, delete, and deletecollection.'
release: v1.20
file: test/e2e/common/node/runtimeclass.go
- testname: Pod with the deleted RuntimeClass is rejected. - testname: Pod with the deleted RuntimeClass is rejected.
codename: '[sig-node] RuntimeClass should reject a Pod requesting a deleted RuntimeClass codename: '[sig-node] RuntimeClass should reject a Pod requesting a deleted RuntimeClass
[NodeConformance] [Conformance]' [NodeConformance] [Conformance]'
@ -2362,6 +2360,16 @@
is not being tested here. is not being tested here.
release: v1.20 release: v1.20
file: test/e2e/common/node/runtimeclass.go file: test/e2e/common/node/runtimeclass.go
- testname: RuntimeClass API
codename: '[sig-node] RuntimeClass should support RuntimeClasses API operations
[Conformance]'
description: ' The node.k8s.io API group MUST exist in the /apis discovery document.
The node.k8s.io/v1 API group/version MUST exist in the /apis/mode.k8s.io discovery
document. The runtimeclasses resource MUST exist in the /apis/node.k8s.io/v1 discovery
document. The runtimeclasses resource must support create, get, list, watch, update,
patch, delete, and deletecollection.'
release: v1.20
file: test/e2e/common/node/runtimeclass.go
- testname: Secrets, pod environment field - testname: Secrets, pod environment field
codename: '[sig-node] Secrets should be consumable from pods in env vars [NodeConformance] codename: '[sig-node] Secrets should be consumable from pods in env vars [NodeConformance]
[Conformance]' [Conformance]'