-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mutmut doesn't test mutants #351
Comments
Did you run |
This is the output:
|
Is this project available somewhere so I can try this? |
Just a note: you should NOT commit the mutants directory to git! |
excuse me but what is the reason? |
They are temporary files for working with mutation testing. I bet it's the same with the cosmic ray files you have committed. At least the .sqlite files seem iffy to commit. You have also committed |
ok, I fixed that. Any updates on the initial issue? |
I'm facing something similar issue. Mutants are being created, but the tests are not being executed Python version: setup.cfg [mutmut]
paths_to_mutate = src/
runner = pytest tests/
tests_dir = tests/ Also tested without result
result of
coverage report: Name Stmts Miss Cover
-------------------------------------------------------------------
src/__init__.py 0 0 100%
src/domain/__init__.py 0 0 100%
src/domain/model/__init__.py 0 0 100%
src/domain/model/exception/__init__.py 0 0 100%
src/domain/model/exception/customException.py 6 0 100%
src/domain/model/usuario/__init__.py 0 0 100%
src/domain/model/usuario/usuario.py 68 0 100%
tests/__init__.py 0 0 100%
tests/domain/__init__.py 0 0 100%
tests/domain/model/__init__.py 0 0 100%
tests/domain/model/usuario/__init__.py 0 0 100%
tests/domain/model/usuario/usuario_test.py 101 0 100%
-------------------------------------------------------------------
TOTAL 175 0 100% When I run mutmut with debug=True on
But I'm not understanding why mutmut is crashing Anyway solved doing a downgrade on mutmut 3 to mutmut 2.5.1
|
@MrMicc |
Hi @boxed ! Happy New Year! 🥳 Link to repo: https://github.com/MrMicc/Study/tree/main/python-playground Thanks in advance |
@MrMicc The code you have there is not correct. https://github.com/MrMicc/Study/blob/main/python-playground/tests/domain/model/usuario/usuario_test.py has imports like |
I'm continuing the discussion here (started here for information #349 (comment) ) because my problem now seems more like the one presented here. I've updated my repository https://github.com/Julien-Delavisse/mutmut-v3-tests with a I'm getting a slightly different result with this script than with my system :
|
Hey @boxed thanks for your support! I configure
But now I'm receiving a problema similar from the issue #341
with
|
Yea. 100% mutants killed. 100% success :P @Julien-Delavisse |
@MrMicc We should not add this information to the readme about how to use python. But I've added a check for it in mutmut so it will fail with an error message. It seems like university courses use mutmut, and there the level of knowledge about python is not super high. This is not really the use case I envisioned when I created mutmut 😅 |
hahaha ...There's no better way to learn something than through unit tests, and with mutation testing, it's even better Congrats about it! It is a really nice and powerful toll |
Having the same issue, https://github.com/GH-maggio/hello_mutmut
|
I am having exactly the same issue when I migrated to mutmut3. In mutmut2, I ran the command When I migrated to mutmut3, I have setup.cfg as follow
When I run I think there might have a bug with multi level directory detection in mutmut3 (or bug from python not able to associate mutant tests with mutant source). If you flatten your project structure, it should work. |
I have a problem with mutmut: the tool creates mutants but it doesn't tests them.
Mutants using command mutmut browse:

Results:

what could be the problem??
@boxed
The text was updated successfully, but these errors were encountered: