목차
When should you delete unit tests ?
“
More tests are better, but if two tests are redundant with respect to each other, should you keep them both around? That depends on two criteria.
The first criterion for your tests is confidence. Never delete a test if it reduces your confidence in the behavior of the system.
The second criterion is communication. If you have two tests that exercise the same path through the code, but they speak to different scenarios for a reader, leave them alone.
That said, if you have two tests that are redundant with respect to confidence and communication, delete the least useful of the two.
—Chapter 32, Test-driven development: by example
목차 관련 글 TDD와 XP “Continuous integration: The tests make an excellent resource, enabling you to integrate more often.” 격리된 테스트 관련 절: Test coupling 두려움을 깨진 테스트로 “What not to test: 두려움이 지루함으로 바뀔 때까지 테스트를 작성하기.” 테스트 악취 “Here are some attributes of tests that suggest a design in trouble.” 그냥 컴퓨터에게 물어보기 “Without the tests you have no choice, you have to reason.” TDD와 설계 관련 절: Be prepared to apply good design 의존과 중복 “If you have details of one vendor's implementation of SQL scattered throughout the code and you decide to chang…” 테스트 주도 개발 “We must write our own tests, because we can't wait 20 times per day for someone else to write a test.” 앎에서 모름으로 “Second, if we need to have a direction in our metaphor, then known-to-unknown is a helpful description.” 테스트 커버리지 “플립의 말을 빌자면 "모든 입력의 경우를 따져서 테스트 커버리지를 높이는 대신에, 우리는 테스트는 그대로 두고 코드를 줄여서 동일한 테스트가 다양한 경우를 다루게 한다." --p157, Test-dr…” 작동하는 깔끔한 코드 “론 제프리즈가 처음 소개하였고, Test-driven development: by example에서 켄트 벡이 인용한 기준.” 테스트 안 하기 “The simple answer, supplied by Phlip is, “Write tests until fear is transformed into boredom.”” On the criteria to be used in decomposing systems into modules “In the first decomposition the criterion used was to make each major step in the processing a module.” Model-driven testing “The model is your test oracle—it tells you not just what to test, but what the expected behavior should be.” 소프트웨어 테스팅의 교훈들 “If a test is truly duplicating another test, what new value is it giving you?” Retrofitting unit tests “The paper presents some common coding practices that make unit tests hard to retrofit, and why.” When to annotate type “First off, explicit types communicate assumptions about the code to readers.” Investigating Intersectional Bias in LLMs using Confidence Disparities in Coreference Resolution “Surprisingly, coreference confidence decreases even for hegemonic or privileged markers, indicating that the re…” Test and type-driven development 주제어가 겹침 Mocks aren't stubs “Dummy objects are passed around but never actually used.”