Asssertion fails due "wrong" response
Hi, i have issue with some of my assertions, for some requests there seems to be wrong response and thus assertion is failing..
I doing REST-API testing for service we are developping
see example belov:
Request:${#Project#ServiceEndpoint}/rest-api/products/${#Project#product_id}/events
raw request:
GET https://it.test_env.com/rest-api/products/1/events HTTP/1.1
...
in response there is for some reason different product id...
<Response xmlns="https://it.vs-mp.nokia.com/rest-api/products/4/events">
<events>
<e>
<attributes/>
<origin>test_user</origin>
<productid>1</productid>
...
now if im using properties with xPath assertions those cases are failing because product id does not match.
whats happening there?, from where that xmlns response is coming, it seems to be occasional because if i create test from scratch again it will work fine..?
I doing REST-API testing for service we are developping
see example belov:
Request:${#Project#ServiceEndpoint}/rest-api/products/${#Project#product_id}/events
raw request:
GET https://it.test_env.com/rest-api/products/1/events HTTP/1.1
...
in response there is for some reason different product id...
<Response xmlns="https://it.vs-mp.nokia.com/rest-api/products/4/events">
<events>
<e>
<attributes/>
<origin>test_user</origin>
<productid>1</productid>
...
now if im using properties with xPath assertions those cases are failing because product id does not match.
whats happening there?, from where that xmlns response is coming, it seems to be occasional because if i create test from scratch again it will work fine..?
