build: rely on explicit test-utils feature setting (#137)

Co-authored-by: Leo <[email protected]>

Author: 0xNeshi

CONTRIBUTING.md

@@ -60,9 +60,9 @@ cargo build --locked --all-targets --all-features
 Run the test suite (we recommend nextest):
 
 ```bash
-cargo nextest run
+cargo nextest run --features test-utils
 # or
-cargo test
+cargo test --features test-utils
 ```
 
 Run examples:
@@ -123,7 +123,7 @@ cargo clippy --all-targets --all-features -- -D warnings -D clippy::pedantic
 typos
 
 # Tests (prefer nextest)
-cargo nextest run
+cargo nextest run --features test-utils
 ```
 
 ---
@@ -160,7 +160,7 @@ Key implementation details, trade-offs, and alternatives considered.
 - [ ] `cargo +nightly fmt --all --check`
 - [ ] `cargo clippy --all-targets --all-features -- -D warnings -D clippy::pedantic`
 - [ ] `typos`
-- [ ] Tests pass (`cargo nextest run`)
+- [ ] Tests pass (`cargo nextest run --features test-utils`)
 - [ ] Docs/README/examples updated (if applicable)
 ```
 

Cargo.toml

@@ -72,8 +72,3 @@ workspace = true
 
 [features]
 test-utils = []
-
-[[test]]
-# see tests/mod.rs
-name = "mod"
-required-features = ["test-utils"]

README.md

@@ -262,6 +262,6 @@ Both examples spin up a local `anvil` instance, deploy a demo counter contract,
 Integration tests cover all modes:
 
 ```bash
-cargo nextest run
+cargo nextest run --features test-utils
 ```