“ Red: Start with tests focusing on the main and edge cases.
Green: We write the sorting function to make the tests green.”
Sounds like you’re writing multiple tests before making any pass. While this doesn’t seem like a bad workflow it’s not TDD. Following TDD you’d write one test, make it pass, then write the next test.
Your point about evolving APIs is well taken. By only writing one test at a time you reduce the amount of work retrofitting new APIs.
I agree with you Teiva, especially about the point in API that is still changing while you code. I had tried TDD and I would say that it depends on the changes we are making. Like any tool / methodology, figure out if it’s a good fit before blindly apply it to your current situation.
“ Red: Start with tests focusing on the main and edge cases.
Green: We write the sorting function to make the tests green.”
Sounds like you’re writing multiple tests before making any pass. While this doesn’t seem like a bad workflow it’s not TDD. Following TDD you’d write one test, make it pass, then write the next test.
Your point about evolving APIs is well taken. By only writing one test at a time you reduce the amount of work retrofitting new APIs.
I agree with you Teiva, especially about the point in API that is still changing while you code. I had tried TDD and I would say that it depends on the changes we are making. Like any tool / methodology, figure out if it’s a good fit before blindly apply it to your current situation.