tag:blogger.com,1999:blog-6605574760630430856.post1124250268604196983..comments2024-03-23T14:49:06.469+01:00Comments on Kode Krunch: TDD: How to test something that doesn't existSlawomir Dymitrowhttp://www.blogger.com/profile/07824496650052695718noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-6605574760630430856.post-14707074485357105512021-10-10T10:29:07.919+02:002021-10-10T10:29:07.919+02:00Hi Slawek! Another great article. I wish I read ar...Hi Slawek! Another great article. I wish I read articles like that when I was junior dev learning TDD. I had to learn it thru pain, exactly the way you described in this post. I cannot agree more with you. One another rule I try to follow when using TDD - tests shall be as close to production as possible. For example, if there is a way to have the fast DB similar as in prod and use it - I go with that in tests, no matter how we call it - unit or integration. Same with other technologies used in prod. Otherwise all my tests can be green but the whole application fail miserably in prod :) Once again, thanks for the post!Dawidhttps://www.blogger.com/profile/02859594262197078942noreply@blogger.com