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

Ensure azure tests perform failure check on CRDs #140

Closed
cab105 opened this issue Jan 3, 2022 · 0 comments · Fixed by #142
Closed

Ensure azure tests perform failure check on CRDs #140

cab105 opened this issue Jan 3, 2022 · 0 comments · Fixed by #142
Assignees
Labels
e2e Issues related to End-to-End testing

Comments

@cab105
Copy link
Contributor

cab105 commented Jan 3, 2022

Based on a comment to #135:

I'm expecting some tests to assert that Kubernetes rejects objects with invalid specs (see AWS sources for examples).
These tests don't require any resource group, the failure is expected to happen long before we even interact with Azure, so this step should be nested one level deeper ("a blob is created ...").

Originally posted by @antoineco in #135 (comment)

Address this across all Azure sources.

@cab105 cab105 self-assigned this Jan 3, 2022
@cab105 cab105 added the e2e Issues related to End-to-End testing label Jan 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
e2e Issues related to End-to-End testing
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant