From eae6b57f17f5065a2bd3f130668043693f579cb4 Mon Sep 17 00:00:00 2001
From: Jasper Ras <jras@hostnet.nl>
Date: Fri, 11 Apr 2025 16:02:40 +0200
Subject: vault backup: 2025-04-11 16:02:40

---
 Detroit-style TDD.md | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)
 create mode 100644 Detroit-style TDD.md

(limited to 'Detroit-style TDD.md')

diff --git a/Detroit-style TDD.md b/Detroit-style TDD.md
new file mode 100644
index 0000000..5726068
--- /dev/null
+++ b/Detroit-style TDD.md	
@@ -0,0 +1,18 @@
+---
+tags:
+  - software-design
+  - software-engineering
+  - tdd
+---
+Classic TDD:
+
+1. Write a failing test for public API (red)
+2. Change implementation to make it pass (green)
+3. Refactor
+4. Go to step 1
+
+Benefits:
+- Small increments
+- When adding features we can spot regressions quickly due to having numerous tests
+- Aggressive refactoring possible due to public API being tested
+- Complete regression test suite
\ No newline at end of file
-- 
cgit v1.2.3