Through the API/WebService Adaptor, TAST connects with API REST services that are available in an End Point and use them for testing. This Adaptor has an important companion named Web Services Mapping Assistant with a more detailed and complex user interface for helping to the creation of TAST messages and mappings. It’s possible to perform single tests with this adaptor or End to end tests connecting with other adaptors either.

This is an example of a UML Diagram which uses the API/WebService Adaptor.





This is an example of interactions between the API/WebService Adaptor with other adaptors in an E2E test.




As part of the mapping process, you should provide the Adaptor’s information, regarding to connect and use it:

• EndPoint: Base URL to access the service.
• Keep Session: Indicates whether the session should be maintained between requests to the service. If it is checked, the adapter will add the cookies it receives in the responses to the requests it makes.
• IsSecure: Indicates if requests to the service were sent over the http or https protocol.
• Headers: Allows adding headers to all the requests that are sent to the service.
• Authentication Type: Allows selecting the type of authentication that the service requires.

After the test set execution, immediately you have the results. There are two main elements you can verify:

• Logs: The step by step information of the execution, with:
  • the results.
  • the methods had been executed.
  • the timelines.
• Evidences: The screenshots or evidence information by step, in case they have requested.