VeryGoodOpenSource / VeryGoodOpenSource/vgv-ai-flutter-plugin
feat: Add per-test results to test output
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 162
- Forks
- 23
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 4
Description
Description
I find Claude frequently wastes time and tokens on testing because (according to Claude) the MCP very_good test tool only returns pass/fail — no per-test output. And it is trying to get more information on why it failed. So it then tries a shell very_good test and gets blocked. Then it tries a shell flutter/dart test and gets blocked. It then finally creates a workaround by issuing something like "command flutter test ..." or "dart run test ...".
Requirements
Unless I (or Claude) is misunderstanding something, I think we need more details on test failures, maybe enabled with a parameter (with instructions for Claude to use).
Additional Context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the MCP very_good test tool and the Flutter/Dart test command it invokes, then inspect how their output is currently returned. Define done as exposing per-test results and useful failure details, with any optional parameter documented for Claude or other users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter
- Domain
- developer-experience, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100