method-test (Total 27 articles)
036. (Unit Test Principles) 10. 단위 테스트 안티 패턴
035. (Unit Test Principles) 9. Mock 처리에 대한 모범 사례
034. (Unit Test Principles) 8. 왜 통합 테스트를 해야 하는가?
033. (Unit Test Principles) 7. 가치있는 단위 테스트를 위한 리팩토링
032. (Unit Test Principles) 6. 단위 테스트 스타일
031. (Unit Test Principles) 5. Mock과 테스트 취약성
030. (Unit Test Principles) 4. 좋은 단위 테스트의 4대 요소
029. (Unit Test Principles) 3. 단위 테스트의 구조
028. (Unit Test Principles) 2. 단위 테스트란 무엇인가
027. (Unit Test Principles) 1. 단위 테스트의 목표
(Working Effectively with Legacy Code) 022. I Need to Change a Monster Method and I Can’t Write Tests for It
(Working Effectively with Legacy Code) 016. I Don’t Understand the Code Well Enough to Change It
(Working Effectively with Legacy Code) 015. My Application Is All API Calls
(Working Effectively with Legacy Code) 014. Dependencies on Libraries Are Killing Me
(Working Effectively with Legacy Code) 013. I Need to Make a Change, but I Don’t Know What Tests to Write
(Working Effectively with Legacy Code) 012. I Need to Make Many Changes in One Area.
(Working Effectively with Legacy Code) 011. I Need to Make a Change. What Methods Should I Test?
(Working Effectively with Legacy Code) 010. I Can’t Run This Method in a Test Harness
(Working Effectively with Legacy Code) 009. I Can’t Get This Class into a Test Harness
(Working Effectively with Legacy Code) 008. How Do I Add a Feature?
(Working Effectively with Legacy Code) 007. It Takes Forever to Make a Change
(Working Effectively with Legacy Code) 006. I Don’t Have Much Time and I Have to Change It
(Working Effectively with Legacy Code) 005. Tools
(Working Effectively with Legacy Code) 004. The Seam Model
(Working Effectively with Legacy Code) 003. Sensing and Separation
(Working Effectively with Legacy Code) 002. Working with Feedback
(Working Effectively with Legacy Code) 001. Changing Software