-
Notifications
You must be signed in to change notification settings - Fork 30
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
Can't use a runtime variable as part of request path #41
Comments
Yes, with the annotation approach you can not make calls that are regards On Mon, Mar 25, 2013 at 12:45 PM, Allblues [email protected] wrote:
|
+1 Without some sort of runtime generation paths, it's actually impossible to test creation and deletion of the same resource (that is common when doing integration tests). |
+1 |
You should try Rest Assured. Been using if for quite some time now and love it. |
@vrspider 11 months after we are using a simple REST client built on top of Apache HTTPClient (https://github.com/ClouDesire/tisana4j) for our integration tests. |
I love how easy it is to use restfuse, but with the annotation-based approach, I don't see a way to use a variable I set at runtime as a segment in a rest request. For example, I want to perform this workflow:
@httptest( method = Method.GET, path = "/entity/Candidate/{id}" )
The {id} segment would resolve to the variable I set at runtime, but it can't since the annotation gets read at compile time.
This is easy to do in SoapUI, but I'm looking at lighter weight tools like restfuse.
The text was updated successfully, but these errors were encountered: