hprasing

Author: ejfine

.claude/commands/tdd-review.md

@@ -59,7 +59,7 @@ For each test file, check against these criteria:
 |--------------|-------------------|
 | **The Liar** | `expect(true).toBe(true)`, empty test bodies, tests with no assertions |
 | **Excessive Setup** | >20 lines of arrange code, >5 mocks, deep nested object construction |
-| **The One** | Assertions covering unrelated behaviors in a single test, or several Acts strung together under one name - count alone is not the signal, since one Arrange and Act can warrant many assertions |
+| **The One** | Multiple Acts in a unit test, Acts from unrelated scenarios strung together under one name, or assertions that don't trace back to one of the test's Acts - assertion count alone is not the signal, since a single Act can warrant many assertions, and E2E or other multi-step flows legitimately chain several sequential Acts within one scenario |
 | **The Peeping Tom** | Testing private methods, asserting on internal state, tests that break on any refactor |
 | **The Slow Poke** | Real database/network calls, file I/O, hard-coded timeouts |
 

.config/.copier-answers.yml

@@ -1,5 +1,5 @@
 # Changes here will be overwritten by Copier
-_commit: v0.0.151-17-g7f4ed3c9
+_commit: v0.0.151-19-g09bc4e1a
 _src_path: gh:LabAutomationAndScreening/copier-base-template.git
 copier_answers_directory: .config
 description: Copier template for creating Python libraries and executables

template/.claude/commands/tdd-review.md

@@ -59,7 +59,7 @@ For each test file, check against these criteria:
 |--------------|-------------------|
 | **The Liar** | `expect(true).toBe(true)`, empty test bodies, tests with no assertions |
 | **Excessive Setup** | >20 lines of arrange code, >5 mocks, deep nested object construction |
-| **The One** | Assertions covering unrelated behaviors in a single test, or several Acts strung together under one name - count alone is not the signal, since one Arrange and Act can warrant many assertions |
+| **The One** | Multiple Acts in a unit test, Acts from unrelated scenarios strung together under one name, or assertions that don't trace back to one of the test's Acts - assertion count alone is not the signal, since a single Act can warrant many assertions, and E2E or other multi-step flows legitimately chain several sequential Acts within one scenario |
 | **The Peeping Tom** | Testing private methods, asserting on internal state, tests that break on any refactor |
 | **The Slow Poke** | Real database/network calls, file I/O, hard-coded timeouts |