Developer discovers 2,500 tests in public repo had never been automatically run

A developer found that their public repository, despite containing over 2,500 tests, had no CI pipeline and no GitHub Actions workflows, meaning tests only ran when manually triggered. One crate was missing from the workspace manifest entirely, making it impossible to compile, while a bundled end-to-end script shipped with a probe threshold higher than the actual test count, causing it to exit with an error on every run. The core feature the project was marketed on had a dedicated test that had never once executed, as it lived in the orphaned crate no one had wired into the build. Additionally, the public Cargo.toml declared 19 workspace members while a fresh clone only contained 14, causing every cargo command to fail before reading a single line of Rust code. The developer has since added the missing crate to the workspace and created a CI workflow, acknowledging that an unrun test suite is effectively just a document formatted like code.