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
I believe that it would be handy to exclude specified paths from the mutants generation.
Let's say that I want to exclude things like configuration logic or some test helper logic files, located within the src directory. Right now the default behaviour of cargo mutants command is that it tries to generate mutants for every file in the src directory and in their child directories.
I could envision having a command line parameter as follows:
Every file which is located in either /src/tests or /src/config directories are excluded from mutants generation.
Actual behaviour:
Because of the default behaviour of cargo-mutants (and due to the non-existency of this command line parameter) there are mutants generated for the files both in /src/tests and /src/config
The text was updated successfully, but these errors were encountered:
Yep. There is already -f to say which files you do want to test. We could usefully and easily add the opposite. I think it should be a glob (as -f is) not a regexp.
I believe that it would be handy to exclude specified paths from the mutants generation.
Let's say that I want to exclude things like configuration logic or some test helper logic files, located within the
src
directory. Right now the default behaviour ofcargo mutants
command is that it tries to generate mutants for every file in thesrc
directory and in their child directories.I could envision having a command line parameter as follows:
Use case scenario:
Prerequisite:
Git clone test repo
Steps:
Expected behaviour:
Every file which is located in either
/src/tests
or/src/config
directories are excluded from mutants generation.Actual behaviour:
Because of the default behaviour of
cargo-mutants
(and due to the non-existency of this command line parameter) there are mutants generated for the files both in/src/tests
and/src/config
The text was updated successfully, but these errors were encountered: