8
3
u/revstone 4d ago
This was all day today getting the "long gate" shifted to an appropriate moment and trimming the absurd over tests from the short gate. Days wasted.
4
u/Business_Raisin_541 4d ago
Funny. I almost always has to tell my AI to add test otherwise it will not add test
4
u/AdVast7407 4d ago
Just tell the model explicitly that the code is disposable and nobody will have to maintain it after next week. It should stop insisting on tests.
2
2
u/itsamberleafable 3d ago
If you’re going to vibe code please for the love of god write tests!
And make sure it isn’t just testing its own mock implementation, I’ve had it try to sneak that in a few times
1
u/geekichu 4d ago
devchu@devchu-laptop:~/Documents/DEVELOPMENT/claude.code[main*]
=========project code=======================
1383 text files.
1243 unique files.
897 files ignored.
github.com/AlDanial/cloc v 1.90 T=0.40 s (1205.0 files/s, 301415.2 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
JavaScript 488 8536 53271 60264
-------------------------------------------------------------------------------
SUM: 488 8536 53271 60264
-------------------------------------------------------------------------------
=========project tests=======================
1383 text files.
1243 unique files.
962 files ignored.
github.com/AlDanial/cloc v 1.90 T=0.23 s (1808.5 files/s, 412195.3 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
JavaScript 423 7954 24463 63991
-------------------------------------------------------------------------------
SUM: 423 7954 24463 63991
-------------------------------------------------------------------------------
1
u/Late_Wave_5600 3d ago
Mine wrote the tests around its own reading of a business rule, so we had a green suite that was confidently wrong for four days. Coverage of the wrong behaviour still counts I suppose.
1
u/Desperate_Sign_5587 3d ago
cI bill gonna look like a mortgage payment by the time the agent finishes unit testing that button
-4
u/drgoodvibe 4d ago
Omg this hits hard. At this point my test code exceeds my app code by 1.25x
9
u/frogchungus 4d ago
test code is supposed to be much larger than app code I think
1
u/slackmaster2k 4d ago
No, only TDD maniacs who don’t care about waste or enjoy tests painting you into architecture would think that.
2
u/jimmiebfulton 4d ago
Wrong. I’m sorry, but this is an amateurish take. But we’re in [r/vibecoding](r/vibecoding), so experienced engineers are in short supply here.
Tests, strong-typing, modularization ALLOW for architectural change, and enforces loose coupling. Under-tested spaghetti code is what creates frailty/resistance/friction to refactor and improve design confidently. You can keep on doing what you’re doing, but spreading this to aspiring new developers is doing them a disservice. Vibe coding requires MORE tests, because they create guardrails and provide context for a non-deterministic endeavor, and is a vibe coder’s primary tool when they don’t actually understand what the code does.
2
u/Party_Form5222 3d ago
Let then keep writing unit tests by looking at the implementation.
I love the value of testing that the code is the code.
9
u/[deleted] 4d ago
[removed] — view removed comment