-
Notifications
You must be signed in to change notification settings - Fork 171
[WIP] Add E2E tests for secrets management #3485
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
base: main
Are you sure you want to change the base?
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3485 +/- ##
==========================================
+ Coverage 65.15% 65.24% +0.08%
==========================================
Files 398 399 +1
Lines 38821 38908 +87
==========================================
+ Hits 25295 25385 +90
+ Misses 11564 11557 -7
- Partials 1962 1966 +4 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
fb44083 to
a910ab4
Compare
a910ab4 to
4da9af4
Compare
eleftherias
left a comment
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.
The 404 tests are failing with a 405. Also added one question inline.
| defer resp.Body.Close() | ||
|
|
||
| By("Verifying response status is 400 or 405") | ||
| Expect(resp.StatusCode).To(SatisfyAny( |
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.
Is it possible that it'll return 2 different status codes today, or is this for future-proofing?
Due to dependency issues (keychain for encrypted, or 1password), these tests only test the environment type. This does not cover all secrets management functionality, but verifies basic correctness of the secrets endpoints.