Comments (2)
I think this would be interesting! It's a lot of work though. I'd estimate around 120 hours of work for someone new to the project, including:
- defining the protocol: likely a file on disk, similar to environment files in GitHub Actions)
- writing test runner support for the protocol
- writing a library that tests can import to make it easy to write their properties (e.g.
nextest-testlib
) - testing
- documentation
- building this as an experimental feature, then shepherding the feature until it is final.
(The time estimate is not meant to deter you, it's just meant to set realistic expectations regarding the quality goals of the project. Like all time estimates in software engineering, it could very well be completely off)
I don't plan to work on this unless my employer needs it. However if you're interested, let's chat here in this issue. I'd love to hear the direction you would like to go in.
from nextest.
Hello
Sorry for the late reply.
I understand, to be honest I'll try to find some time to think about it but at this moment it's a little complicated ^^
from nextest.
Related Issues (20)
- Ability to specify a custom cargo profile? HOT 2
- `build.rs` line change slows tests HOT 2
- Ability to enable features in the configuration HOT 2
- Allow user-specific configuration
- Allow to display stdout, while silencing test harness. HOT 2
- Add support for excluding paths from an archive
- Archive extra files, relative to paths other than the target directory
- Add a way to include extra files on a per-test-binary and per-platform basis
- Add a "testimonials" page (please comment here!) HOT 3
- [windows] lots of tests running in parallel may cause "leaky" warnings HOT 3
- v0.9.70 using significantly more stack HOT 7
- Idea: network isolation between tests HOT 14
- Add support for `cargo test`s --skip and --exact command line flags HOT 1
- `cargo nextest run --workspace` fails with DLL missing if a macro lib exists HOT 14
- nextest chooses arbitrarily not to run some tests it's found HOT 6
- Consider conditions to not include libstd in archives
- [meta] tell users what configuration their tests are running with
- Human-readable configuration output HOT 1
- Machine-readable configuration output
- Feature Request: Conditional skipping test based on setup scripts
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 nextest.