150k lines of vibe coded Elixir: The Good, the Bad and the Ugly

Re:150k lines of vibe coded Elixir: The Good, the Bad and th... by dnautics on Sunday January 25, 2026 @04:57PM (#46758799)

yes, Now this test also has to check that your redis-based cache is populated correctly. And/or sends stuff down your RabbitMQ/Kafka pipeline.

[ Parent | on HN ]

Re:150k lines of vibe coded Elixir: The Good, the Bad and th... by pmontra on Sunday January 25, 2026 @05:42PM (#46759325)

That looks like an integration test. A possible way to handle that scenario is to drop all the databases after it ends and create them again, or truncate all the tables or whatever it makes sense for that possible set of different data stores.

That could run on developer machines but maybe it runs only on a CI server and developers run only unit tests.

[ Parent | on HN ]

Re:150k lines of vibe coded Elixir: The Good, the Bad and th... by dnautics on Sunday January 25, 2026 @07:25PM (#46760223)

so in elixir you can do this async alongside your unit tests.

[ Parent | on HN ]