summaryrefslogtreecommitdiff
path: root/London-style versus Detroit-style TDD.md
diff options
context:
space:
mode:
Diffstat (limited to 'London-style versus Detroit-style TDD.md')
-rw-r--r--London-style versus Detroit-style TDD.md12
1 files changed, 12 insertions, 0 deletions
diff --git a/London-style versus Detroit-style TDD.md b/London-style versus Detroit-style TDD.md
new file mode 100644
index 0000000..7c10d4d
--- /dev/null
+++ b/London-style versus Detroit-style TDD.md
@@ -0,0 +1,12 @@
+---
+tags:
+ - tdd
+ - software-design
+ - software-engineering
+---
+Detroit-style TDD focuses mainly on working bottom up, starting with the core of the domain working outward.
+London-style TDD works outside in, starting at an API endpoint or controller working inwards.
+
+The primary con of london style is to build things that aren't needed ([[YAGNI]])
+
+https://github.com/testdouble/contributing-tests/wiki/London-school-TDD \ No newline at end of file