-
Notifications
You must be signed in to change notification settings - Fork 43
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 module for end 2 end tests for verify the the generated client co… #252
Add module for end 2 end tests for verify the the generated client co… #252
Conversation
@cjbooms I would propose to add acceptance/end2end tests like this. |
Yep, fine with me. Nice that it's a separate module |
ec8a20a
to
c601935
Compare
examplePath2Client.getExamplePath2PathParam("304", 10) | ||
} | ||
|
||
assertThat(result.message).isEqualTo("[304]: ") |
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.
@cjbooms This looks dodgy. There seems to be no handling for the 3xx cases.
Messages are either successful -> 200..299
, bad request -> 400..499
or server error -> 500..599
.
Everything 3xx
falls through into the else case in http-util.kt.hbs
line 46.
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 don't think anyone at Zalando have used the API client for anything other than tests, so probably proper 3X handling never came up.
ba48788
to
cb57996
Compare
…mplies with the spec and is run able
cb57996
to
910d361
Compare
First part of the coverage done |
👍 |
…mplies with the spec and is run able