JSON-Driven API Sequencing Engine

The problem

Many API tests have the same shape: call, wait, pass a value on. Writing each one as code repeats the same work.

How it works

1. 01JSON config
2. 02Fill in values
3. 03Call + retry
4. 04Stream results (SSE)
5. 05Report

What was hard

• Some endpoints answer “accepted” and finish later, so steps poll until done or time out.
• Results stream to the builder over SSE while each step runs.
• The config has to stay easy for someone else to read and edit.

The result

New test sequences are written as config and run from a visual builder, not coded by hand.

Built with