There is no SOAP/xml-rpc Request plugin after the jmeter3.2 version , so there is no way to test the WebService interface directly.
In principle:
Web service soap protocol through http wsdl document, customers can read the wsdl document to use this web service
The simple understanding of soap is that this is an open protocol soap=rpc+http+xml: Using HTTP as the underlying communication protocol;RPC as a consistent invocation path, XML acts as a data-transfer format that allows service providers and service clients to communicate over the INTERNET through firewalls .
so we can actually test the webservice by some means, throughthe HTTP request in JMeter.
Of course, the Manual on the official website also shows that it is possible. You only need to use the HTTP header manager two parameters Content-type and soapaction.
First, you need to New project in Soapui fills in the WebService interface address. and fill in the parameters in the interface, click Send.
Ensure that the parameters are sent successfully, as specified.
This step is to get some information that JMeter does not have.
1. Test plan-Right click Add-->threads--> new Thread Group
2. Thread Group--Right click Configuration Component--Add HTTP header Manager
3. Thread Group--click Add-->sampler-->http Request
4, the HTTP information Header manager needs to fill in Content-type(required) or soapaction, and soapaction is not required information.
These two data are to be obtained from the SoapUI . this soapaction information is not required when the Blue dash displays information that does not begin with "http ://" .
in the HTTP header manager, we need to fill in the Content-type information
5, in the HTTP request in the XML data information, all copied to the JMeter HTTP request body data.
6. Then send the request, success (*^▽^*)
information: From JMeter official website
Https://www.cnblogs.com/stone9159/p/8078842.html
Https://www.cnblogs.com/leijiangtao/p/5137351.html
jmeter3.2 version how to perform WebService interface functional testing