Stale Documentation

Documentation that was accurate at the time of writing but has since become outdated due to changes in the system, codebase, or process it describes. In testing, stale documentation is a significant risk because teams may test against expectations that no longer reflect actual system behaviour. Documentation stored in tools like Confluence is particularly vulnerable to going stale when it is disconnected from the development workflow and not actively maintained alongside code changes. The problem is often not that documentation was never written, but that there is no mechanism to keep it current.