Forum Discussion
sbeauvais
11 years agoContributor
I have found a way to work around the problem.
The problem is that SoapUI gets confused if there are several methods with the same name under a REST service. (I had left the default names created by SoapUI.)
The confusion is that teststeps (in a testsuite) may use the wrong method for a resource. This is seen when a teststep is configured with a REST test request specifying a PUT method, but after saving and reloading the project, the test request may use the GET method.
The work-around is to name all methods differently. (It may be necessary to add in the testsuite test requests anew, so that they refer back to the renamed methods.)
SB
The problem is that SoapUI gets confused if there are several methods with the same name under a REST service. (I had left the default names created by SoapUI.)
The confusion is that teststeps (in a testsuite) may use the wrong method for a resource. This is seen when a teststep is configured with a REST test request specifying a PUT method, but after saving and reloading the project, the test request may use the GET method.
The work-around is to name all methods differently. (It may be necessary to add in the testsuite test requests anew, so that they refer back to the renamed methods.)
SB
- wjblazek9 years agoOccasional Contributor
I had this same problem with POST methods not being saved.
Prepending GET, POST, PUT, DEL to the actual name of each method for the resource fixed it.
This also makes it easier to find and choose the right resource method when creating a new test step.
Thanks.
Related Content
- 7 years ago
- 10 years ago
Recent Discussions
- 4 days ago