Do it. DO IT

That depends on what you count as a “test”. In some langs/frameworks it is a lot, indeed.

Bash

Yeah. Totally agree on this. I spend maybe 3-4h a day reviewing code, and these are my thoughts…

The LLM generated tests I see are generally of very low quality. Perfectly fitting the bill of looking like a test, but not actually being a good test.

They often don’t test the precise expected value. As an overly simplistic example: They rarely check 2+2==4. But just assert 2+2>0, or often just that 2+2 doesn’t cause an error.

The tests often contain mountains of redundancy. Again, an oversimplified example: They have a test for 2+2, and another for 2+3.

There is never any attempt to make the tests nice to read for humans. It is always just heaps of boilerplate code. No helpers introduced, or affordances to simplify test setup.

Coupling the proclivity for boilerplate together with subtly redundant tests makes for some very poor programming. Worse than I’d expect from a junior, tbh.

And 1500 tests… That is not necessarily a lot! If that is the output of 1 month of pumping out code, I would say bare minimum