Cursor · Anysphere
Let product managers, designers and QA staff work straight from the code
Japanese fintech Money Forward rolled Cursor out beyond engineering, so QA staff turn tickets into test cases, product managers draft specs from the real system and designers pull product data themselves.
What they did
QA connects Cursor to Jira and Notion: one agent writes structured test cases and a second turns them into automated browser tests, and QA also uses it to analyse incidents and review specs early. Product managers ask it to map how parts of the system connect, draw architecture diagrams and draft requirement documents based on what the code actually does. Designers edit live pages and pull analytics through connected tools.
How it went
The company says more than 1,000 employees use Cursor daily and that time spent writing test cases fell by 70%. A product manager quoted in the story says Cursor can find specifications in the code even when no document exists.
Worth knowing
Published by Cursor's maker, with no baseline or method behind the 70% figure. The product and design benefits are described in quotes only, with no numbers.
Try it with Cursor
Read <ticket or spec link> and the related code in <repository or folder>. Write a list of test cases covering the main flow, edge cases and error states, each with steps and the expected result. Point out anything in the spec that the code does differently or that is missing. Do not change any code; save the test cases to <file or Notion page> for my review.
Swap the parts in angle brackets for your own details. This prompt is adapted from the case, not copied from the original.
What this label means: Vendor case study
The maker describes it on its own site or launch post. It shows what the product is meant to do, with no independent result.
Summarised from the original source; the link has the full story. The people and companies here are not Wize customers.