The test was assuming that we always want to run all the tests in an
workspace, but that is not the case when we have multiple crates that we
want to publish part of the same workspace.
To address this issue, we can now select to run the coverage test only
on the crate in scope. This can be achieved by passing the parameter
--test-scope with the value "crate". By default, tests are still
running as a workspace so that we do not need to update all the other
rust-vmm components that were counting on this feature.
The test-scope option can also be reused in other tests that are
making use of --all. For example, cargo build.
The test was assuming that we always want to run all the tests in an workspace, but that is not the case when we have multiple crates that we want to publish part of the same workspace.
To address this issue, we can now select to run the coverage test only on the crate in scope. This can be achieved by passing the parameter
--test-scopewith the value "crate". By default, tests are still running as a workspace so that we do not need to update all the other rust-vmm components that were counting on this feature.The
test-scopeoption can also be reused in other tests that are making use of--all. For example, cargo build.