-
Notifications
You must be signed in to change notification settings - Fork 26
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
Add e2e tests for ConfigMap feature #558
Conversation
Signed-off-by: Katyanna Moura <[email protected]>
3db9342
to
46d5293
Compare
942949b
to
ea6be21
Compare
0c033af
to
c59e59a
Compare
👍 |
@linki I was thinking it could make sense to have a test showing the behavior when it fails e.g. the configmap is not there. Basically traffic switching should not succeed if configmap is missing. You could be inspired by this test: stackset-controller/cmd/e2e/broken_stack_test.go Lines 13 to 53 in 4278725
|
}, | ||
}, | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This stuff makes sure that if you configure your Stackset to have a versioned ConfigMap (via the factory and calling ConfigMap()
) that it will end up with a working configuration (name pattern matches, external ConfigMap exists).
👍 |
1 similar comment
👍 |
Debug e2e not failing for ConfigMap feature