-
Notifications
You must be signed in to change notification settings - Fork 102
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
Improving output: verbose mode #31
Comments
That output looks totally broken and not at all like what it looks like on my machine. How do you run those tests? It's supposed to show an interactive progress and one line of output per surviving mutant. |
The same as in #26 I am using:
|
Strange. It's supposed to output "x out of y" that it erases and overwrites until it finds a surviving mutant and then write "FAILED:" etc on one line and then start with "x out of y" again. So the final output should not contain any "x out of y" and all lines should start with "FAILED: " |
@asottile told me what the problem was: the output breaks when the terminal window is too narrow and you get a line break. |
yes, I have narrow terminal windows. @boxed thanks for digging it! |
I'm going to totally rework the output to remove this bug and make it nicer in some other ways. |
I've now pushed a totally reworked UX, plus a total rewrite of the cache mechanism. I would love for you to give the new code a try! I'll wait a while to release a new version to hopefully get some feedback first. |
@boxed I will have some time on weekend. I will also test how |
I am very curious about the results! |
I've released 1.0.0 of mutmut with the new UX. Please give it a try, I think you'll be pleasantly surprised at how much nicer it is to use. |
Yes, it looks awesome! But, it does not work for me 🙂 I am pretty sure that this is a configuration issue. Can you please guide me?
[mutmut]
paths_to_mutate = server/main_app
backup = False
runner = pytest
tests_dir = tests/ Here's the output:
UpdateThe next time I did clean-build from this template, I have found that it works. |
@boxed considering the output. It looks very pretty! Great work!
But, I still can not see the most important part: what mutations passed. And what tests did the dirty job killing the mutants. Maybe I am missing something 🤔 |
Well crap, the output is wrong. What you want to do is:
To show a diff of a mutant:
And to apply
The mutation ids are just primary keys into the SQLite cache database now. This is a lot nicer to use imo. |
@boxed so, just to be clear, there's a bug in my output?
|
Well, there was a bug in mutmut 1.0.0 where it said "mutmut --print-result", but it should have been "mutmut results". I've released 1.0.1 to fix this and some other minor nitpicks that people found. So the workflow is:
|
I guess there's something wrong with For some reason they are marked as
|
Huh, that IS strange. Can you post that in a new ticket with the project? Since it looks like a small test project I guess you can send it? |
How currently the output looks like?
It shows two cases: failing and successful state.
Let's talk about both of them. I will also try to cover some general thoughts that I have.
First of all, I would like to analyze what happened. Since this process it rather long, I am not able to watch it in real time. The final output is also quite verbose, so it is hard to read it though. What do I suggest? It would be nice to have some short report that will cover:
Secondly, it is possible to have better "inline experience". What do I mean by that?
I would like to say, that this tool is absolutely awesome! Thank you for building it!
The text was updated successfully, but these errors were encountered: