Wrong?
https://github.com/linux-test-project/ltp/wiki https://github.com/neovim/neovim/tree/master/test https://github.com/openssl/openssl/blob/master/test/README.s...
What are you trying to say, that people don't write tests for their code?
https://github.com/linux-test-project/ltp/wiki https://github.com/neovim/neovim/tree/master/test https://github.com/openssl/openssl/blob/master/test/README.s...
What are you trying to say, that people don't write tests for their code?
Test-Driven Development means that the tests are written before the features.
OK, write the test…
> write a few lines of production code to make it pass
…before the feature.
I recognize the color you’re trying to add (it’s more like TFTFTF than TTTFFF), but it remains Test-Driven Development.
You're conflating unit tests with general testing
Uncle Bob makes it very clear that he only considers "unit tests" to be valid
So, no, these dogmatically "don't count"
(they do count when Uncle Bob supporters want to play half-truths and push for TDD instead of more realistic tests)
They obviously produce useful results and most would love to see more of it, yet it is tacked on afterwards and often by completely different people than the original developers, not as part of the development process.
They have a long way to go to have good enough tests that could be relied on for integration purposes. TDD isn't even on the map. And will probably never be.