I don't like this distinction that both post makes. Testing is necessary to deliver quality code. Whether you write your tests first and follow TDD strictly, or carefully plan the feature first and then write your tests, it does not matter. A feature needs to have tests in order for it to be added to the main branch, that is my philosophy.
We should, of course, not get carried away and strive for 100% code coverage, as code coverage is not a metric for how good your tests are. You can easily get to 100% coverage just by testing happy paths of your code.
Quality tests are the telltale sign of a good developer, and in order for everyone to get there, you need to write tests for every feature you develop. You will get better at it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I don't like this distinction that both post makes. Testing is necessary to deliver quality code. Whether you write your tests first and follow TDD strictly, or carefully plan the feature first and then write your tests, it does not matter. A feature needs to have tests in order for it to be added to the main branch, that is my philosophy.
We should, of course, not get carried away and strive for 100% code coverage, as code coverage is not a metric for how good your tests are. You can easily get to 100% coverage just by testing happy paths of your code.
Quality tests are the telltale sign of a good developer, and in order for everyone to get there, you need to write tests for every feature you develop. You will get better at it.