실패
성공
리팩토링
출처:
https://velog.io/@jkijki12/Java-TDD
https://velog.io/@velopert/TDD%EC%9D%98-%EC%86%8C%EA%B0%9C
(영문 해석)
Test-Driven Development starts with designing and developing tests for every small functionality of an application. TDD framework instructs developers to write new code only if an automated test has failed. This avoids duplication of code. The TDD full form is Test-driven development.
A. Requirements - Drive out requirement issues early (more focus on requirements in depth).
B. Rapid Feedback - Many small changes Vs. One significant change.
C. Values Refactoring - Refactor often to lower impact and risk.
D. Design to Test - Testing driving good design practice.
E. Tests as information - Documenting decisions and assumptions.
Source:
https://backend.turing.edu/module1/lessons/test_driven_development?ads_cmpid=6451354298&ads_adid=76255849919&ads_matchtype=&ads_network=g&ads_creative=517671727591&utm_term=&ads_targetid=dsa-19959388920&utm_campaign=&utm_source=adwords&utm_medium=ppc&ttv=2&gclid=CjwKCAjw79iaBhAJEiwAPYwoCNi0gbvrpLupSUh7687Oau8sKoCcjeTmXtpoWVTGgs1R0M4HdzONAxoC2KMQAvD_BwE
https://www.xenonstack.com/blog/test-driven-development
https://www.guru99.com/test-driven-development.html