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
Remaining print in console ? #137
Comments
This is the full printout? E.g., there is no introductory message that tests are being started or a final report about the texts? Because this looks a lot like reports about empty or illegal references that comes after the textual table but before the final report. Are there no labels for those lines, e.g., "Empty references found:"? |
It is normal that nothing is shown because I did not put verbose or console. But even in other mode, you'd have those remaining print out of context... |
Gotcha. I saw |
This seems to be something that was introduced with the empty references test. I will continue to check. |
The problem looks to have been with MyCapytain. When I was working on the EmptyReference exception there, I used a print statement for debugging that I accidentally left in there. I will do a PR there to fix it. |
Fixed in Capitains/MyCapytain#176 |
I can't seem to find where this is printing during the tests. When I check stderr and stdout, they are both empty. E.g., the following code (which uses https://github.com/Capitains/HookTest/blob/master/tests/test_run.py#L74-L95):
We want to get where this test does pass as it is. But right now, it shouldn't because it should produce the artifacts described above. (This test does produce and print these artifacts: https://github.com/Capitains/HookTest/blob/master/tests/test_units.py#L579-L597) |
Hey, |
Thanks for the investigation. Please close if you are okay with my answer :) |
OK. Closing. And NP with the late response. I also had other things to do today. |
If you look at the following repository https://travis-ci.org/PonteIneptique/digiliblt and you do
hooktest . -w 7
you getThe text was updated successfully, but these errors were encountered: