{"id":1232,"date":"2021-05-07T23:32:09","date_gmt":"2021-05-07T13:32:09","guid":{"rendered":"https:\/\/www.moneystock.net\/wp_e\/?p=1232"},"modified":"2021-05-07T23:32:09","modified_gmt":"2021-05-07T13:32:09","slug":"when-test-driven-development-goes-wrong","status":"publish","type":"post","link":"https:\/\/moneystock.net\/wp_e\/2021\/05\/07\/when-test-driven-development-goes-wrong\/","title":{"rendered":"When Test Driven Development Goes Wrong"},"content":{"rendered":"

When you feel TDD is difficult when you first started TDD, that might sign that there are improvements to make in the design.<\/p>\n

There are 5 common anti-patterns.<\/p>\n

    \n
  1. The Liar
    \nPasses all tests with no useful assertions, which could be caused by chasing test coverage.
    \n=> Write the test first, which fails with a purpose.<\/li>\n
  2. Excessive Setup
    \nTest and Code are highly coupled. Hard to maintain.
    \n=> Improve Abstraction and Separation of Concerns. Write Test first.<\/li>\n
  3. The Giant
    \nMany lines of code and many assertions which caused by writing the code first before writing testing. This isn’t easy to understand.
    \n=> Decomposed into multiple test cases.<\/li>\n
  4. The Mockery
    \nUse so many mocks, which is similar to the excessive setup.
    \n=> Review design of code. The same solution as #2.<\/li>\n
  5. The inspector
    \nViolate encapsulation to make assertions, which can be caused by poor dependency injection.
    \n=> Never compromise encapsulation for testing. Design for testability.<\/li>\n<\/ol>\n

    In summary, to practice TDD correctly, write a test first, which will help design the code testable.<\/p>\n

     <\/p>\n

    reference: GOTO 2021 \u2022 When Test Driven Development Goes Wrong \u2022 Dave Farley<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

    When you feel TDD is difficult when you first started TDD, that might sign that there are improvements to make in the design. There are 5 common anti-patterns. The Liar Passes all tests with no useful assertions, which could be caused by chasing test coverage. => Write the test first, which fails with a purpose.… Continue reading When Test Driven Development Goes Wrong<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[606,548],"tags":[622,624],"class_list":["post-1232","post","type-post","status-publish","format-standard","hentry","category-architecture","category-c","tag-tdd","tag-test-driven-development","entry"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t