-
Notifications
You must be signed in to change notification settings - Fork 263
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 CronJob source #566
Comments
I'd like to try. |
/reopen (for verifying the events at the sink) |
@navidshaikh: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@navidshaikh will you provide more details for "verifying the events at the sink" ? |
@daisy-ycguo : We can use |
I will take care of the item: |
/assign daisy-ycguo |
@rhuss @navidshaikh The reason that I question this requirement is that I'm not able to implement this test case based on the GKE with Istio add-on testing environment. Eventing has the pingsource e2e test case working well with So I recommend to change the test case to |
Sounds reasonable, but I really wonder how eventing the e2e tests pingsource if it doesn't work with the setup given ? |
* updating plank to v20190311 * add comment
similar to for E2E tests for ApiServer source. Ideally this should involve also a service to connect to and checking whether cronjob events have been delivered.
The text was updated successfully, but these errors were encountered: