TDD

Creator

Creator

Seonglae Cho

Created

Created

2019 Nov 16 7:9

Editor

Editor

Seonglae Cho

Edited

Edited

2024 Jul 27 16:9

Refs

Refs

Emergent Design & Evolutionary Architecture

More about design than testing

Design will emerge from tests

Better abstractions

Less accidental complexity

Atomic understanding of intent

기능 추가시 사례분류한 것 모든 사례 테스트가 작동해야

기능 변경, 제거, 추가시 모든 사례분류가 작동가능해야

TDD Notion

justhackem.wordpress.com

https://justhackem.wordpress.com/2018/01/16/is-that-integration-test-really/

Mockist vs. Classicists TDD

Software Developer and IT-Consultant at codecentric AG Published on The slides of my talk "Mockist vs. Classicists TDD" at the Softwerkskammer Berlin Meetup http://www.meetup.com/de-DE/Software-Craftsmanship-Berlin/events/227959647/. Abstract: There are two different schools of TDD: the proponents of "London School TDD" ("Mockists") drive their design "outside-in" top-down starting with end-to-end acceptance tests.

Mockist vs. Classicists TDD

https://www.slideshare.net/davidvoelkel/mockist-vs-classicists-tdd-57218553

Mockist vs. Classicists TDD

[tdd] 상태검증과 행위검증, stub과 mock 차이

SUT(System Under Test) : 주요 객체(primary object) 협력객체(collaborator) : 부차적 객체(secondary objects) 테스트 더블(Test Double) : 테스팅을 목적으로 진짜 객체대신 사용되는 모든 종류의 위장 객체 Dummy, Fake Object, Stub, Mock https://minslovey.tistory.com/97 http://testing.jabberstory.net/ 많은 테스트 더블들이 있지만, 테스트 더블들의 역할이 딱딱 나뉘어져 있지도 않고, 서로가 서로의 특성을 조금씩 포함하므로, 대표적으로 stub과 mock만을 구분한다.

[tdd] 상태검증과 행위검증, stub과 mock 차이

https://joont92.github.io/tdd/%EC%83%81%ED%83%9C%EA%B2%80%EC%A6%9D%EA%B3%BC-%ED%96%89%EC%9C%84%EA%B2%80%EC%A6%9D-stub%EA%B3%BC-mock-%EC%B0%A8%EC%9D%B4/

Recommendations

///