-
Notifications
You must be signed in to change notification settings - Fork 7
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
Split e2e tests from samples #186
Conversation
@@ -545,7 +545,7 @@ void restartOrchestrationThrowsException() { | |||
|
|||
} | |||
|
|||
@Test | |||
// @Test |
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 test is pretty flaky, commented it out for now, will investigate this one and create PR accordingly. It may be an issue with the sidecar.
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.
If I understand this change correctly, it looks like we're no longer running the samples in the CI but just the new E2E tests. Can we do both? Having automation that tests the samples, even minimally, is useful to help ensure we don't accidentally break the samples. Maybe we could have two separate GitHub workflows, one that tests the samples (like we had before) and one that does more general E2E testing?
Yes, I can add back the tests for samples. |
Add back tests for samples! @cgillum |
Issue describing the changes in this PR
This PR split e2e test suit from function samples, adding flexibility to create end-to-end tests.
Pull request checklist
CHANGELOG.md
Additional information
Additional PR information