Skip to content
BUILT FOR THE WHOLE WORKFLOW

Missing a service?
Keep testing.

Xentropy is a service simulation and API workflow testing platform. Create agents for unavailable dependencies, connect real and simulated APIs, and run end-to-end tests in your browser or on your computer.

Explore workflows and recorded trajectories. Fork a template to get started.
checkout-exampleEXAMPLE GRAPH
COLLECTION / CHECKOUT

From cart to confirmed.

Run
POST/checkoutExample
Inventory12 in stock
$Pricing$48.00
Shipping$6.00
Order confirmed201 Created
Total$54.00
"inventoryRemaining": 10 // state updated
Illustrative exampleInspect the workflow
Your instructions & files Your connected graph Browser or local execution Outcomes you can inspect
LESS WAITING. MORE TESTING.

Bring the rules.
Connect the whole flow.

Use the context you already have to fill a gap in your test environment.

01

Describe the service

Add behavior, specs, source, and fixtures. Keep files in their original formats.

02

Connect your workflow

Build a graph of real and simulated service operations. Bind actual outputs into the next step.

03

Test the outcome

Add test cases and run in your browser or local runner. Each run is a fresh session with inspectable results.

EDITABLE EXAMPLE

A valid response is only
part of the story.

What happens when stock runs out? Or shipping goes offline? Define test cases and follow actual results through checkout.

Explore the checkout demo
Happy pathStock reserved. Order confirmed.201
Low inventoryStop before an order is created.409
Shipping unavailableKeep inventory unchanged.503

Service simulation and workflow testing, explained

Xentropy simulates unavailable services from instructions, files, operation contracts, and initial state so you can test connected API workflows. Learn how to build a workflow.

How does service simulation differ from a fixed mock response?

A fixed mock returns configured responses. Xentropy uses Eve to produce outputs from your service context, request, and session state. Keep expected answers in test assertions, separate from the service instructions. Passing a test does not prove equivalence to the real service.

Where do workflows and simulations run?

The workflow graph runs in your browser or local Node.js runner. Real nodes call their APIs directly; simulated nodes call Xentropy’s hosted Eve service. Each test case starts a fresh session. Read the execution boundaries.

Can I combine real APIs and simulated services?

Yes. Choose real or simulated execution for each node, then bind upstream outputs into downstream requests. Graphs support parallel branches and joins. A failed real call does not automatically switch to simulation. Follow the workflow tutorial.

When should I use the local runner?

Use the local runner for private endpoints, localhost services, or headers supplied from local environment variables. Browser calls require endpoints that allow browser access through CORS. See the API and local runner guide.

Your next test doesn’t have to wait.

Start with one missing dependency and the files you already have.

Open platform

Xentropy models the behavior you define. Passing your tests does not establish equivalence to the original service. Read how workflows run