ltarjanyi
6 years agoNew Contributor
SoapUI v. 5.5.0: Load Test runs HTTP DELETE instead of PATCH
Hi,
I have a TestCase with multiple steps including (among others) an REST HTTP DELETE and than a PATCH command.
It runs fine when I run the TestCase standalone:
...
Wed May 22 21:58:53 CEST 2019:DEBUG:Sending request: DELETE /api/v1/shopping-carts/0287038cc7744fe5950d5bb10707ebdd/items/20 HTTP/1.1 Wed May 22 21:58:53 CEST 2019:DEBUG:Receiving response: HTTP/1.1 200 OK Wed May 22 21:58:53 CEST 2019:DEBUG:Connection can be kept alive indefinitely Wed May 22 21:58:53 CEST 2019:DEBUG:Stale connection check Wed May 22 21:58:53 CEST 2019:DEBUG:Attempt 1 to execute request Wed May 22 21:58:53 CEST 2019:DEBUG:Sending request: PATCH /api/v1/shopping-carts/0287038cc7744fe5950d5bb10707ebdd/items/30 HTTP/1.1 Wed May 22 21:58:53 CEST 2019:DEBUG:Receiving response: HTTP/1.1 200 OK Wed May 22 21:58:53 CEST 2019:DEBUG:Connection can be kept alive indefinitely Wed May 22 21:58:53 CEST 2019:INFO:Got response for [http://tvushpcart01.pgsm.hu:7150.DeleteItem:Update] in 109ms (1667 bytes) Wed May 22 21:58:53 CEST 2019:DEBUG:Stale connection check
...
When I run the same in Load Test, it runs HTTP DELETE instead of PATCH also. What could be the problem?
...
Wed May 22 22:00:27 CEST 2019:DEBUG:Sending request: DELETE /api/v1/shopping-carts/b1c45f620aff4947951c305c94a54c56/items/20 HTTP/1.1 Wed May 22 22:00:27 CEST 2019:DEBUG:Receiving response: HTTP/1.1 200 OK Wed May 22 22:00:27 CEST 2019:DEBUG:Connection can be kept alive indefinitely Wed May 22 22:00:27 CEST 2019:DEBUG:Stale connection check Wed May 22 22:00:27 CEST 2019:DEBUG:Attempt 1 to execute request Wed May 22 22:00:27 CEST 2019:DEBUG:Sending request: DELETE /api/v1/shopping-carts/b1c45f620aff4947951c305c94a54c56/items/30 HTTP/1.1 Wed May 22 22:00:27 CEST 2019:DEBUG:Receiving response: HTTP/1.1 200 OK Wed May 22 22:00:27 CEST 2019:DEBUG:Connection can be kept alive indefinitely Wed May 22 22:00:27 CEST 2019:DEBUG:Stale connection check
...
Regards,
Laszlo
- Hi, I solved it by recreating the REST resource and request and adding it to the Test Case. Don't know why it was not working with the other test step, but this solved the problem. Regards, Lala