Why Living Documentation is Cool
summary
Claims that tests double as documentation by using living documentation generated from BDD feature files and executed with Serenity BDD. Shows concrete pipeline: PR → main → tests run → HTML report deployed to GitHub Pages or object storage, exposing every scenario, test data and code coverage. Argues this fixes stale docs (one-year-old spec, one-month rework) and enables ubiquitous language between business and dev, while warning AI can hallucinate if used to auto-generate scenarios.
AI-written summary · about
related talks
50m"Living Documentation": When Our Product Definition, Our Automated Tests...
47mDocumentation, it is alive!
43mWhat If Documenting Were Enough to Test?
37mKeeping trust: Testing documentation as part of a continuous integration process
08mExample-driven development: bridging tests and documentation
38mDocs as Tests: A Strategy for Resilient Docs
44mTesting Documentation: Why So Technical?
40mDocumentation as User Experience