Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Promote: ConfigMap Lifecycle test - +2 conformance endpoint coverage #90941

Merged
merged 8 commits into from Jul 15, 2020
Merged

Promote: ConfigMap Lifecycle test - +2 conformance endpoint coverage #90941

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
0b6994e
Promote: ConfigMap Lifecycle test
BobyMCbobs Feb 11, 2020
0ea650b
Fix: conformance data, conformance test entrypoint
BobyMCbobs Feb 11, 2020
f6cd389
Fix: formatting
BobyMCbobs Feb 19, 2020
b4ee99c
Fix formatting
BobyMCbobs Feb 25, 2020
b20856e
Add conformance testdata
BobyMCbobs Feb 27, 2020
d9ca849
Update conformance metadata to have release version v1.19
BobyMCbobs Mar 24, 2020
82c99d8
Fix metadata release version
BobyMCbobs Mar 26, 2020
9520a87
Fix metadata formatting
heyste Jul 9, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
8 changes: 8 additions & 0 deletions test/conformance/testdata/conformance.yaml
View file
Open in desktop
Expand Up @@ -1851,6 +1851,14 @@
fail.
release: v1.14
file: test/e2e/common/configmap.go
- testname: ConfigMap lifecycle
codename: '[sig-node] ConfigMap should run through a ConfigMap lifecycle [Conformance]'
description: Attempt to create a ConfigMap. Patch the created ConfigMap. Fetching
the ConfigMap MUST reflect changes. By fetching all the ConfigMaps via a Label
selector it MUST find the ConfigMap by it's static label and updated value. The
ConfigMap must be deleted by Collection.
release: v1.19
file: test/e2e/common/configmap.go
- testname: DownwardAPI, environment for CPU and memory limits and requests
codename: '[sig-node] Downward API should provide container''s limits.cpu/memory
and requests.cpu/memory as env vars [NodeConformance] [Conformance]'
Expand Down
8 changes: 7 additions & 1 deletion test/e2e/common/configmap.go
View file
Open in desktop
Expand Up @@ -168,7 +168,13 @@ var _ = ginkgo.Describe("[sig-node] ConfigMap", func() {
framework.ExpectEqual(configMapFromUpdate.Data, configMap.Data)
})

ginkgo.It("should run through a ConfigMap lifecycle", func() {
/*
Release : v1.19
Testname: ConfigMap lifecycle
Description: Attempt to create a ConfigMap. Patch the created ConfigMap. Fetching the ConfigMap MUST reflect changes.
By fetching all the ConfigMaps via a Label selector it MUST find the ConfigMap by it's static label and updated value. The ConfigMap must be deleted by Collection.
*/
framework.ConformanceIt("should run through a ConfigMap lifecycle", func() {
testNamespaceName := f.Namespace.Name
testConfigMapName := "test-configmap" + string(uuid.NewUUID())

Expand Down