UpdateHub / updatehub / 32296696600
66%

DEFAULT BRANCH: master
Ran
Jobs 1
Files 79
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 62.245%. Remained the same
32296696600

push

github

otavio 
chore: keep test-env out of the default features

`test-env` gates the `updatehub-setup-mock-env` binary and the `updatehub::tests`
helpers the integration tests drive the agent with. It was on by default, so
anyone who follows the README and runs `cargo build --release` compiles 18 crates
they will never run, `mockito` and its HTTP mock server among them, and pays for
them on every build. Nobody should have to remember `--no-default-features` to
get the plain agent.

Turn the default feature set off and let the test targets ask for what they need:

`crate::tests` and `crate::firmware::tests` now answer to `cfg(test)` as well, so
the unit tests keep reaching them with no feature at all.

The three integration test targets gain `required-features = ["test-env"]`. They
call `updatehub::tests::TestEnvironment` and `mockito`, and cargo builds the
library without `cfg(test)` for an integration test, so the feature is the only
way in. `cargo test` skips them and `cargo test --all-features` runs them.

`async-ctrlc` and `mockito` stay optional rather than move to dev-dependencies,
because `src/setup_mock_env.rs` is a binary and cargo gives dev-dependencies to
tests, examples and benches only.

CI needs no change; every step already passes `--all-features`. The `Check build
with the default features` step now covers the feature set users really get.

The stripped binary loses only 8 KiB, as the linker already dropped what the
agent never called. The build graph is where this is paid.

3261 of 5239 relevant lines covered (62.24%)

951.75 hits per line

Jobs
ID Job ID Ran Files Coverage
1 32296696600.1 79
62.24
 GitHub Action Run
Source Files on build 32296696600