Generate API test files from endpoint descriptions
A poster described their endpoints to Cursor's agent, which generated .http files with tests and assertions, then ran them through an extension. ·
Done withCursor
- What they did
- In the Reddit comment, the builder says they made a Cursor extension so API testing stayed inside the editor. Their workflow was: describe endpoints to Cursor’s agent or point it at docs, let the agent generate a set of .http files with tests and assertions, then run those files through the extension, which uses their open-source t-req engine to make the requests scriptable rather than static.
- How it went
- The stated result was an in-editor loop where the agent could scaffold runnable API tests and the user could iterate without switching tools or copying tokens around. The post gives no performance numbers or concrete limits beyond saying everything runs locally and needs no account.
- Worth knowing
- The main catch mentioned is that this depends on the author’s extension plus the t-req engine; they say it runs locally and requires no account.
Try it yourself with Cursor
I have an API with these endpoints: [list each endpoint with method, path, and what it does]. In my repo, create .http files in a [tests/api] folder with a request for each endpoint, covering a success case and at least one error case, and add assertions for status code and key response fields. Use [base URL] as a variable, then run the files through my REST client extension and show me which assertions pass or fail. You're done when every endpoint has tests and you've reported the results.
Want help getting this working? Join the Vibe Coding Academy ↗ Run by Alex Finn, who also runs this site.
Source: Reddit · Mar 15, 2025
Related use cases
Keep coding agents running autonomously for long stretches
Cursor's write-up on scaling long-running autonomous coding.
Upgrade site dependencies and frameworks with Cursor
Kent C. Dodds had Cursor's agent look up migration docs, plan and upgrade Remix v2 to React Router v7 and xstate in his site.
Migrate a website from a CMS to raw code and Markdown
Lee Robinson used Cursor agents to move cursor.com off its CMS in three days for $260 in tokens, with subagents handling a broad refactor.
Build a C compiler with a team of parallel agents
Anthropic's engineering write-up on tasking Opus 4.6 agent teams with building a C compiler.
Take ideas to implementation with a planning-command pipeline
A solo SaaS founder uses a custom five-command agent flow (intent, impact analysis, planning, execution, review) with lint guardrails to ship features in a production product.
Build and deploy a blog aggregator website in a day
An author used Claude Code to turn a year-old requirements doc into a live Vue 3 site on Netlify that pulls their posts from several platforms.
Submitted by from search gap: 网站
Get 5 like this every morning
The best things people got an AI agent to do, each with the prompt to try it.