SAP API testing

API Testing for SAP

Over the past few years, SAP has enhanced their API support through technologies like oData, RFC, SOAP RFC, iDocs and REST. It’s imperative that your test automation solution can support all of these technologies and the appropriate authentication methods (oAUth, SAML, NTLM…)— on all of the various supporting systems (S/4HANA, BW/4HANA…) with API test automation as well as “enabling” technologies such as test data generation and SAP service virtualization.

Tricentis supports the entire SAP API stack natively, without requiring third-party tools or integrations.

Simplify API Testing with Tricentis Tosca

Tricentis Tosca allows testers to rapidly create tests for SAP APIs from recording and then integrate them into end-to-end test scenarios. Even if you’re new to API testing, it’s simple to get started in minutes.

Since all Tricentis API tests use the same model-based test automation technology behind all Tricentis automated testing, they are simple to update. For example, if an element or attribute name changes, just update it once, and that change is automatically propagated to all associated tests.

Additionally, you can use Tricentis technologies to enhance and optimize your API tests. Risk-based testing helps you focus on the tests that matter most, and test data management lets you rapidly populate these tests with the exact data you need to achieve maximum risk coverage.

Supported Technologies

For SAP API testing, Tricentis covers the technologies, authentication methods, and systems that are central to SAP ecosystem.

  • oData
  • RFC
  • IDOCs
  • REST
  • HTTP(s) / JSON / XML
  • oAuth
  • SAML
  • NTLM
  • Kerberos
  • BasicAuth
  • SAP S/4 HANA
  • SAP Cloud Platform
  • SAP NetWeaver Gateway
  • SAP Services

For broader end-to-end testing, we also support the testing of APIs beyond the SAP ecosystem:

Definition Languages
  • WSDL
  • XSD
  • WADL
  • JSON Schema
  • Swagger
  • RAML
  • Odata
  • CopyBooks (12.1)
Transport Protocols
  • HTTP(s)
  • JMS and Queues
  • Rabbit MQ
  • Active MQ
  • AMQP (Advanced Message Queuing Protocol)
  • IBM MQ
  • Oracle Weblogic
  • RFC
  • OData
  • MLLP
  • MS MQ (12.1)
  • KAFKA Message Queues (12.1)
Message Formats
  • XML
  • JSON
  • Text
  • URL-Encoded
  • Form-Data
  • IDoc
  • Binary Content
  • Multipart Attachments
  • MTOM Attachments
  • HL7
  • COBOL (12.1)
  • SOAP
  • REST
  • ISO 20022
  • SEPA
  • Fixed Length
  • CICS (12.1)

Why Test at the API Layer?

Any time that SAP functionality is exposed via APIs, it’s advantageous to test the application logic at the API layer and reserve UI testing for validating the interface:

Easier to Maintain

API tests are less brittle and easier to maintain than traditional UI tests.

Earlier Execution

API tests can be implemented and executed earlier in each sprint than UI tests.

Detailed Verification

API tests can often verify detailed “under-the-hood” functionality that lies beyond the scope of UI tests.

Better UI/UX Checks

API tests are much faster to execute and are thus more suitable for checking whether each new build impacts the existing user experience.