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

Add E2E tests for CronJob source #566

Closed
1 of 2 tasks
rhuss opened this issue Dec 17, 2019 · 9 comments · Fixed by #727
Closed
1 of 2 tasks

Add E2E tests for CronJob source #566

rhuss opened this issue Dec 17, 2019 · 9 comments · Fixed by #727
Assignees
Labels
kind/feature New feature or request

Comments

@rhuss
Copy link
Contributor

rhuss commented Dec 17, 2019

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.

  • Add CronJob create/update/delete tests
  • Verify the events at configured sink
@rhuss rhuss added kind/feature New feature or request topic/eventing-mvp labels Dec 17, 2019
@MIBc
Copy link
Contributor

MIBc commented Jan 6, 2020

I'd like to try.

MIBc added a commit to MIBc/client that referenced this issue Jan 7, 2020
@navidshaikh
Copy link
Collaborator

/reopen

(for verifying the events at the sink)

@knative-prow-robot
Copy link
Contributor

@navidshaikh: Reopened this issue.

In response to this:

/reopen

(for verifying the events at the sink)

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.

@rhuss rhuss added the good first issue Denotes an issue ready for a new contributor. label Feb 5, 2020
@daisy-ycguo
Copy link
Member

/reopen

(for verifying the events at the sink)

@navidshaikh will you provide more details for "verifying the events at the sink" ?

@navidshaikh
Copy link
Collaborator

@daisy-ycguo : We can use gcr.io/knative-releases/github.com/knative/eventing-contrib/cmd/event_display to receive events and verify events from logs.

@daisy-ycguo
Copy link
Member

I will take care of the item: Verify the events at configured sink.

@daisy-ycguo
Copy link
Member

/assign daisy-ycguo

@daisy-ycguo
Copy link
Member

@rhuss @navidshaikh
I don't think we should work on this test case Verify the events at configured sink. It should be a part of e2e test of eventing. We could verify that pingsource could be described correctly. Because if pingsource could be described correctly, and eventing functions work well, it's definitely true that event message could be sent to sink.

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 --skip-istio-addon enabled in their test environment. While if we disable istio add-on, some serving test cases might be failed according to @chizhg 's comment.

So I recommend to change the test case to verify pingsource description.

@rhuss
Copy link
Contributor Author

rhuss commented Mar 10, 2020

Sounds reasonable, but I really wonder how eventing the e2e tests pingsource if it doesn't work with the setup given ?

@rhuss rhuss removed the good first issue Denotes an issue ready for a new contributor. label Mar 10, 2020
coryrc pushed a commit to coryrc/client that referenced this issue May 14, 2020
* updating plank to v20190311

* add comment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment