Schedule a demo
◂ Back to examples
✓

Test your Zato services without running a server

Simulate REST, SQL, LDAP, Jira, and Microsoft 365 connections. Integrate with your CI/CD pipelines for automated testing.

Go to tutorial

Getting started

Tutorial

Step-by-step guide to unit testing Zato services

CI/CD integration

Automate testing in Azure DevOps, GitHub Actions, and other pipelines

Connection types

REST connections

Test outgoing REST API calls with status codes, headers, and request matching

SQL connections

Test database queries and stored procedures

Microsoft 365 connections

Test SharePoint, OneDrive, Teams, Calendar, and other Microsoft 365 APIs

LDAP connections

Test LDAP directory lookups and searches

Jira connections

Test Jira cloud API calls and JQL queries

Invoking services

Test services that call other services

About API testing

  • You can test Zato services without running a server.
  • You write tests using Python's standard unittest module, simulate external connections, and verify your service logic works correctly.
  • The test framework creates a test environment that mimics Zato's runtime, so your services run exactly as they would on a real server.

Frequently asked questions

Do I need a running Zato server?

No. Tests run entirely in Python without any server.

How do I install the framework?

Clone the blueprint project - it has everything set up. Go to the tutorial and it will explain everything.

What connection types can I mock?

REST, SQL, LDAP, Jira, and Microsoft 365 (SharePoint, OneDrive, Teams, Calendar, etc.).

Can I run tests in CI/CD?

Yes. The blueprint includes ready-to-use Azure DevOps and GitHub Actions pipelines.

Start with the tutorial

The tutorial covers installation, mocking, and assertions - everything you need to test your services.

Go to tutorial