bugfix: mutmut should pick up the config before running the original test suite #305
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bug: mutmut reads the config file stored in
mutmut_config.py
only after it runs the initial set of tests. Some tests (like end-to-end, integration tests etc) can't pass without certain infrastructure and are not even supposed to be part of mutation testing process.As a result they fail before mutmut accesses the config file with
runner
command and mutmut can't proceed and crashes as well.Fix: Reading configs prior to running initial set of tests allows to specify test suits you want to run and avoid crashes.
Example: Let's say, you have unit tests in
tests/unit/
folder and you want to run only them. You can configure yourmutmut_config.py
like so: