Comments (1)
demmerichs
commented on June 27, 2024
Some thoughts on this one:
When you want to group by category/functionality, see #42. I am working on a PR that will allow to specify quite flexible rules regarding grouping and relating feature flags.
I can see the need for having different testing configurations, staying in the analogy, e.g. if we change something at the engine, we only want to test feature combinations relating to the engine. For this it would be useful, to have multiple named setting groups that change the behavior of feature set selection just by providing a group name at the CLI. This would also allow to configure a more restricted/reduced feature set for fast testing, and a complete/large feature set matrix for an important milestone testing which is allowed to run longer.
Regarding the random subsampling, I am not a big fan of that. The whole purpose of testing feature combinations and having control over it, is to give developers confidence that they did not miss a bug. Just randomly checking a few does not provide this confidence.
from cargo-all-features.
Related Issues (20)
- Clarify behaviour - feature set vs feature list
- Clarify config options and transitively included features HOT 1
- Cargo udeps integration HOT 2
- Bug: Tries too many / invalid combinations of features on beta/nightly Rust HOT 1
- Support chunking HOT 11
- skip_optional_dependencies is broken with 1.60 HOT 2
- Recommended way to test all crates in a workspace HOT 2
- Optional dependencies that do not create a feature of the same name
- wasm-pack support HOT 1
- Doc test get run despite the `no_run` directive
- `allowlist = []` doesn't do anything
- build-all-features uses all disk space in github actions HOT 3
- argument processing incorrect in cargo subcommand mode
- support at-least-one groups of features (nested ideally) HOT 1
- feature foo needs feature bar HOT 2
- Allow to find out easy way what feature was enabled in transient in crate and what not
- Notify the user of the amount of combinations left at the end of each build stage. HOT 1
- Chunk by feature set rather than crates HOT 3
- Specifying `-p` in a workspace still enumerates featuers from packages not specified on command line
- Option to use workspace.default-members instead of workspace.members
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cargo-all-features.