If you just wrote a test and it put your coverage up to 100%, you didn't do TDD, from my own experience, most of the time when you write tests after code, the tests aren't as good.
Write tests first, let it fail, then code, then test again, you'll be almost always 100% covered, and your tests are better.
I'm a developer-turned-business owner who loves to explore the right tools for the job. I enjoy writing and documenting my journey. I use code as one of the tools to solve real problems.
If you just wrote a test and it put your coverage up to 100%, you didn't do TDD, from my own experience, most of the time when you write tests after code, the tests aren't as good.
Write tests first, let it fail, then code, then test again, you'll be almost always 100% covered, and your tests are better.
Exactly my point! 100% test coverage is a tool, not the goal.