2500 tests in my public repository and nothing was running them

Description and use

A public Rust repo had 2,500 tests that never ran due to missing CI, an omitted crate in the workspace, and a failing e2e script. Adding the crate, creating a CI workflow, and fixing the script enabled the tests to run, including a critical one that now passes.

Problem

A public Rust repository contained 2,500 test cases that were never executed because the CI pipeline was missing, a crate was omitted from the workspace, and an end‑to‑end script failed due to a hard‑coded probe count.

Outcome

After adding the missing crate and CI configuration, the repository’s test suite became executable, ten critical tests ran and passed, and the end‑to‑end script no longer failed.

Workflow

• 1. Verify absence of CI by checking .github/workflows and cargo metadata.
• 2. Identify missing crate in workspace by inspecting Cargo.toml members list.
• 3. Add missing crate to members list and commit.
• 4. Create .github/workflows/ci.yml to run cargo test on PRs.
• 5. Update tools/e2e.sh MIN_PROBES to match actual test count or remove the check.
• 6. Push changes and observe CI execution and test results.

Evidence

There was no CI. No .github/workflows/ in the tree and none in its history.

Source

One crate was not in the workspace at all. crates/gx-adapter-time was neither in the members list nor in exclude.

Source

The bundled end-to-end script could not pass in the bundled tree. tools/e2e.sh carried a floor of MIN_PROBES=2822 and the tree it shipped with had roughly 2500.

Source