Hard to think of the tests
--------------------------
What about existing code or piece of code, say posterior TDD?
Aren't moving future bugs at the test code side? Worse aren't we adding maintenance effort on the test side?
Playing a video (Stop)
Powered by Haskell (GHC 8.8.4
)
Does not fit how I code.
------------------------
There are a lot of moving parts in our legacy code base - e.g. C/C++ intertwinded with some generated code. No point testing until we have done some minimum stitching etc.
Hard to think of the tests
--------------------------
It would be challenging to implement in complex function which perform multiple tasks. There will be to many unknown scenarios.
There is no design.
-------------------
There seems to be no notion of "design" - where we are approaching it with one bit at a time. Some times we are applying an existing "design pattern" or approach. What to do in such a case?
Other.
------
Should try to cover as much scenario as possible to not miss any feature.
Too much time.
--------------
Unclear how to apply this '1 line of code at a time' and watch it fail- knowing it'll fail. Also there is we a lot of build time involved in how we build our code.
Hard to think of the tests
--------------------------
how it will works when the requirements changes dynamically ?
What concerns you about TDD?
