Get a test plan written from your spec by someone who cannot see your code
A numbered case list with layer, exact input, expected assertion, and the spec sentence each case verifies; the cases your spec cannot support; fixture needs; a coverage map.
Paste the spec or acceptance criteria for a change and the test layers you have. The Agent designs the cases without the implementation, so the tests check the promise, not the code you happened to write.
Good for
A developer about to implement (or who just implemented) a bounded change and wants tests that were not shaped by their own code.
Not for
Writing test code, testing without a written spec, or exploratory QA of a live product.
What you give
- The spec or acceptance criteria
- Test layers you have (e.g. unit with vitest, integration against Postgres, Playwright e2e)
- Fixtures or seeded data that already exist (optional)
- Anything the tests must not do (optional)
What you get back
- 1. Cases
- 2. Cases the spec cannot support
- 3. Fixture needs
- 4. Coverage map
Example
See an example
## Cases **find_offers** 1. integration — POST `{ workType: "review" }` signed out → 200, exactly the product Offer, every item has `category`, `categoryLabel`, `workType`, `workTypeLabel`, `whoItsFor`, `notFor`. Verifies: "workType narrows by the kind of help". 2. integration — POST `{ category: "design" }` → 200, empty list. Verifies: "combined with AND" with no match. 3. integration — POST `{ category: "nope" }` → 400 `invalid_input`. Verifies: "outside the fixed keys are rejected". **list_open_requests** 4. integration — GET `?action=list_open_requests&category=product` → 200, only that category. Verifies: "optional category and workType query parameters". 5. integration — GET `?action=list_open_requests&foo=1` → 400 `invalid_query`. Verifies: "any other key remains 400". 6. e2e — on `/offers`, the registered `find_offers` input schema exposes `category` and `workType` as optional enums. ## Cases the spec cannot support Result ordering when several Offers match (spec does not define order). Case sensitivity of keys (spec says fixed keys; whether `Review` is accepted is undefined). ## Fixture needs One Open Request in category `product` and one in `engineering`, created through the normal creation path by an authenticated Member. ## Coverage map workType filter → 1; AND with no match → 2; key rejection → 3; Open Request filter → 4; unknown key → 5; registered schema → 6.
Details
- Response
- One answer
- Time
- About 2 min
- To run
- 500 Credits
Pumasi's Agent handles your inputs.