5 ms·

Wrong? https://github.com/linux-test-project/ltp/wiki https://github.com/linux-test-project/ltp/wiki https://github.com/neovim/neovim/tree/master/test https://

Wrong? https://github.com/linux-test-project/ltp/wiki https://github.com/linux-test-project/ltp/wiki https://github.com/neovim/neovim/tree/master/test https://github.com/neovim/neovim/tree/master/test https://github.com/openssl/openssl/blob/master/test/README.ssltest.md 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?

chrisoverzero 4y ago
Are you trying to say that “Test-Driven Development” is “writ[ing] tests for their code”? Test-Driven Development means that the tests are written before the features.
- jdlshore 4y ago
  That's a common misunderstanding, but it's not true. TDD involves writing the tests at the same time as the code in tiny little steps. Write a few lines of test code that fail --> write a few lines of production code to make it pass --> refactor if needed to clean things up --> repeat.
  - chrisoverzero 4y ago
    > Write a few lines of test code that fail 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.
    - jdlshore 4y ago
      Sure, if you insist. I've seen enough people misunderstand TDD to be TTTFFF that I think it's important to clarify.
lgleason 4y ago
I would agree with this, but perhaps the commenter has a different definition of "high profile" ¯\_(ツ)_/¯
deleted 4y ago
[deleted]
cylon13 4y ago
Writing tests and doing TDD aren't the same thing. The commenter is talking about TDD in particular I think, not saying "unit testing has no success stories".
raverbashing 4y ago
No. Those are most integration tests (neovim has some unit tests) 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)
- lgleason 4y ago
  I'm an Uncle Bob supporter, but also support pragmatic testing techniques depending on the platform. The two are not mutually exclusive.
xorcist 4y ago
Linux and OpenSSL are two great examples of projects that probably should, but doesn't bother, to do much testing at all. Even if they are both steadily getting better at it. 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.

chrisoverzero 4y ago

Are you trying to say that “Test-Driven Development” is “writ[ing] tests for their code”? Test-Driven Development means that the tests are written before the features.

jdlshore 4y ago
That's a common misunderstanding, but it's not true. TDD involves writing the tests at the same time as the code in tiny little steps. Write a few lines of test code that fail --> write a few lines of production code to make it pass --> refactor if needed to clean things up --> repeat.
- chrisoverzero 4y ago
  > Write a few lines of test code that fail 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.
  - jdlshore 4y ago
    Sure, if you insist. I've seen enough people misunderstand TDD to be TTTFFF that I think it's important to clarify.

lgleason 4y ago

I would agree with this, but perhaps the commenter has a different definition of "high profile" ¯\_(ツ)_/¯

deleted 4y ago

[deleted]

cylon13 4y ago

Writing tests and doing TDD aren't the same thing. The commenter is talking about TDD in particular I think, not saying "unit testing has no success stories".

raverbashing 4y ago

No. Those are most integration tests (neovim has some unit tests) 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)

lgleason 4y ago
I'm an Uncle Bob supporter, but also support pragmatic testing techniques depending on the platform. The two are not mutually exclusive.

xorcist 4y ago

Linux and OpenSSL are two great examples of projects that probably should, but doesn't bother, to do much testing at all. Even if they are both steadily getting better at it. 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.