Replies: 2 comments 1 reply
-
|
Maybe there's a way we could run a scheduled conformance pipeline (once a week maybe) that tests the main branch. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
turns out we already have it #668 |
Beta Was this translation helpful? Give feedback.
-
|
closing this. #668 was to include |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Because we run Gateway API conformance tests from the last release of Gateway API (or whatever version our project is using), there is a risk that conformance tests for the next Gateway API release will start failing for our implementation, without us knowing about until the next Gateway API version is released and we start using it in NKG.
To catch conformance-related problems earlier, let’s find a way to run conformance tests from the main branch of Gateway API?
Additionally, it makes sense to be able to run conformance tests from any PR that add/changes existing conformance tests to the Gateway API project. This will allow us to review such PRs and give feedback when the changes start breaking our implementation (assuming the change is actually not compliant with Gateway API, rather than our implementation being not compliant).
Beta Was this translation helpful? Give feedback.
All reactions