You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
having a lot of tests under the old format path 'foo/bar/baz', I tried to play with raw path, to try and check if my old test work without rewriting to path 'foo', 'bar', 'baz', which I personnally found a lot less clear (this is not the place to debate that though).
Using karate version : 1.1.0.RC2
And I found out that when I have 2 HTTP calls using path rawin the same scenario, the paths are getting concatenated, while I expected it to be replaced.
See example below :
Given url 'http://httpbin.org'
And raw path 'anything/dog'
When method GET
Then status 200
And match response.url == 'http://httpbin.org/anything/dog'
Given url 'http://httpbin.org'
And raw path 'anything/cat'
When method GET
Then status 200
And match response.url == 'http://httpbin.org/anything/cat' # TEST FAILS, actually it is http://httpbin.org/anything/dog/anything/cat
This might be a misunderstanding from me, as raw path is not yet documented, but I feel it shouldn't behave like that.
I made the same test using two different scenarios, and raw path works as I expect it.
The text was updated successfully, but these errors were encountered:
Hi,
having a lot of tests under the old format
path 'foo/bar/baz'
, I tried to play withraw path
, to try and check if my old test work without rewriting to path 'foo', 'bar', 'baz', which I personnally found a lot less clear (this is not the place to debate that though).Using karate version : 1.1.0.RC2
And I found out that when I have 2 HTTP calls using
path raw
in the same scenario, the paths are getting concatenated, while I expected it to be replaced.See example below :
This might be a misunderstanding from me, as
raw path
is not yet documented, but I feel it shouldn't behave like that.I made the same test using two different scenarios, and
raw path
works as I expect it.The text was updated successfully, but these errors were encountered: