A list of Logical Fallacies for Testing.
This went around at the office and I got permission from its author to share.
diff --git a/LogicalTestingFallacies.wiki b/LogicalTestingFallacies.wiki
new file mode 100644
index 0000000..f2230da
--- /dev/null
+++ b/LogicalTestingFallacies.wiki
@@ -0,0 +1,28 @@
+#summary "Why My Patch Doesn't Need Tests"
+#labels Importance-Useful,Phase-QA,Contents-Complete
+
+Author: Adrienne Walker (a colleague of Nathaniel's at Google)
+
+==_Appeal To Importance_==
+
+This needs to land this right now to fix a bug / make a milestone / my hair’s on fire; can't you understand that there's no time for tests??
+
+==_Sufficient Coverage Argument_==
+
+This CL already has at least one unit test, and therefore should be considered reasonably tested.
+
+==_Argument From Historical Laziness_==
+
+This other pre-existing system doesn’t have tests, so my similar new system shouldn’t need any either!
+
+==_Missing Infrastructure Argument_==
+
+There’s no good way to write these tests easily, so I shouldn’t need to write them.
+
+==_Just a Refactoring Argument_==
+
+All functionality in this patch is already entirely covered by preexisting tests. Trust me.
+
+==_Promise Of Future Work_==
+
+I pinky-swear that I will write a follow-up CL that adds tests, just as soon as I fix these other things first...
\ No newline at end of file
