iotaledger / iotaledger/notarization
Isolate PoI test-cluster tests from default workspace builds
- Dominant language
- Rust
- Stars
- 5
- Forks
- 7
- Avg merge
- 10h 34m
- Merged PRs (30d)
- 11
Description
## Problem
`test-cluster` is an unconditional `poi-rs` dev dependency. Default workspace test builds therefore compile much of the IOTA node stack on every platform, even when running only lightweight tests.
## Proposed change
- Make `test-cluster` optional behind a `test-cluster-tests` feature.
- Gate only cluster-dependent tests and helpers; keep offline tests enabled by default.
- Run `cargo test -p poi-rs --features test-cluster-tests --release -- --test-threads=1` once on Ubuntu CI.
## Acceptance criteria
- `cargo test --workspace` does not compile `test-cluster`.
- CI still runs all PoI test-cluster tests single-threaded.
- Existing epoch-transition and multi-epoch coverage is preserved.
Contributor guide
Research direction
Start by locating the poi-rs Cargo manifest, the test-cluster dependency, and the cluster-dependent tests and helpers. Inspect the Ubuntu CI job, then run the workspace tests and the specified release command with test-cluster-tests enabled. Done means default workspace tests omit test-cluster while CI preserves all cluster, epoch-transition, and multi-epoch coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, testing
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100