-
Notifications
You must be signed in to change notification settings - Fork 738
Support REST Assured 4 #635
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
Comments
For reference, while we are probably not using all REST-Assured features or APIs, we are already using REST Assured 4.0.0 and Spring Restdocs 2.0.3.RELEASE together without any visible issues. |
Thank you, @bric3. That's useful info. This may turn into a just adding some compatibility testing. It may also make sense to do some repackaging as the current REST Assured support is in a |
Ah yes I forgot to say that indeed we are using the API that lives under |
I've added some compatibility testing against both 4.0.0 and 4.1.1 (#640). I'll keep this issue open to deal with the
The first option is cleaner, but backs us into a corner if there's a REST Assured 5 with breaking changes in the future. The second avoids that problem but at the cost of some duplication. I think I'm leaning towards the first option at the moment. |
Isn't there already a |
There is in 1.2 where it's deprecated. It was removed in 2.0. |
On SpringBoot 2.3.1 I updated rest assured to 4.3.1 and groovy to 3.0.4 and things seem to be working just fine. I don't have a lot of tests yet that are using RestDocs just a few as I have just started using RestDocs on this project. |
This has been superseded by #752 where the package will be renamed from |
No description provided.
The text was updated successfully, but these errors were encountered: