summaryrefslogtreecommitdiff
path: root/Detroit-style TDD.md
diff options
context:
space:
mode:
authorJasper Ras <jras@hostnet.nl>2025-04-11 16:02:40 +0200
committerJasper Ras <jras@hostnet.nl>2025-04-11 16:02:40 +0200
commiteae6b57f17f5065a2bd3f130668043693f579cb4 (patch)
tree7b695dd512530d81790063e2ee769eab2ba560e0 /Detroit-style TDD.md
parentf9034731fa234a4b5efa1d2d6147fe1e798b6d36 (diff)
vault backup: 2025-04-11 16:02:40
Diffstat (limited to 'Detroit-style TDD.md')
-rw-r--r--Detroit-style TDD.md18
1 files changed, 18 insertions, 0 deletions
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