vitest / normal testing (examples in template or instructions in CLAUDE.md)? #6

Activity

1. Crazytieguy commented on Aug 28, 2025

   

   Crazytieguy

   on Aug 28, 2025

   Owner

   More actions

   I'm happy you're finding this useful! I mainly didn't put it in because I was optimizing for pure vibe coding and didn't expect unit tests to be very useful. With vibe-coded tests there's a risk of just getting boilerplate tests that don't actually check anything important and slow down further development.

   But I can definitely see a use case for this and will gladly add it! Maybe even later this week. Thanks for posting issues, feel free to post more!

   ❤️React with ❤️1Reacted by helloakemail
2. sandias42 commented on Aug 28, 2025

   

   sandias42

   on Aug 28, 2025

   Author

   More actions

   Thanks so much! And will do regarding issues. The rest of this comment is just user feedback in case its helpful, NNTR.

   The particular pain points I'm feeling that made me think of normal tests (but maybe shouldn't be solved with tests):

   1. Tests-as-documentation-of-expected-behavior: it's difficult do get claude back up to speed after compaction or whatever.
   2. Tests-as-regression-prevention: I've had several instances of working hard to get a particular feature or interaction just right, then asking for something else (usually several compactions later) which breaks what I worked hard to make just-so.
   3. Tests-as-refactoring-harness: this is maybe out of scope for this repo, but I'm at the stage with one of my vibe projects where there's just too much dumb code for claude to keep making progress. I feel optimistic that if I unfucked the code, claude would be able to continue making fast progress, and I also feel optimistic that if I had good tests of the expected behavior I could make the refactor happen fast with only a little manual work (on the schema / interfaces).

   I'd curious to understand how folks change workflow when the code gets messy
3. Crazytieguy commented on Oct 3, 2025

   

   Crazytieguy

   on Oct 3, 2025

   Last edited by Crazytieguy

   Owner

   More actions

   I've finally added e2e testing with playwright, and I think that might actually cover most use cases. LMK if you like it or if you still think vitest would be valuable!
4. charliewwdev commented on Feb 14, 2026

   

   charliewwdev

   on Feb 14, 2026

   More actions

   Testing is definitely the missing piece in vibe coding workflows. Writing test code kind of defeats the purpose of 'just describe what you want.'

   One approach that's worked well for us: instead of traditional test frameworks, use an MCP server that lets the AI agent directly interact with the running app. The AI can tap buttons, fill forms, scroll, take screenshots, and verify state — all from natural language prompts.

   So instead of writing vitest/playwright test files, you just tell Claude: 'Test the signup flow — enter an email, set a password, click Register, verify the dashboard loads.'

   We've built this as flutter-skill — works across web, mobile, and desktop apps. Might be worth considering as an alternative to traditional test frameworks in a vibe coding template, since it keeps the 'zero boilerplate' philosophy.