Summary of Web Service testing tools-Transfer

I have been doing WebService tests recently. Considering the difficulties of manual tests, I am looking for a good testing tool. Now I am doing some work.

1.. Net WebService Studio

This tool is from within Microsoft. The biggest advantage is that it has good visualization. without looking at the XML files, the basic content of WebService has XML, but there are too many cases in the test, the XML file is used to view each test result, which seriously damages your eyesight.

As you can see, the operation is also very convenient. After deploying the service to IIS, enter the URL of the service to be tested in the WSDL endpoint, and click the get button, you can obtain the list of parameters to be input by the Service. During the test, you only need to enter the parameter value and click the invoke button to obtain the result. The result is the same as the result. One side is the parameter, one side is the value, which is easy to check. The parameter type can also be displayed.

However, the disadvantage is that every case must be input once, and the test driver cannot be implemented. In this way, if there are 1000 cases, you need to enter 1000, which is less efficient.

Download. Net WebService Studio

2. webtest from vsts

This is introduced in the Reading Notes of vsts for testers. For more information, seeArticle, Bytes. However, by the way, the test results cannot be copied, which makes me very depressed.

3. New Problems

However, this is not over yet. All the services mentioned above can be deployed in IIS, and the interfaces are public,

However, the current project uses the WCF Service, which is not public and is not deployed to IIS. It is all host-to-system services.

In this way, the above two tools are not supported, so you should first find out if there is a suitable tool. If not, you can only develop it within your own team.

4. soatest

Soatest is produced by parasoft, formerly called soaptest. It uses WSDL to control web service access by describing the service and identify location. It provides WSDL verification, unit testing, functional testing, and performance testing. It supports multiple data sources and is a professional web service testing tool. Specific introduction can visit the official website to visit the http://www.parasoft.com/, the official website provides trial download, has been 5.0 version; in addition, the article soaptest-a useful web service test resource is described in detail.

However, after reading the soatest tutorial document, it seems that the input must be a wsdl url. I am not fully familiar with the use of this tool. I hope anyone familiar with this tool will give me some advice.

4. Independent Development Tools

The main idea is to first extract the XML schema file of each service from the DLL file as a template,

 

 

Import the test data to the template Test Service.

5. Summary

Many systems are now using a service-oriented architecture, and many business functions are implemented through services. During testing, deep-level problems cannot be found through the UI. By testing Servce, the coverage rate can be increased, however, there have been a small number of contacts in the past, and we hope that through discussion, we can form a more appropriate testing method.

1.. Net WebService Studio

This tool is from within Microsoft. The biggest advantage is that it has good visualization. without looking at the XML files, the basic content of WebService has XML, but there are too many cases in the test, the XML file is used to view each test result, which seriously damages your eyesight.

As you can see, the operation is also very convenient. After deploying the service to IIS, enter the URL of the service to be tested in the WSDL endpoint, and click the get button, you can obtain the list of parameters to be input by the Service. During the test, you only need to enter the parameter value and click the invoke button to obtain the result. The result is the same as the result. One side is the parameter, one side is the value, which is easy to check. The parameter type can also be displayed.

However, the disadvantage is that every case must be input once, and the test driver cannot be implemented. In this way, if there are 1000 cases, you need to enter 1000, which is less efficient.

Download. Net WebService Studio

2. webtest from vsts

This article has been introduced in the Reading Notes of vsts for testers. For details, refer to the mango article, author. However, by the way, the test results cannot be copied, which makes me very depressed.

3. New Problems

However, this is not over yet. All the services mentioned above can be deployed in IIS, and the interfaces are public,

However, the current project uses the WCF Service, which is not public and is not deployed to IIS. It is all host-to-system services.

In this way, the above two tools are not supported, so you should first find out if there is a suitable tool. If not, you can only develop it within your own team.

4. soatest

Soatest is produced by parasoft, formerly called soaptest. It uses WSDL to control web service access by describing the service and identify location. It provides WSDL verification, unit testing, functional testing, and performance testing. It supports multiple data sources and is a professional web service testing tool. Specific introduction can visit the official website to visit the http://www.parasoft.com/, the official website provides trial download, has been 5.0 version; in addition, the article soaptest-a useful web service test resource is described in detail.

However, after reading the soatest tutorial document, it seems that the input must be a wsdl url. I am not fully familiar with the use of this tool. I hope anyone familiar with this tool will give me some advice.

4. Independent Development Tools

The main idea is to first extract the XML schema file of each service from the DLL file as a template,

 

 

Import the test data to the template Test Service.

5. Summary

Many systems are now using a service-oriented architecture, and many business functions are implemented through services. During testing, deep-level problems cannot be found through the UI. By testing Servce, the coverage rate can be increased, however, there have been a small number of contacts in the past, and we hope that through discussion, we can form a more appropriate testing method.