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.
- First reported
- cursor.com · 18 Mar 2026
- Added
- 13 Oct 2026
- Source checked
- 13 Oct 2026
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.
What happened
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.
Keep in mind
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 your agent
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.
Replace the <angle brackets> with your own details.
Original source
cursor.comVendor case studyPublished by the company that makes the agent. Read it as a claim.
Tools for this kind of work
- RepoManage your Supabase database and projects from your agent
- RepoManage GitHub issues, pull requests and repos from your agent
