Testing Web Services - Overview

Need to test REST and SOAP web services? Looking for advanced features like data-driven testing and response validation?

Check out ReadyAPI – an all-in-one automated testing tool for REST and SOAP services. It is code-based on SoapUI – the world’s most popular API testing solution – and includes tons of pro features:

• Support for all major web service technologies: REST, SOAP, Swagger, WSDL, WADL, OAuth 2.0, OpenID Connect, JSON, XML, and more,

• Functional, security, and load tests,

• Easy service mocking and virtualization,

• Data-driven testing and parameterization,

• Response validation with 25+ built-in assertions,

• And more.

Download a free trial now to see how ReadyAPI works for you.

If needed, integrate ReadyAPI tests into your TestComplete projects for unified reporting.

Supported Web Services and Protocols

Functional Web Service Testing in TestComplete

Creating Web Service Functional Tests

Using Web Service Checkpoints

More Information on Testing Web Services in TestComplete

Sample

TestComplete can test web services that match the following specifications:

Notes:

• For information on supporting WCF services, see WCF Services - Specifics of Testing.

• For more information on specifying authentication information for service clients, see Specifying Web Service Credentials.

• For information on data types that can be used in tests, see Supported Data Types.

• Currently, TestComplete does not support testing of web services that use encryption.

To test web services in TestComplete, you use Web Service items that belong to the Web Services collection in your project. Each Web Service item contains the following information:

• The web service’s URL and SOAP version.

• The URL of the web service’s WSDL file.

• Types and methods that the WSDL file defines.

You use Web Service items to call web service methods in your tests and check the method results. You access Web Service items and call methods of appropriate web services by their names:

Once you get a result value, you can verify it. You can do it by using standard comparison statements (the if statement in scripts, the If Then operation in keyword tests) or by using web service checkpoints (see below).

To change the API that TestComplete uses to call your web service methods, configure the Preferred Web Service API options. Enable the .NET WCF option to use the .NET API to call web service methods. Otherwise, use the native API.

Functional web service tests cannot be recorded. You create them manually by calling web service methods and checking their values from test scripts or keyword tests.

For detailed instructions on how to create a test, see –

Creating Web Service Tests

SOAP web services use the XML format for transferred data.

In TestComplete, you can use XML checkpoints to verify XML documents easily. To use XML checkpoints to verify your web service responses:

1. Store an expected response in the Stores | XML collection.

2. Call the needed web service method.

3. Call the XML checkpoint to verify the method result against the stored data.

To perform all these steps, you can use the Checkpoint wizard. The wizard guides you through the baseline XMLCheckpoint element creation and generates the code or keyword test operations that call the needed web service method and verify the result. See About Web Service Checkpoints.

Refer to the following topics to learn more about creation of web service tests in TestComplete:

TestComplete includes a sample project that demonstrates how to call web service methods from scripts, prepare complex parameters for the methods to be called and check the returned results by using script statements and checkpoints:

<TestComplete Samples>\Common\Web Service Testing\Functional Testing

These projects work with a sample web service that resides on our web site:

secure.smartbearsoftware.com/samples/testcomplete14/webservices/Service.asmx