simperby
simperby copied to clipboard
Configuring the dependency graph for e2e test suits optimization
Note
- It takes tons of time for running CI stage but it takes much longer time for every single PRs to be passed, but this time lag can be minimized by not running unrelevant dependency modules
basic module research
considering to find some third party dependencies in that there's no native module to track the graph in Rust natively
https://sr.ht/~jplatte/cargo-depgraph/ https://github.com/pacak/hackerman/ https://github.com/regexident/cargo-modules
process
- dependency visualization
- map dependencies to tests
- detech changes in pull request
- determine relevant tests & run only them
- fallback strategy (e.g. run full suite of tests)
There's also https://crates.io/crates/guppy