That's my problem. I REALLY wanna try TDD, but the slowing down part stops me from venturing it.
So do you write TDD for each and every part of your business logic, or is it that there's some things that are not worth tests, like simple small modules/classes?
That is a great question. The reason behind tdd, or tests in general is to ensure your logic works as expected all the time. And that is why it makes you faster, because its all about confidence.
So for me, the answer is yes I test all business logic. If it is simple then its test will be very very easy but you will ensure that your product works as expected all the time.
And another benifit I notice is that if you are reading a code you wrote long time ago or other people code, its easier to start from tests, because the have to be easy and you can easly spot the inputs and outputs of your component.
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.
That's my problem. I REALLY wanna try TDD, but the slowing down part stops me from venturing it.
So do you write TDD for each and every part of your business logic, or is it that there's some things that are not worth tests, like simple small modules/classes?
That is a great question. The reason behind tdd, or tests in general is to ensure your logic works as expected all the time. And that is why it makes you faster, because its all about confidence.
So for me, the answer is yes I test all business logic. If it is simple then its test will be very very easy but you will ensure that your product works as expected all the time.
And another benifit I notice is that if you are reading a code you wrote long time ago or other people code, its easier to start from tests, because the have to be easy and you can easly spot the inputs and outputs of your component.