A style that repeats a short process of writing a test for each function needed in the program (this is called Test First), implementing the minimum necessary for the test to work for now, and then refining the code.
Example - Test-driven implementation of the variant 26th decimal system
relevance - behavior driven development - Write tests that more closely resemble the specification description
This page is auto-translated from /nishio/テスト駆動開発 using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. I’m very happy to spread my thought to non-Japanese readers.