// the find
unclebob/fitnesse
FitNesse -- The Acceptance Test Wiki
FitNesse is a wiki-based acceptance testing framework where you write tests as wiki tables and execute them against your application via 'fixtures' — Java classes that bridge the wiki syntax to your code. It's been around since the early 2000s and is still used in enterprise Java shops that adopted it before modern BDD tools matured.
The self-contained single-jar deployment is genuinely convenient — no test server to configure separately, the wiki IS the test runner. The fixture model cleanly separates test authoring (domain experts write tables) from test plumbing (developers write the Java glue). It eats its own dog food: the acceptance test suite runs inside FitNesse itself, which at least means the core features are continuously exercised. Active enough to still get commits in 2026 despite being a 20-year-old tool.
The wiki-as-filesystem storage model (every page is a directory with content.txt and properties.xml) is painful with version control — diffs are noisy and merge conflicts in test pages are miserable to resolve. The fixture API requires you to write glue code that maps wiki column headers to Java methods by name-mangling convention, which breaks silently when you rename things. Modern alternatives (Cucumber, Serenity, Robot Framework) have better IDE tooling, richer reporting, and active ecosystems — it's hard to recommend FitNesse for a greenfield project when those exist. Documentation lives on fitnesse.org, which itself runs as a FitNesse instance, making it feel like you need to already understand FitNesse to navigate the FitNesse docs.