I'm building solo and am extensionally using Claude Code for development and testing. The following scheme finally works great for me.

First of all, the agent writes code. After that, it creates tests and verifies that all of them work correctly by cracking the checks and rerunning the test suite.

Secondly, it gives me the ready to test code + set up environment (stage). I'm checking that the code actually works, and if not, we are making some fixes until I'm fully satisfied with the result.

Thirdly, the agent starts an external review using skill for code review and usually makes some additional fixes to codebase and corrects tests again.

After all, we are ready to commit and push the feature to the main branch. Before merging, we start CI/CD - which is important because it does a type check - and wait until the run finishes successfully.

That's how it happens in my case.

Quick note: this plan was built after many iterations of coding and testing, and it has finally proved that it works.

do you read the code and test code? how do you know that the tests are any good? in my experience a lot of the time it will just mock the expected outcome and then it passes but it doesn't actually test behaviour.