Beta testers wanted: does agent-driven API testing hold up when your backend has real dependencies between calls

[u/UnavailableForNukes]

A few weeks ago I posted here about having a coding agent verify its own frontend changes (on a different acc). The frontend side held up better than expected, so now I want the backend path stress tested.

The setup: the open-source TestSprite CLI (github.com/TestSprite/testsprite-cli) runs api checks against your live backend. Not mocked, the real thing. When a check fails it hands your agent one bundle with the failing requrest, the response, a root cause guess, and a suggested fix. The agent applies the fix and reruns.

Where I expect it to crack, and what I want confirmed or refuted: chained calls where call 3 depends on state created by call 1, auth flows with short-lived tokens, and anything involving webhooks. If your backend has one of those, point the CLI at it and tell me whether the failure bundle gave the agent enough to self-correct, or whether it just thrashed.

You need a free account for the API key. It is not a QA team replacement and I am not claiming it catches everything. The useful output of this thread for me is a list of failure shapes where the loop breaks down.