-
Notifications
You must be signed in to change notification settings - Fork 536
Add mesh conformance tests for httproute port and scheme redirect #3776
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
base: main
Are you sure you want to change the base?
Add mesh conformance tests for httproute port and scheme redirect #3776
Conversation
2c64c87
to
a88271b
Compare
/retest |
/cc @kflynn |
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.
Thanks @LiorLieberman!
MeshConformanceTests = append(MeshConformanceTests, MeshHTTPRouteRedirectPort) | ||
} | ||
|
||
var MeshHTTPRouteRedirectPort = suite.ConformanceTest{ |
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.
I think I missed this from the earlier conversations, but what's the plan to make these tests more sustainable + maintainable? Would it be viable to just have a simple script that did the copying and modification required for any tests that should be replicated for mesh? Is there a way to share the same test definitions for both?
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: LiorLieberman, robscott The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/area conformance-test
Add mesh tests for port and scheme redirect
This is a follow up to #3729
What this PR does / why we need it:
Add mesh tests coverage
Which issue(s) this PR fixes:
Related #3581
Does this PR introduce a user-facing change?: