You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to be able to generate some kind of database that records what tests cover which source lines. This could then be consumed by something like nextest in conjunction with git diff to only run tests that are affected by the changes in a patch to avoid running the entire test suite all the time.
The text was updated successfully, but these errors were encountered:
But, maybe here you're saying we could remember which specific tests failed due to each specific mutation?
Yes. When discussing with colleages, they suggested doing it by coverage, but I'm not aware of any coverage tools that save such information in a per-test bucket (especially in-process testing like Rust's #[test] or pytest).
Yes, I think it's an interesting idea. I think it's more closely connected to a coverage tool than to cargo-mutants, and it would probably require running each test separately like Nextest does.
It would be nice to be able to generate some kind of database that records what tests cover which source lines. This could then be consumed by something like
nextest
in conjunction withgit diff
to only run tests that are affected by the changes in a patch to avoid running the entire test suite all the time.The text was updated successfully, but these errors were encountered: