Service testing overview

The service testing capabilities of IBM Rational Performance Tester or IBM Rational Service Tester for SOA Quality automate the creation, execution and analysis of functional, regression and performance tests for SOAP-based Web services, XML services or plain text service.
Informative test results rely upon sound test development. Each of the following stages contributes to generating meaningful test results:

Service testing tools

The following tools are available in the product:
  • The generic service client enables you to manually perform service requests for a wide variety of transport protocols, authentication configurations and security profiles, making it an extremely versatile service client. It effectively replaces a dedicated client and can be used to record service calls or for manual testing and debugging a service during development. To open the generic service client, click the Generic Service Client
    WSDL Security Editor
    toolbar button.
  • The WSDL security editor allows you to set up sophisticated security stacks for your service requests and responses. A security stack can contain key definitions, encryption, time stamp, or signature operations and can be associated with each operation in a WSDL file. To open the WSDL security editor, right-click a WSDL file in your workspace and select Edit WSDL Security or click the WSDL Security Editor
    WSDL Security Editor
    button in the generic service client..
  • The test editor is where you develop your test. After recording, you can modify the test to add data correlation or verification points. You can also add loops and conditions and edit you can edit every detail of the service requests.
  • In Rational Performance Tester, the schedule editor lets you deploy multiple virtual users on local and remote computers to generate a heavy load for performance testing. A schedule typically contains multiple tests and multiple virtual users.
  • The stub editor enables you to create service stubs. With the stub editor, you can define multiple input conditions, which are similar to verification points. Each condition triggers a predefined simulated response, which is functionally identical to a response from the simulated service.

Feedback