4 ms·
Vibe coding aside [1], it's very interesting software projects these days don't really care about adding a single test [2]. [1]: https://github.com/withastro/f
by afshinmeh 5mo ago
Vibe coding aside [1], it's very interesting software projects these days don't really care about adding a single test [2].
[1]: https://github.com/withastro/flue/blob/8fdf8e0e9df5bd33c3120f846d510c86188861f6/packages/sdk/src/types.ts#L204 https://github.com/withastro/flue/blob/8fdf8e0e9df5bd33c3120...
[2]: https://github.com/search?q=repo%3Awithastro%2Fflue+test+path%3A%2F%5Epackages%5C%2F%2F&type=code https://github.com/search?q=repo%3Awithastro%2Fflue+test+pat...
- jstummbillig 5mo agoThat would be really interesting. I doubt it's the case, actually probably the opposite? The harnesses seem very happy to write extensive test suits, without me having to ask much.
- ai_slop_hater 5mo agoAnd what would they test? This is a meaningless wrapper for Anthropic or OpenAI SDKs.
- amluto 5mo agoI find this impressive: in my experience, codex-rs loves to add tests even when not prompted. Of course, it’s a bit of a crap shoot as to whether the test tests useful behavior. (My favorite so far: it created an empty file in /home/whatever and added a test to verify that some code it wrote would indeed fail when tested on this empty input and that it would fail with the correct error message. Never mind that this covered approximately none of the desired behavior and that the test would, of course, fail on any other system.
- gerardnico 5mo agoTests is the new gold. You keep them to avoid a vibe coded fork.
- willio58 5mo agoI find automated tests are the only way to keep vibe coded projects on the rails, especially as you grow something beyond demo phase.