Testing / Cucumber Interview Questions
What is living documentation in the context of Cucumber?
Living documentation refers to documentation that stays automatically accurate over time because it's the same artifact that's actually executed as a test, rather than a separate written description that has to be manually kept in sync with a codebase as it evolves.
A Cucumber feature file is a natural fit for this idea: it describes expected behavior in plain language, and it's also literally run as an automated test on every build. If the feature file's description of behavior stops matching what the system actually does, the corresponding scenario fails, immediately surfacing the mismatch, rather than the documentation silently going stale the way a separate wiki page or design document often does.
This property is one of the core arguments for adopting BDD and Cucumber specifically: the specification doesn't just describe the system once at design time, it continuously verifies that description remains true as the system changes.
More Related questions...
