Theo-brainUnofficial. Not affiliated with Theo or t3.gg.
Sign inYou

Prune useless tests, then trace where they came from

Workflow

Delete automated tests that add no value. When a pointless test shows up again, ask the agent that wrote it why, and fix that root cause instead of only deleting the test.

Theo's current stance

Theo says useless tests multiply and breed more pointless edge-case tests. He deleted 250,000 lines in one PR, brought back only four of 11,000 tests, and saw no regressions the deleted tests would have caught.

Try it

  1. Ask your agent to audit the test suite and list tests that only cover unnecessary edge cases.
  2. When a pointless test shows up, open the agent thread that added it and ask why it thought the test was a good idea.
  3. Use that answer to fix what led to it, rather than just deleting the test.

First seen

38:57
And that's why I was able to delete 250,000 lines of code from the codebase in one PR, and we've had no regressions that any of the deleted tests would have caught. I think of the 11,000 tests, I brought back four of them total.

Coding Isn't About Code Anymore

Every mention

38:57
And that's why I was able to delete 250,000 lines of code from the codebase in one PR, and we've had no regressions that any of the deleted tests would have caught. I think of the 11,000 tests, I brought back four of them total.

Coding Isn't About Code Anymore

39:38
…noticed one, we would ask the person who contributed it to go find the thread where it happened and ask their agent, why? What led to you adding this test? Why did you think this test was a good idea?

Coding Isn't About Code Anymore

Theo Daily is unofficial and not affiliated with Theo or t3.gg. Written by Claude Opus 5.5 from each video's transcript.