farley-score

Score test-suite quality with Dave Farley's 8 Properties of Good Tests (Understandable, Maintainable, Repeatable, Atomic, Necessary, Granular, Fast, First/TDD) and produce a weighted 0-10 Farley Index with per-property evidence, tautology-theatre and mock anti-pattern detection, the five worst tests, and prioritised recommendations. Read-only: it never edits code. Supports Java/JUnit, Python/pytest/unittest, JS/TS Jest/Vitest, Go testing, and C# NUnit/xUnit. Use whenever someone asks how good their tests are, not just how many: 'score my tests', 'farley score', 'farley index', 'review test quality', 'are these tests any good', 'find useless tests', 'tests that pass no matter what', 'too many mocks', 'test smells', or before trusting a suite's coverage number. NOT for measuring coverage or running tests. NOT for writing or fixing tests - it reports; the fixing is separate work. For learning to spot the problems yourself, use farley-score-coach.

Interactive, Socratic coaching on test quality using Dave Farley's 8 Properties of Good Tests - teaches a developer to spot and fix weak tests themselves instead of receiving a report. Walks the properties easiest-first, quizzes on bundled sample tests with deliberate anti-patterns (tautology theatre, mock tautologies, mega-tests, shared state, sleeps, over-specified mocks), asks for score predictions before revealing them, reviews the learner's own tests property by property, and adapts across beginner, intermediate and advanced modes. Use when someone wants to learn or practise rather than get a verdict - 'teach me good test design', 'coach me on my tests', 'why is this test bad', 'what makes a test maintainable', 'practise spotting test smells', 'help me get better at writing tests', 'farley score coach'. NOT for an autonomous scored review of a suite (use farley-score). NOT for writing production code or running tests.