Thank you, Victoria, for the post. Here's my humble addition to your thoughts.
One small (read important) thing that may become an obstacle in TDD is the fact, that first step -- writing test, implies that you should completely understand the task and have already decomposed it in your mind into small pieces.
And following the point, this is the core of software development, -- to understand and decompose the task, that can take 40-70% of the time for the task.
And writing tests in RSpec or something else is not difficult after that.
(I'm not talking here about simple scaffolded model and controller tests, but TDD for the business logic)
Thank you, Victoria, for the post. Here's my humble addition to your thoughts.
One small (read important) thing that may become an obstacle in TDD is the fact, that first step -- writing test, implies that you should completely understand the task and have already decomposed it in your mind into small pieces.
And following the point, this is the core of software development, -- to understand and decompose the task, that can take 40-70% of the time for the task.
And writing tests in RSpec or something else is not difficult after that.
(I'm not talking here about simple scaffolded model and controller tests, but TDD for the business logic)
You are absolutely correct. Thank you so much for adding this to the discussion.