What could go wrong when we let CoPilot write our unit tests.

If you let them write it after development even just to get coverage.

Big LoL.

@chfkch
By not saying you are wrong, doing TDD and reviewing the tests closely to verify if the doc matches the expectations could be a very powerful approach

@matil
True, but not having a defined expectation/test scenario and just creating coverage is a bad approach.

I like TDD, but that's not it. We will see, nothing is finally decided on that matter.

@chfkch agreed also it’s important to keep record of architecture even further like ADRs etc