I get that TDD makes solid code, I end up spending way too much time on just one method and i loose sight of the big picture and get lost or stuck.
what if i mocked a feature on the side then rebuild it while adding tests. this doesnt feel like test first coding though
what do you guys think?
I had the same struggle and then my mentor at the time said “TDD is not test-first it’s test-driven development”. In most cases it means that product that has continuous deployment flow has tests integrated in CI - if tests fail nothing could be committed and accordingly deployed. This means that if developer wants to introduce new functionality he has to respect tests that are already in place. It literally makes no sense on the scale of one method… Hope this will help a bit 