-
Notifications
You must be signed in to change notification settings - Fork 602
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
Conformance testing for Channel URL #1958
Comments
Testable enough by checking status.address is URL and modify URL with random changes to verify 404? |
/project Channels To do |
/close We're good in terms of this test. Closing this ticket as: |
@aliok: Closing 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. |
Problem
From channel specification extracted testable
“The HTTP event queueing request's URL MUST correspond to a single, unique
Channel at any given moment in time. This MAY be done via the host, path, query
string, or any combination of these. This mapping is handled exclusively by the
Channel implementation, exposed via the Channel's
status.address
. If an HTTPevent queueing request's URL does not correspond to an existing Channel, then
the Channel MUST respond with
404 Not Found
.Persona:
Which persona is this feature for?
System Integrator, Contributors
Exit Criteria
A measurable (binary) test that would indicate that the problem has been resolved.
Test runs without errors for in-memory channel
Time Estimate (optional):
How many developer-days do you think this may take to resolve?
1h?
Additional context (optional)
Add any other context about the feature request here.
The text was updated successfully, but these errors were encountered: